QA Engineer career ladder: levels, titles, and criteria
Career levels, titles, scope, and promotion criteria for qa engineer roles — from entry level to senior leadership.
QA engineer career ladder — quick overview
A QA engineer career ladder typically runs: QA Engineer I → QA Engineer II → Senior QA Engineer → Lead QA Engineer / SDET → Staff / Principal QA Engineer on the IC track. Management track mirrors engineering: QA Tech Lead → QA Manager → Director of QA/Testing → VP of Engineering (Quality). QA increasingly overlaps with software development engineering, especially at the Senior and Lead level.
Turn this ladder into a live framework for your team. Start free →
QA Engineer IC career levels
| Level | Title | Scope | Key differentiator | Typical YoE |
|---|---|---|---|---|
| IC1 | QA Engineer I | Assigned test cases; manual and basic automation | Writes and executes test cases; reports bugs clearly; learns the product and CI/CD pipeline | 0–2 |
| IC2 | QA Engineer II | Feature area; growing automation ownership | Builds automated tests for assigned features; contributes to test frameworks; runs regression suites | 2–4 |
| IC3 | Senior QA Engineer / SDET | Product area; cross-feature automation | Designs test strategy for a product area; builds and maintains automation frameworks; partners with engineering | 4–7 |
| IC4 | Lead QA Engineer | Cross-team quality standards; mentorship | Owns testing strategy across teams; sets automation standards; evaluates tooling; mentors junior QAs | 6–9 |
| IC5 | Staff / Principal QA Engineer | Company-wide quality strategy | Defines test architecture for the organization; thought leader on quality engineering; works with CTO-level on quality risk | 9+ |
QA Engineer management track
| Level | Title | Scope | Key differentiator |
|---|---|---|---|
| M1 | QA Tech Lead | Technical direction for QA team | Player-coach; drives technical quality standards; partial management of QA engineers |
| M2 | QA Manager | Team of 4–8 QA engineers | Manages QA team; owns quality metrics; partners with engineering management; hires and develops QAs |
| M3 | Director of QA | Full QA organization | Owns QA strategy; manages QA managers; partners with VP Engineering on quality risk and release standards |
How the QA Engineer career path progresses
A QA engineer career path moves from executing manual test cases to owning the automation frameworks and quality strategy a whole product depends on. Early QAs write and run test cases against a spec; by Senior the job is largely automation engineering, building the frameworks other engineers write tests against, and the path then forks between deepening technical automation craft or moving into QA team leadership.
- 1
Execute defined test cases
As a QA Engineer I, the work is manual and basic automation testing against an assigned set of test cases: writing them, running them, and filing bug reports engineers can act on without follow-up.
- 2
Build automation ownership
As a QA Engineer II, the QA starts automating tests for their assigned features and contributing to the team's existing frameworks, moving past manual execution alone.
- 3
Own test strategy for a product area
As a Senior QA Engineer or SDET, the job becomes designing the test strategy for a product area and building the automation frameworks that strategy runs on, working as a close partner to engineering rather than a downstream checker.
- 4
Take the automation or people fork
The path splits here. Lead QA Engineer stays IC, owning testing strategy and automation standards across several teams and evaluating new tooling. QA Tech Lead is the management entry point, a player-coach role driving technical quality standards while starting to manage QA engineers.
- 5
Reach the top of either track
Staff or Principal QA Engineer defines test architecture for the whole organization and works with CTO-level stakeholders on quality risk. QA Manager runs a team of 4 to 8 QA engineers, owning quality metrics and hiring.
- 6
Lead the QA organization
Director of QA owns QA strategy company-wide, manages QA managers, and partners with VP Engineering on release standards and quality risk at the org level.
Skills and competencies by level
Each level below lists the hard skills (tools, techniques, deliverables) and soft skills (judgment, communication, stakeholder handling) that typically distinguish it.
Entry (QA Engineer I-II)
Hard skills
- Test case design. Turns a feature spec into test cases that catch edge cases, not just the happy path.
- Bug report writing. Files a report with clear repro steps a developer can act on without asking follow-up questions.
- Automation scripting. Writes automated tests in the team's existing framework for assigned features.
- Regression suite execution. Runs the existing regression suite before a release and reads what the results actually mean.
Soft skills
- Clarifying ambiguous specs. Asks the feature owner instead of guessing what "working correctly" is supposed to mean.
- Methodical bug reproduction. Stays systematic when a bug won't reproduce instead of giving up or guessing at the cause.
- Constructive bug framing. Reports a defect in a way a developer can act on without it reading as an accusation.
- Coverage prioritization. Picks which cases matter most to test when there is not enough time to test everything.
Mid (Senior QA Engineer / SDET)
Hard skills
- Test strategy design. Decides what gets automated, what stays manual, and where testing effort pays off for a product area.
- Automation framework building. Builds and maintains the shared framework other QAs write their tests against.
- Flake triage. Tracks down whether a failing test is a real regression or a timing issue in the test itself.
- CI/CD test integration. Wires automated suites into the deployment pipeline so a real failure blocks a bad release.
Soft skills
- Engineering partnership. Works with developers on a feature's testability before it ships, not just after.
- Risk-based judgment. Decides where quality risk is highest and pushes back on scope when testing time is squeezed.
- Framework advocacy. Gets other engineers to adopt a new test pattern without mandating it top down.
- Debugging under pressure. Stays clear-headed isolating a failure the night before a release.
Senior (Lead QA Engineer / QA Tech Lead)
Hard skills
- Cross-team quality standards. Sets what "tested" actually means across several teams, not just their own.
- Tooling evaluation. Pilots a new testing tool and makes the call on whether it is worth rolling out company-wide.
- Release risk assessment. Reads test results across teams and makes the call on whether a release is safe to ship.
- Mentoring on test design. Reviews a junior QA's test plan and shows them the coverage gap they missed and why it matters.
Soft skills
- Standards buy-in. Gets teams that don't report to them to actually follow a new quality standard.
- Player-coach balance. Splits time between hands-on testing work and developing the QA engineers around them.
- Escalation judgment. Knows which quality risk needs to go to engineering leadership now versus wait for the next release.
- Difficult feedback delivery. Tells a team their release isn't ready without it turning into a fight.
Leadership (Staff/Principal QA, QA Manager, Director of QA)
Hard skills
- Test architecture strategy. Defines how testing should work across the whole engineering org, not just one product.
- Quality metrics ownership. Tracks and reports the metrics, like escaped defects and coverage, that show whether quality is improving.
- Hiring bar setting. Builds a QA team's hiring bar and interview process.
- Release standards governance. Sets the bar every team has to clear before a release ships.
Soft skills
- Executive-level framing. Explains quality risk to a CTO in terms of business impact, not raw test counts.
- Cross-org influence. Moves quality practice forward across teams with no direct authority over most of them.
- Org-wide accountability. Owns the outcome when a quality issue reaches production, even from a team they don't manage directly.
- Long-term quality vision. Sets a multi-quarter direction for how testing should evolve as the product grows.
Common questions
Frequently asked questions
Build your QA Engineer career framework in Harmny
Turn this career ladder into a live system — employees see their gap to the next level, and development goals connect directly to the framework.