Principal Quality Engineer job description

Quality engineering — Principal Quality Engineer
Sets quality strategy and release gates across the organization.

RESPONSIBILITIES
- Set how risk is assessed and weighted across the organization's test effort, and arbitrate when two teams disagree about where the risk actually sits.
- Set how the organization measures, quarantines and pays down flakiness, and hold the line when a team wants to retry past it.
- Set how the organization tests and budgets for performance, and influence architecture decisions before performance has to be retrofitted.
- Set the baseline security testing a product runs before every release, and judge which findings need a specialist penetration test rather than routine testing.
- Get to the bottom of cross-platform failures with no obvious cause, in input handling, viewport behavior or an older engine, and reach a fix rather than a workaround.
- Own the organization's test strategy and set the standards, tooling and staffing that test teams follow.

REQUIREMENTS
- Experience at the QA Lead level (level 4 of 5) or equivalent
- Holds ISTQB Certified Tester Foundation Level, ISTQB Certified Tester Advanced Level - Test Analyst and ISTQB Certified Tester Advanced Level - Test Automation Engineering

REQUIRED SKILLS
Test Analysis
- Exploratory Test Charters — You can plan a charter set that covers a feature area by risk rather than by habit, coach others in chartering, and fold session notes back into the test approach.
- Risk-Based Test Prioritization — You can set how risk is assessed and weighted across the organization's test effort, and arbitrate when two teams disagree about where the risk actually sits.
- Requirements and Acceptance Criteria Analysis — You can lead requirements analysis across several teams, coach others in spotting untestable criteria, and get analysis engaged earlier in the lifecycle.
- Boundary and Equivalence Test Design — You can teach the technique to others, review their case sets for gaps, and combine it with other techniques where equivalence classes alone miss real risk.
- Defect Management — You can use defect patterns to recommend where your team should invest in prevention.

Automation
- Automation Framework Design — You can set automation framework strategy across the organization, including build-versus-adopt decisions for shared tooling, and be the final call when teams disagree on approach.
- API Test Automation — You can set the API automation approach for a product, including how tests handle test data, environments and flaky dependencies, and coach others in it.
- UI Test Automation — You can set the UI automation approach for a product, including where UI automation is the right layer versus API or unit level, and coach others in writing stable tests.
- Regression Suite Maintenance — You can rebuild a suite that has lost the team's trust, cutting run time and duplication without losing coverage that matters, and decide which tests survive a large refactor.
- Test Code Review — You can review tests across unfamiliar components and complicated setups, and catch the coverage gap nobody had framed as one. Your reviews teach: the same problem stops appearing in that author's next pull request.

Test Engineering
- CI Test Pipeline Integration — You can set the CI test pipeline strategy for a product, including what blocks a merge versus a deploy, and diagnose pipeline-level flake that automated-test fixes cannot reach.
- Test Data Management — You can set the test data strategy for a product, including how production-like data is generated or masked safely, and fix data-related flake others cannot trace.
- Test Environment Provisioning — You can design provisioning for test runs that span several services and awkward third-party dependencies, and decide what to stub rather than run.
- Flaky Test Diagnosis — You can set how the organization measures, quarantines and pays down flakiness, and hold the line when a team wants to retry past it. You make the link between flake rate and how far people trust the pipeline visible to leaders.
- Test Reporting and Metrics — You can design reporting for a program with several teams and competing definitions of done, and keep it honest under pressure to look green. You retire a metric once it starts driving the wrong behavior.

Specialist Testing
- Load and Performance Test Design — You can set how the organization tests and budgets for performance, and influence architecture decisions before performance has to be retrofitted.
- Accessibility Conformance Testing — You can set the accessibility testing approach for a product, coach others in manual technique beyond automated scanning, and get findings fixed before release rather than logged and left.
- Baseline Security Testing — You can set the baseline security testing a product runs before every release, and judge which findings need a specialist penetration test rather than routine testing.
- API Contract Testing — You can introduce contract testing across services owned by different teams and settle who publishes and who verifies. You use it to shrink the end-to-end suite rather than to add another layer on top of it.
- Cross-Browser and Device Testing — You can get to the bottom of cross-platform failures with no obvious cause, in input handling, viewport behavior or an older engine, and reach a fix rather than a workaround. You keep the support matrix honest against what users actually run.

Quality Leadership
- Test Strategy — You can own the organization's test strategy and set the standards, tooling and staffing that test teams follow.
- Release Readiness Assessment — You can define how releases are judged ready, who owns the call and what evidence counts, and overrule a green dashboard when the risk lies outside what it measures.
- Quality Coaching and Enablement — You can decide how quality capability is built across the organization and where the effort is worth spending. You change how teams beyond your reach think about their own testing, by persuasion and evidence rather than mandate.
- Quality Gate Definition — You can set which quality gates the organization requires and which are a team's own choice, and defend the delivery cost of each one. You remove a popular gate when the evidence says it is stopping nothing.

Delivery
- Project Management — You can set the everyday habits for how work is organized and followed up across the organization, and teams you do not lead adopt the routines you introduce.
- Planning & Estimation — You can forecast work and staffing quarters ahead, and set the estimating method other teams use.
- Ownership & Accountability — You can report the organization's most exposed outcomes to its leaders as they stand, including bad news, and answer for them.
- Quality Focus — You can raise the quality bar across the organization by building the tools and habits that make the careful way the easy way.

Craft
- Problem Solving — You can crack problems the organization has repeatedly failed to solve, and your approach becomes how others tackle that whole kind of problem.
- Domain Expertise — You can influence how the field is practiced beyond this organization, and your expertise settles questions that have stood open for years.
- Continuous Learning — You can set what the organization invests its learning time in, and the material and practice you create outlive your involvement.

Communication
- Communication — You can set how the organization communicates by creating the forums and norms that teams use to share information.
- Collaboration — You can remove the barriers that stop teams working together by putting in place routines and forums they use across the organization.
- Writing & Documentation — You can set the writing standard the organization works to, and documents you wrote are still in use long after you have moved on.
- Stakeholder Management — You can represent the organization in its most important relationships and set how it engages with everyone who depends on it.

Leadership
- Leadership — You can set direction for the whole organization, make hard calls under real uncertainty, and carry the decisions nobody else wants to own.
- Mentoring — You can shape how the organization grows its people, and those you developed are themselves named by others as strong in their field.
- Strategic Thinking — You can shape the organization's strategy, and the bets you argued for are visible in where it ended up.

REQUIRED CERTIFICATIONS
- ISTQB Certified Tester Foundation Level (required from QA Engineer)
- ISTQB Certified Tester Advanced Level - Test Analyst (required from Senior QA Engineer)
- ISTQB Certified Tester Advanced Level - Test Automation Engineering (required from QA Lead)