magnus919_agent-skills/qa-methodology/references/qa-career-levels.md

QA Career Levels: Senior → Staff → Principal

Scope-Progression Model

Career progression in QA engineering follows the same scope ladder as general software engineering. The differentiator between levels is scope of influence, not years of experience or technical depth alone.

Scope Tier	Definition	QA Example
Task	Complete a well-defined assignment	Write test cases for one API endpoint
Feature	Own quality for a feature end-to-end	Design test strategy for checkout v2
Project	Coordinate quality across a project with multiple features	Lead QA for a platform migration
Product	Influence quality across multiple teams on one product	Define org-wide flake policy; set test architecture standards
Org	Shape quality engineering direction across the organization	Multi-year QE vision; industry presence; hiring bar ownership
Department	Influence beyond engineering (product, support, compliance)	Company-wide reliability culture; regulatory quality frameworks

Level-to-Scope Mapping

Level	Primary Scope	Key Distinction
Senior QA Engineer	Project	Operates autonomously within a project; others ask for help
Staff QA Engineer	Product	Multi-team influence without authority; sets direction others follow voluntarily
Principal QA Engineer	Org	Multi-year QE vision, public presence, shapes hiring standards and org strategy

Gotcha — "Engineer 2.5" trap: Performing at the very top of your current level (e.g., an excellent Senior doing Senior work brilliantly) is NOT the same as operating at the next level. Promotion requires demonstrated scope at the NEXT level, not excellence at the current one. Many strong Seniors stall here: they are "Senior+" but haven't crossed into product-scope influence.

Leveling Mechanics

How Promotion Works

Promotion is recognition that you are already operating at the next level's scope — not a reward for tenure or a motivation tool.

1. Demonstrate next-level scope for a sustained period (typically 2–4 quarters)
2. Gather evidence from multiple teams/stakeholders showing impact beyond your current scope
3. Sponsor (usually your manager) builds the case with your evidence
4. Calibration across peers at the target level confirms the scope match

QA ↔ General Engineering Level Mapping

QA Title	General Engineering Equivalent	Scope Expectation
QA Engineer I/II	SDE I/II	Task → Feature
Senior QA Engineer	Senior SDE	Project
Staff QA Engineer / SDET	Staff SDE	Product
Principal QA Engineer / Test Architect	Principal SDE	Org
QE Director / Fellow	Director / Distinguished Engineer	Department+

This mapping matters because it determines compensation bands, review calibration pools, and cross-functional influence expectations.

Role Archetypes

Staff-Level Archetypes (per Will Larson, Staff Engineer, 2020)

Archetype	Description	QA Manifestation
Team Lead	Guides a team's technical direction while staying hands-on	QA lead embedding quality practices in a product team
Architect	Sets technical direction across multiple teams	Test infrastructure architect; framework standards owner
Solver	Drops into hard problems, fixes them, moves on	Reliability firefighter; flake-hunter across teams
Right Hand	Extends a leader's attention; delegates authority	QE partner to VP Eng; owns quality org initiatives

QA-Specific Role Archetypes

