MissionOwn comprehensive, risk-based validation of complex IRIS data-platform capabilities and provide actionable evidence of functional, data, integration, resiliency, and release quality, using production-quality Python automation, reusable validation frameworks, and automated CI/CD quality gates.
Responsibilities
- Design, develop, test, and maintain production-quality Python test automation, applications, reusable components, and validation frameworks that support complex platform quality-engineering initiatives.
- Design risk-based test strategies for complex features, integrations, data flows, and releases.
- Build and maintain scalable automated suites for REST APIs, JSON contracts, ETL/ELT pipelines, transformations, orchestration workflows, Spark-based processing, Kubernetes-based services, and cloud dependencies.
- Apply strong software-design practices, including object-oriented programming, modular design, parameterization, configuration management, structured logging, exception handling, packaging, and debugging, to Python automation frameworks and validation utilities.
- Design complex data-reconciliation approaches that validate source-to-target completeness, accuracy, transformation logic, duplicates, null handling, referential integrity, and exception behavior.
- Lead unit, regression, integration, end-to-end, negative, boundary, failure, recovery, resiliency, performance, and scalability validation for assigned capabilities.
- Create reusable Python frameworks, validation libraries, templates, fixtures, controlled test data, and self-service capabilities that are adopted across workflows and teams.
- Partner with data consumers, application teams, platform engineers, and software engineers to translate requirements and risks into validation approaches and improve the quality of delivered datasets.
- Analyze complex application defects, pipeline failures, performance bottlenecks, and data-quality issues across application, data, orchestration, and environment layers; isolate failure conditions and provide actionable root-cause evidence.
- Validate application and pipeline behavior across supported cloud and Kubernetes configurations, dependencies, scaling conditions, and recovery scenarios.
- Implement and use observability, monitoring, logging, and alerting capabilities to validate data quality, application reliability, and timely pipeline execution across cross-component workflows.
- Maintain traceability among requirements, risks, tests, defects, execution results, and release-quality evidence; identify systemic coverage gaps and drive remediation through test design, engineering improvements, or explicit risk acceptance.
- Embed automated quality gates into CI/CD pipelines and drive cloud-native development, DevOps, and quality-engineering practices across applicable platform components.
- Drive improvements in test automation, pipeline reliability, performance, and operational efficiency through reusable engineering patterns and continuous automation.
- Review test designs and automation code, mentor Quality Engineers, and contribute technical documentation, knowledge sharing, and reusable implementation examples.
- Use AI-assisted software and test development responsibly to accelerate Python coding, test generation, test-data creation, debugging, troubleshooting, and documentation while maintaining documented human review of all generated outputs for correctness, security, maintainability, relevance, and coverage.
- Risk-based feature and release test strategies.
- Production-quality Python test automation, validation frameworks, and reusable components committed to source control.
- Cross-component automated unit, functional, API, data, regression, integration, and end-to-end test suites.
- Reusable Python frameworks, libraries, fixtures, templates, controlled test data, and self-service validation capabilities adopted across workflows.
- Complex data-reconciliation, resiliency, and failure/recovery validation assets.
- Defect evidence, root-cause analyses, and retest confirmation for complex cross-component issues.
- Requirements-to-test traceability, quality-risk assessments, and release-readiness evidence.
- Automated CI/CD quality gates, observability capabilities, and actionable diagnostic information.
- Test reviews, mentoring outputs, coverage-improvement plans, technical documentation, and knowledge-transfer materials.
Measurable success outcomes
- Outcome areaMeasure of successStrategy readinessTest strategy for assigned material scope is reviewed and approved before execution begins or within the agreed planning window.
- Risk coverage100% of identified critical and high risks have tests, mitigating controls, or approved residual-risk disposition.
- Automation growthPriority regression and cross-component scenarios show measurable automation improvement from the 30-day baseline against approved targets.
- Defect containmentNo unresolved critical defects in assigned scope at release decision; high-severity defects are remediated or formally accepted by authorized client owners.
- Defect effectivenessAt least 95% of submitted defects are accepted without return for inadequate evidence; defect reopen rate remains below the client-agreed threshold.
- Resiliency evidenceClient-designated failure and recovery scenarios are executed with documented expected versus actual results before relevant release decisions.
- LeadershipRequired reviews, mentoring, and coverage decisions occur at the agreed cadence, with unresolved material findings explicitly escalated.
- Reuse and quality gatesShared validation frameworks and libraries are documented and adopted by at least two applicable workflows, components, or teams; agreed critical checks run automatically in CI/CD with actionable diagnostics.
- Observability validationPriority cross-component pipelines have agreed data-quality and timeliness checks implemented through observability, monitoring, or alerting, with failures dispositioned before release decisions.
- Engineering quality100% of production-bound code is peer reviewed, source controlled, tested, and compliant with agreed CI/CD quality gates.
Stakeholder interactions
- Principal Quality Engineer
- Senior and principal software engineers
- Architecture and DevOps
- Data engineering and platform operations
- Product owners and release stakeholders
- Application and data consumers
Qualifications
- Preferred qualificationsExperience with non-functional testing, distributed systems, production incident analysis, or data observability.
- Experience creating testing frameworks or common enterprise QE assets.
- Experience communicating release risk to senior technical and product stakeholders.
- Experience working in Agile product teams and vendor-delivered engagements.
Required Skills
- Required skills and experienceStrong Python software-development and automated quality-engineering experience, including object-oriented programming, classes, modules, functions, parameters, exception handling, reusable component design, and pytest or comparable testing frameworks.
- Proficiency with Python logging, configuration management, command-line parameters, debugging, structured error-handling patterns, dependency management, and Python packaging.
- Experience writing unit, integration, regression, and end-to-end tests for Python applications, automation frameworks, reusable components, and transformation logic.
- Knowledge of software-design principles, maintainable coding practices, source control, code reviews, reusable framework design,