Role	Focus	Typical Level Range
QA Engineer	Manual + exploratory testing, domain expertise	Junior → Senior
SDET (Software Development Engineer in Test)	Test infrastructure as product; coding-first	Senior → Principal
Test Automation Engineer (TAE)	Automation design and maintenance	Junior → Staff
Quality Coach	Embeds quality culture in dev teams; no direct test execution	Staff → Principal
Test Architect	Cross-team test strategy, tooling, standards	Staff → Principal
Google TE/SET (Test Engineer / Software Engineer in Test)	Hybrid: product development + test tooling (Google's model)	Senior → Staff

For SDET competency details, see sdet-engineering.md.

Misconceptions

"QA is Dead"

Claim: AI and developer-owned testing eliminate the need for QA roles.

Reality: The role evolves, not disappears. Organizations that dissolved dedicated QA (e.g., some early Spotify-model teams) reinstated quality engineering functions within 2–3 years when defect escape rates climbed. AI increases test generation volume but does NOT replace quality judgment, risk assessment, test strategy, or the independence principle. The demand shifts from "test executor" to "quality engineer" — higher-scope, more technical.

"The QA career ladder is flat"

Claim: QA has no growth path beyond "senior tester."

Reality: QA maps directly onto the general engineering ladder (see mapping above). Staff and Principal QA roles exist at Google, Microsoft, Amazon, Netflix, and Atlassian. The perceived flatness comes from companies that fail to define the scope expectations for QA at Staff+ levels, not from an inherent ceiling.

"More tests = more quality"

Claim: Writing more tests always improves quality.

Reality: Test count is a vanity metric. A suite of 10,000 assertions that never catch a regression provides zero quality value. Quality comes from the RIGHT tests (risk-based, targeting escaped-defect patterns) with strong assertions (validated by mutation testing). See quality-gates-and-metrics.md for vanity-vs-actionable metrics.

Actionable Usage Guidance

Promotion-Packet Guidance (Senior → Staff Example)

Step 1: Gather scope evidence. Collect artifacts demonstrating product-scope (multi-team) impact:

• Test strategy documents adopted by 2+ teams
• Framework/infrastructure contributions used org-wide
• Mentoring records (engineers you've leveled up outside your team)
• Cross-team incident postmortems you led or contributed to
• Conference talks, internal tech talks, or published writing

Step 2: Structure the packet.

Section	Content	Evidence Type
Scope summary	One paragraph: "I operate at product scope by..."	Narrative
Technical impact	3–5 bullets with metrics (flake rate reduced X%, CI time cut Y%)	Data
Multi-team influence	Teams influenced, mechanisms (guilds, standards, reviews)	Peer feedback
Direction setting	Standards/strategies you authored that others adopted	Documents
Mentorship	Engineers coached, their growth outcomes	Testimonials

Step 3: Map to next-level expectations. Each piece of evidence must answer: "How does this demonstrate PRODUCT-scope influence without authority?" If it only shows excellence within one project, it's Senior-level evidence, not Staff-level.

Level-Calibrated Growth Advice

Current Level	To Reach Next Level	Concrete Actions
Senior → Staff	Demonstrate product-scope influence	Author a cross-team test standard; lead a quality guild; own flake policy for 3+ teams; contribute to another team's test architecture
Staff → Principal	Demonstrate org-scope vision	Define 2-year QE roadmap adopted by leadership; establish hiring bar for QE; represent the org externally (talks, standards bodies); resolve a systemic quality failure spanning 4+ teams
Principal → Director/Fellow	Department influence + strategy	Shift from technical to organizational: budget ownership, headcount strategy, cross-department quality programs

Role-to-Level Mapping Procedure

Given a job description or team charter, determine the appropriate level:

1. Identify the scope of impact the role requires (task/feature/project/product/org)
2. Check authority vs. influence: Does the role manage people (→ Team Lead track) or influence without authority (→ Architect/Solver/Right Hand track)?
3. Map scope to level using the table above
4. Validate against leveling mechanics: Does the role require demonstrated evidence at that scope? If a "Staff QA" posting only describes project-scope work, it's misleveled.

If the role description says...	Scope tier	Likely level
"Write and maintain tests for feature X"	Task/Feature	QA Engineer I/II
"Own quality strategy for the payments project"	Project	Senior
"Define test standards adopted by all product teams"	Product	Staff
"Set 3-year quality vision; represent company in industry"	Org	Principal

Decision Table: When to Apply This Reference

Situation	Use This Reference For	Exit Condition
Writing a promotion packet	Evidence structure + scope mapping	Packet has ≥3 product-scope evidence items mapped to next-level criteria
Leveling a new role/position	Role-to-level mapping procedure	Role mapped to a scope tier with documented justification
Career growth planning	Level-calibrated growth advice	2–3 concrete next-level actions identified for current level
Evaluating team quality org design	Archetype + scope model	Each QE role mapped to archetype + scope tier

Exit condition: You are done applying this reference when you can state the target level's scope tier, map ≥3 pieces of evidence to that tier, and identify the gap (if any) between current and target scope.

Worked Example: Senior → Staff Promotion Packet

Context: Maria is a Senior QA Engineer on the Checkout team. She wants to reach Staff.

Evidence she gathered:

Evidence	Scope Demonstrated
Authored the org-wide flaky-test quarantine policy, adopted by 4 teams	Product (multi-team standard)
Built shared Playwright component library used by 3 product teams	Product (shared infrastructure)
Led quality guild (12 members, biweekly) for 3 quarters	Product (direction setting)
Mentored 2 junior QAs to Senior level (one on another team)	Product (multi-team growth)
Reduced org-wide CI flake rate from 8% to 2.3%	Product (measurable cross-team impact)

Assessment: Maria demonstrates product-scope influence without authority (no direct reports on other teams). Her evidence maps cleanly to Staff expectations. Packet is ready for sponsor review.

Composition Links

• SDET competency model and career progression: sdet-engineering.md
• Quality metrics (vanity vs actionable): quality-gates-and-metrics.md

---

Sources: Will Larson, Staff Engineer (2020), staffeng.com; endoflineblog.com career-leveling frameworks; Google Testing Blog (TE/SET model, testing.googleblog.com); Angie Jones, "Test Automation Career Path" (angiejones.tech, 2021); DORA State of DevOps Reports (quality-engineering role evolution).