Quality Assurance Track
Quality Assurance
Refuses to ship defects. Owns test strategy, defect lifecycle, and release sign-off. Prevention starts at requirements; detection ends at sign-off.
3levels
·
8competencies
·
Total weight 12.5
·
Hire bar QA2
The 3 QA levels
QA1
Junior
You ship:
Execute test cases · learn discipline
📚Runs prepared test cases
🐛Files reproducible bugs
🎯Paired with senior for sign-off
1.5 – 2.4
QA2
Middle
You ship:
Sole QA on a sub-team · one automation layer
🛠Owns test suite + defects
📊Maintains test reports
🔁Builds automation foundation
2.5 – 3.7
QA3
Senior · 2 sub-tracks
You ship:
Lead QA · Analyst (prevention) or SDET (automation framework)
🧭Gatekeeper for stage release
🎯2 sub-tracks: Analyst or SDET
📜Sets quality standards
3.8 – 5.0
Your journey:
QA1
QA2
QA3
Behaviors, not tenure. See the detail below.
Competency matrix — at a glance
Competency
W
QA1
QA2
QA3
Test Design & Coverage
×2
2
3
4
Test Execution & Defect Discipline
×2
2
3
4
Carefulness & Quality Rigor
×1.5
2
3
4
Reporting & Quality Metrics
×1.5
2
3
4
Test Automation & Tooling
×1.5
1
2
3
AI-Assisted QA
×1.5
1
2
4
Domain & Product Understanding
×1
1
2
4
Communication & Cross-team
×1.5
1
2
4
1 Aware2 Developing3 Proficient · hire bar4 Senior5 Expert
Competency deep-dive
Test Design & Coverage
Weight ×2
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I run the tests someone else wrote."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Executes test cases written by senior QA | ≥80% assigned cases executed per sprint | TestRail / Xray execution log |
| Coverage scope on assigned feature | Single feature, happy-path only | Jira ticket scope + TestRail run |
| Asks senior QA for clarification on ambiguous AC | ≥3 clarifying questions/refinement session | Refinement meeting notes / Slack thread |
| Files reflection notes after each test cycle | ≥1 learning note/week to mentor QA | Confluence mentor log |
| Zero solo sign-offs on releases | 100% sign-offs co-signed by senior QA | Release sign-off doc / QA gate log |
L2
"I can write test cases from a clear spec."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Writes test cases from clear spec independently | ≥70% sub-area cases authored by self | TestRail / Xray author field |
| AC coverage on owned sub-area | ≥95% AC mapped to test cases | AC-to-test traceability matrix |
| Applies boundary and equivalence techniques | ≥1 boundary/equivalence case per spec'd field | TestRail case design review |
| Edge and negative paths included per feature | ≥2 negative cases per user story | TestRail case tags / sprint review |
| Owns test plan for 1 sub-team | Sub-team of 3-5 devs, sole QA | Project org chart + Jira team config |
L3
"I design the test suite end-to-end. Edge and exception flows are not afterthoughts."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Owns test plans solo across owned scope | 100% owned-scope test plans authored solo | Confluence test plan author field |
| AC coverage across owned scope | ≥90% AC coverage on owned scope | AC-to-test traceability matrix |
| Risk-based prioritization documented per plan | 100% plans include documented risk-based priority | Confluence test plan risk section |
| Mixes ≥2 design techniques per release | ≥2 design techniques per release plan | Test plan technique log |
| Reviews juniors' test design | ≥80% junior cases reviewed before execution | TestRail reviewer field / Confluence review log |
L4
"I run the test strategy across the whole project."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Lead QA on project covering multiple workstreams | ≥1 project, 2+ workstreams covered | Project assignment + Jira component map |
| Risk-weighted coverage across modules | Top-3 risks ≥90% covered, documented per release | Confluence risk-weighted test plan |
| Shapes AC with BA before sprint commit | ≥80% stories show QA AC contribution | Jira AC edit history / refinement notes |
| Mixes exploratory, scripted, model-based techniques | ≥3 technique types deployed/release | Test plan technique log |
| Mentors mid-QAs on test design | ≥1 mid-QA mentored with documented 1:1s | Confluence mentor log |
L5
"I set the test design standard for the ODC."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Sets QA test design standard across ODC | Standard adopted by ≥2 PMs / projects | Confluence standards + adoption record |
| Coverage model reused across projects | ≥2 projects adopt the model/year | Confluence model + project plan references |
| Codifies technique playbook | ≥1 playbook, ≥3 techniques codified | Confluence technique playbook |
| Defines testability standard upstream | Standard adopted by ≥80% BAs/devs in ODC | Confluence testability standard + adoption |
| Multi-project / ODC test strategy ownership | Strategy covers ≥3 projects | ODC QA strategy doc |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Only runs scripts, never questions them
Tests only what spec literally says
Forgets negative and edge paths under deadline
Strategy on paper but team not following
Sets standards no one adopts
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
Test Execution & Defect Discipline
Weight ×2
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I run tests and report what I see."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Files reproducible bug reports with steps | ≥X bugs/sprint with clean steps (per sub-team baseline) | Jira bug ticket audit |
| Defect reports include environment + evidence | 100% bugs include env + screenshot/log | Jira bug template compliance |
| Hands off defects to senior QA after logging | 100% handoffs include context | Slack/Jira comment trail |
| Defers severity calls to senior QA | 100% severity decisions reviewed before send | Jira severity change history |
| Daily defect status reported in standup | 100% own defects raised same day in standup | Standup notes / Jira blocker flag |
L2
"I log clean, reproducible defects."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Triage SLA on P0/P1 defects | P0 ≤2h, P1 ≤6h | Jira defect status timestamps |
| Tracks own defects to closure (no drift) | Zero own defects aging >sprint without owner | Jira aging defect report |
| Proposes severity with rationale | ≥95% defects have severity rationale field | Jira defect template field |
| Closes own defect loop weekly | ≥95% defects updated/closed within 7 days | Jira weekly defect audit |
| Owns regression suite for sub-team | 1 sub-team regression suite owned end-to-end | TestRail / Xray suite ownership |
L3
"I own the defect lifecycle. No defect drifts without an owner."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Executes defects at all priority levels solo | 100% priority levels handled solo | Jira assignee + priority audit |
| Defect escape rate from owned scope | Defect escape rate <5% | Prod incident log vs scope mapping |
| Maintains regression suite up to date | Regression suite refreshed ≥1/sprint | TestRail / Xray suite version history |
| Median P1 resolution time on owned scope | Median P1 resolution ≤4 days | Jira cycle time report |
| Coaches L1/L2 QA on repro discipline | ≥1 QA coached/sprint with documented session | Confluence coaching log |
L4
"I drive triage. Defects move fast and cleanly."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Runs project-wide triage cadence | ≥2 triage sessions/week on project | Calendar + triage meeting notes |
| Project-wide aging defect dashboard maintained | ≥1 live dashboard, refreshed weekly | Jira dashboard URL |
| Coaches team on repro discipline | ≥2 mid-QAs coached/quarter with documented sessions | Confluence coaching log |
| Reviews and uplifts team's defect quality | ≥80% team defects reviewed before client visibility | Jira reviewer field / audit log |
| Defects move fast under their triage | Median P1 resolution ≤3 days project-wide | Jira cycle time report |
L5
"I set the defect lifecycle standard for the ODC."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Sets repro and defect quality standard ODC-wide | Standard adopted by ≥2 projects | Confluence standard + adoption |
| Lifecycle policy across projects | Policy adopted by ≥80% QA leads | Confluence policy + audit |
| Triage governance owned | Governance doc adopted, ≥2 PMs cite | Confluence governance doc |
| Org-wide flow metrics standard | ≥3 flow metrics (aging, MTTR, escape) standard across ODC | BI/Confluence flow dashboard |
| Cross-project defect root-cause analyses authored | ≥2 cross-project RCAs/year | Confluence RCA repository |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Logs vague 'doesn't work' tickets
Reproduces but doesn't own to close
Lets P3/P4 defects rot in backlog
Triage becomes a status meeting
Policy ignored by working teams
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
Carefulness & Quality Rigor
Weight ×1.5
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I follow the checklist."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Follows self-check checklist before marking Pass | 100% test cases checklist-verified | TestRail checklist field / mentor audit |
| Attaches evidence (screenshot/log) per test result | 100% results include evidence | TestRail attachment audit |
| Owns escapes from own assigned area | 100% own escapes acknowledged with learning note | Confluence escape log + mentor sign-off |
| Re-runs flagged regression list for own area | 100% flagged regression items executed pre-release | TestRail regression run log |
| Asks senior QA for second eye on risky claims | ≥1 second-eye request/week on risky paths | Slack / mentor log |
L2
"I double-check my own work."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Double-checks own work before sign-off | 100% Pass marks have re-check timestamp | TestRail execution history |
| Spots obvious mismatches against spec | ≥90% spec-vs-build mismatches caught pre-release | Defect log vs spec audit |
| Escape rate from owned sub-area | ≤5% defects escape to prod from owned area | Prod incident log vs sub-area mapping |
| Re-runs regression list per sprint | 100% regression list re-run before sprint close | TestRail sprint regression run |
| Audit-ready evidence on own work | 100% test artifacts pass mentor audit spot-check | Mentor audit log |
L3
"I never mark Pass on something I haven't verified. Always one more check."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Zero critical bugs missed in last 2 sprints | 0 critical bugs missed last 2 sprints | Prod incident log + sprint mapping |
| Audits own work systematically | 100% own deliverables self-audited before submit | Self-audit log / Confluence |
| Escape rate from owned scope | ≤3% defects escape from owned scope | Prod incident log vs scope mapping |
| Catches cross-feature interaction defects | ≥2 cross-feature defects caught/sprint | Jira defect tag analysis |
| Enforces evidence hygiene on owned work | 100% own artifacts audit-ready on spot-check | Mentor/lead audit log |
L4
"I catch the issues no one else thinks to test. Zero leakage is the goal."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Zero-leakage target on project | 0 P0/P1 leaks to prod over 2 consecutive releases | Prod incident log + release manifest |
| Curates living regression suite for project | Suite refreshed ≥1/sprint, ≤10% stale items | TestRail suite version history |
| Verifies team's risky claims before sign-off | 100% high-risk Pass marks audited | Mentor/lead audit log |
| Enforces evidence hygiene on team | ≥95% team artifacts audit-ready on spot-check | Project audit report |
| Sees issues others miss (subtle/cross-system) | ≥3 documented 'caught-by-lead' findings/release | Defect log notes / release retro |
L5
"I set the carefulness standard for the department."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Department zero-leakage culture | 0 critical leaks last 4 releases across ODC | Prod incident log ODC-wide |
| Sets self-check + hygiene bar across ODC | Bar adopted by ≥80% QA leads | Confluence standard + adoption |
| Regression strategy standard owned | Standard adopted by ≥2 projects | Confluence regression standard |
| Trains attention-to-detail as a skill | ≥1 training session/quarter, ≥5 QAs attend | HR training tracker + Confluence curriculum |
| Cross-project leakage analyses authored | ≥2 leakage RCAs/year with mitigations adopted | Confluence RCA + mitigation adoption |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Marks Pass without re-checking
'Works on my machine' thinking
Skips one more check under deadline
Tolerates leakage as inevitable
Carefulness becomes paperwork theater
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
Reporting & Quality Metrics
Weight ×1.5
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I fill the daily template."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Fills daily QA report template | ≥95% days reported on time | Daily report archive / Slack timestamps |
| Pass/fail counts reported per sprint | 100% sprints have pass/fail count | Sprint report archive |
| Defers report design to senior QA | 100% report changes reviewed before publish | Confluence edit history / mentor sign-off |
| Same template used regardless of audience | Uses approved template 100% of time | Report template compliance audit |
| Adds blockers + observations to daily template | ≥1 blocker/observation entry per day reported | Daily report content audit |
L2
"I write the sprint test report."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Writes sprint test report independently | ≥1 sprint test report/sprint | Sprint report archive |
| Reports include pass/fail + defect counts + blockers | 100% reports cover all 3 sections | Report template compliance |
| Adjusts tone for PM vs dev lead | ≥2 distinct report variants per sprint | Email/Confluence report archive |
| Maintains existing QA dashboard | Dashboard refreshed ≥1/week | Dashboard edit log |
| Daily signal PM can act on | ≥80% daily reports cited in PM standup decisions | Standup notes referencing QA daily |
L3
"My reports are the project's quality truth — for the PM and the client."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Weekly QA reports delivered on time | 100% weekly reports delivered on time | Weekly report archive / Slack timestamps |
| RCA on majority of defects | RCA on ≥80% defects | Jira RCA field / Confluence RCA log |
| Reports include trend + risk + coverage | 100% weekly reports cover all 3 dimensions | Confluence report template |
| Tailors reports to PM and dev lead | ≥2 tailored variants per release | Report archive variant log |
| Reports drive at least 1 decision/week | ≥1 PM decision/week cites QA report | Decision log / Standup notes |
L4
"I design how quality is seen across the project."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Designs project quality view / dashboard | ≥1 dashboard with ≥5 metrics, refreshed weekly | Confluence/BI dashboard URL |
| Metrics that drive action (trends + risk + coverage) | ≥3 actionable metrics live per project | Dashboard config + retro citation |
| Sprint quality story authored for client | ≥1 client-ready quality narrative/sprint | Client report archive |
| Exec-ready quality narrative authored | ≥1 exec narrative/release | Confluence exec brief archive |
| Coaches mid-QAs on reporting clarity | ≥2 mid-QAs coached/quarter with documented sessions | Confluence coaching log |
L5
"I set the reporting standard for the department."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Department sprint report template owned | Template adopted by ≥80% QA leads | Confluence template + adoption |
| Metric standard across projects | ≥5 standard metrics adopted by ≥2 projects | Confluence metric standard + dashboards |
| Reporting playbook by audience | Playbook covers ≥3 audiences (PM/client/exec), adopted ODC-wide | Confluence playbook + adoption |
| Visibility framework for department | Framework adopted, ≥2 PMs cite | Confluence framework + citation |
| Daily reporting standard ODC-wide | Standard adopted by ≥80% QA daily reporters | Daily report template compliance audit |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Template filled with no real signal
Reports activity, not quality
Hides bad news in report
Dashboards no one reads
Reporting standard nobody follows
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
Test Automation & Tooling
Weight ×1.5
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I run existing automation and read the report."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Runs existing automation suites and reads reports | 100% assigned runs executed and reports filed | CI run log / TestRail report |
| Reports flakes to senior QA with context | ≥95% flakes reported within 1 day of detection | Slack/Jira flake ticket trail |
| Reads automation code unaided | ≥1 code review participation/sprint as reader | GitHub/GitLab PR review log |
| Aware which tests run in CI | 100% recall of project CI pipeline in mentor check | Mentor verbal check |
| No framework ownership | 0 framework files owned (read-only contributor) | Git CODEOWNERS / mentor sign-off |
L2
"I add new tests to the existing framework."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Automation coverage on owned sub-area | ≥30% regression coverage automated | Coverage report / TestRail tag analysis |
| Adds new tests to existing framework | ≥5 tests/sprint added by self | Git commit log / PR author |
| Triggers suites on branches and reads pipeline | 100% PRs trigger relevant suite, results read | CI pipeline trigger log |
| Fixes assigned flaky tests | ≥80% assigned flakes resolved within sprint | Jira flake ticket close rate |
| Owns one automation layer (UI or API) | 1 layer owned end-to-end | CODEOWNERS / framework doc |
L3
"I own automation at one layer and keep it green."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Writes automation scripts solo | 100% owned-scope scripts authored solo | Git commit log / PR author |
| Automated regression coverage | ≥40% regression automated | Coverage report / CI metrics |
| Maintains automation framework | 100% owned framework files kept green | CI health dashboard / CODEOWNERS |
| Resolves flakes within sprint | ≥90% flakes resolved within sprint | Jira flake ticket close rate |
| Reviews juniors' automation PRs | ≥80% junior automation PRs reviewed | GitHub/GitLab PR reviewer stats |
L4
"I own the automation framework across UI, API, and performance."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Automation coverage on project | ≥80% regression coverage automated | Coverage report / CI metrics |
| Owns framework across UI + API (+ perf) | 2-3 layers owned end-to-end | CODEOWNERS / framework architecture doc |
| CI feedback time on regression suite | <15 min for PR gating suite | CI duration metrics |
| Flakiness rate driven toward zero | <5% flake rate sustained 4 sprints | CI flake dashboard |
| Reviews and refactors team automation code | ≥50% team PRs reviewed by self | GitHub PR reviewer stats |
L5
"I architect automation across multiple projects."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Authors automation framework module used cross-project | ≥1 framework module adopted by ≥2 projects/year | Git module usage + project README |
| Multi-project pipeline architect | ≥2 projects use pipeline templates authored | CI template repo + adoption |
| Reliability SLOs across ODC | SLOs (flake <3%, runtime, MTTR) adopted by ≥2 projects | Confluence SLO doc + dashboard |
| Coding standards for automation owned | Standards adopted by ≥80% QA automation engineers | Confluence standards + linter config |
| Sets pipeline standard org-wide | Pipeline standard adopted ODC-wide | CI template adoption audit |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Treats automation as black box
Copy-pastes patterns without understanding
Green suite that doesn't catch bugs
Framework so complex only owner can use it
Standard ignores project realities
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
AI-Assisted QA
Weight ×1.5
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I sometimes ask ChatGPT for test ideas."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Uses AI for test case drafting under supervision | 100% AI outputs reviewed by senior before use | Mentor review log / Confluence AI usage log |
| Single-line prompts logged for mentor review | ≥3 prompts/week logged | Confluence prompt log |
| Aware of hallucination risk (basic) | 100% AI outputs flagged as 'AI-drafted' in tickets | Jira/Confluence AI tag compliance |
| Files learning notes after AI usage | ≥1 reflection note/week | Confluence mentor log |
| Defers AI risk decisions to senior QA | 100% AI workflow changes reviewed before adoption | Slack/mentor sign-off trail |
L2
"I use AI to generate test cases and regression checklists."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Generates test cases and checklists with AI | ≥30% test cases AI-drafted on owned area | Confluence AI usage tag / TestRail tag |
| Spot-checks AI suggestions before commit | 100% AI outputs spot-checked, ≥1 verification note/output | Confluence verification log |
| Reuses prompt patterns | ≥3 reusable prompts in personal library | Confluence/Notion prompt library |
| Uses AI for one task type consistently | ≥1 daily workflow with AI integrated (e.g. case gen) | Daily AI usage log |
| Flags risky AI outputs explicitly | 100% risky outputs flagged with rationale | Confluence/Jira AI risk tag |
L3
"AI is part of my normal workflow — and I verify every output."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Uses AI for test case generation fluently | ≥60% test cases AI-assisted on owned scope | Confluence AI usage tag / TestRail tag |
| Productivity gain from AI | ≥30% productivity gain measured | Confluence AI savings log / time tracking |
| Reviews 100% of AI output | 100% AI outputs reviewed before use | Confluence verification log |
| Maintains personal prompt library | ≥10 reusable prompts in personal library | Confluence/Notion prompt library |
| Shares AI techniques with juniors | ≥1 knowledge-share session/sprint | Confluence knowledge-share log |
L4
"I design AI workflows for the QA team."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Designs AI workflows for team | ≥1 team workflow with AI integrated, ≥2 QAs adopt | Confluence workflow doc + adoption |
| Maintains prompt library for project | ≥10 prompts in shared library, ≥80% team usage | Confluence prompt library + usage analytics |
| Coaches team on verification discipline | ≥2 QAs coached/quarter with documented sessions | Confluence coaching log |
| Sets AI guardrails for team | Guardrail doc adopted by ≥80% project QAs | Confluence guardrail doc + adoption |
| AI-driven time savings tracked on project | ≥10h/week aggregate savings documented | Confluence AI savings log |
L5
"I set the AI-QA stack for the department."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Sets AI-QA stack for department | Stack adopted by ≥2 projects | Confluence AI stack doc + adoption |
| Verification standard ODC-wide | Standard adopted by ≥80% QA leads | Confluence verification standard + audit |
| Prompt engineering standard authored | Standard cited in ≥2 project libraries | Confluence prompt standard + citation |
| AI-QA stack adopted department-wide | ≥80% QAs in ODC use the stack | Adoption survey + tool license audit |
| AI risk policy for QA org owned | Policy adopted ODC-wide, ≥1 review/year | Confluence AI policy + review log |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Copies AI output into tickets
Uses AI for cases, skips verification
AI dependence dulls own thinking
Mandates AI tools team doesn't trust
Stack chosen by hype, not fit
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
Domain & Product Understanding
Weight ×1
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I recognize product names and main features."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Completes domain glossary / onboarding | 100% within 60 days of joining project | HR training tracker + mentor sign-off |
| Recognizes product names + features in spec | 100% recall in mentor verbal check | Mentor knowledge check log |
| Asks BA for everything domain-related | ≥3 BA questions/sprint logged | Slack/meeting notes BA channel |
| Files domain learning notes weekly | ≥1 note/week | Confluence learning log |
| Tests UI knowing the feature's intent | 100% test cases reference business intent in description | TestRail case description audit |
L2
"I understand the workflows; I test the main paths."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Uses domain terms correctly in defects + reports | ≥95% terms accurate per BA spot-check | BA review of defect language |
| Tests main domain workflows (not just screens) | ≥80% sub-area workflows covered end-to-end | TestRail workflow tag coverage |
| Catches obvious domain bugs (business-logic) | ≥3 domain bugs/sprint caught | Jira defect domain tag |
| Discusses cases with BA before finalizing | ≥80% cases reviewed with BA pre-execution | Confluence/Slack BA review trail |
| Reads spec + helpdesk tickets regularly | ≥2 helpdesk tickets read/week | Helpdesk read log / Confluence notes |
L3
"I design tests for real-world misuse, not just the spec."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Domain certification or equivalent | ≥1 domain certification or equivalent body of work | HR certification record / Confluence portfolio |
| Owns domain test design | 100% domain test design owned on scope | TestRail design author field / Confluence |
| Catches business-logic defects across workflows | ≥5 business-logic defects caught/sprint | Jira defect domain tag |
| Acts as domain reference for juniors | ≥3 junior consultations/sprint logged | Slack/meeting consultation log |
| Reads industry/regulatory updates monthly | ≥1 industry note/month | Confluence industry log |
L4
"I advise dev and BA on domain-specific quality risks."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Maps cross-system flows on project | ≥1 cross-system flow diagram authored/release | Confluence flow diagrams |
| Trusted domain advisor to dev/BA | ≥3 dev/BA consultations/quarter on domain risk | Slack/meeting notes consultation log |
| Designs for real-world misuse patterns | ≥2 misuse-pattern test sets/release | TestRail misuse-pattern tag |
| Mentors team on domain | ≥2 QAs mentored/quarter with documented sessions | Confluence mentor log |
| Studies competitors and regulations | ≥1 competitor/reg note/month | Confluence competitive intel log |
L5
"I co-pitch the domain in presales."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Domain risk framework for ODC owned | Framework adopted by ≥2 projects | Confluence framework + adoption |
| End-to-end domain model owned across projects | Model covers ≥3 projects, reused | Confluence domain model + reuse log |
| Co-pitches domain expertise in presales | ≥2 presales engagements/year | Sales/presales engagement log |
| Builds domain curriculum | ≥1 curriculum, ≥5 QAs trained/year | Confluence curriculum + training log |
| Authoritative domain voice across ODC | Consulted on ≥3 cross-project domain calls/quarter | Slack/meeting consultation log |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Tests UI without knowing what it does
Only tests the literal spec
Domain knowledge stays in head
Advises but team won't listen
Presales claims outrun reality
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
Communication & Cross-team Collaboration
Weight ×1.5
L1
1
L2
2
L3 · hire bar
3
L4
4
L5
5
L1
"I write what I see, simply."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Speaks up in own standup | 100% standups contributed to (not silent) | Standup notes / facilitator check |
| Writes simple, evidence-attached defects | 100% defects have evidence attachment | Jira defect template compliance |
| Accepts dev's severity call with senior review | 100% severity disputes routed to senior QA | Jira severity change history |
| Executes assigned tasks without scope drift | 100% tasks completed within assigned scope | Jira scope vs delivery audit |
| Internal team only (no client-facing solo) | 0 solo client comms | Email/Slack client comms audit |
L2
"I write clear defects and status notes."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Explains issues to dev clearly (verbal) | ≥90% issues resolved without re-explanation | Slack/meeting follow-up rate |
| Defect/status notes are clear and concise | ≥95% notes pass mentor clarity audit | Mentor audit log |
| States rationale for severity | 100% severity proposals include rationale | Jira severity rationale field |
| Trusted by own squad | ≥4/5 squad trust score in pulse survey | Squad pulse survey |
| Suggests improvements to senior QA | ≥1 improvement suggestion/sprint logged | Confluence improvement log / retro notes |
L3
"I run daily and sprint test reviews. I negotiate severity with evidence."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Weekly client demo presence | 100% weekly client demos attended | Calendar + meeting notes |
| Escalates blockers same day | 100% blockers escalated same day | Slack/Jira escalation timestamps |
| Substantive standup contributions | ≥3 substantive standup contributions/week | Standup notes / facilitator check |
| Negotiates severity with dev lead | ≥80% disputes resolved at QA-dev level | Escalation log resolution column |
| Writes client-readable status notes | ≥1 client-readable status note/week | Client report archive |
L4
"I'm trusted by client QA and PMs. I represent Techvify's quality posture."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Runs daily/sprint reviews + represents Techvify quality | ≥80% project quality reviews led by self | Calendar host + meeting notes |
| Resolves cross-team severity/priority disputes | ≥90% disputes resolved without escalation | Escalation log resolution column |
| Trusted by client leadership | ≥2 named client leaders with regular touchpoints | Calendar 1:1 series + CRM |
| Writing drives decisions | ≥3 written reports cited in PM/client decisions/release | Decision log / retro citation |
| Shapes project quality direction | ≥3 project quality decisions owned/release | Confluence decision log |
L5
"I open conversations on quality with executives."
Measurable indicators(pQA verification checklist)
| Indicator | Threshold | pQA source |
|---|---|---|
| Sets written standard for QA across ODC | Standard adopted by ≥80% QAs | Confluence standard + audit |
| Opens exec-level quality dialogue | ≥2 exec quality briefings/year | Exec briefing log |
| Negotiation playbook for QA owned | Playbook adopted by ≥2 projects | Confluence playbook + adoption |
| Trusted at executive level | ≥3 exec-initiated quality consultations/quarter | Email/Slack exec consultation log |
| Shapes department quality strategy | Contributes to ≥1 ODC quality strategy/year | Confluence ODC strategy doc |
Anti-signal & scoring rule3-of-5 majority
Dimension
L1 · Aware
L2 · Familiar
L3 · Proficient
L4 · Advanced
L5 · Expert
Anti-signal · auto-disqualifies the level
Rejects
Silent in meetings, vague in writing
Reports issues without evidence
Wins arguments but loses trust
Becomes client's mouthpiece, not Techvify's voice
Influence dependent on title, not credibility
Scoring rule: You are at Level N if you hit Level N in at least 3 of 5 dimensions, AND no dimension is below Level (N−1). Sort levels descending — the 3rd value is your overall level. If the lowest drops more than 1 below, demote 1 level.
How to advance — promotion criteria
QA1QA2
Typical 18–24 monthsWhat to demonstrate
- L3 in Design, Execution, Carefulness, Reporting
- L2+ in Automation, AI-QA, Communication
- Sole QA on a sub-team for 2+ sprints
Portfolio (CORE)
- 2 test plans with risk-based coverage
- 1 release sign-off doc with evidence
- Defect log showing severity discipline
Verification path
1Self-assess + supervisor calibration
2Submit portfolio
3Annual review sign-off
QA2QA3
Choose Analyst or SDET sub-trackWhat to demonstrate
- Analyst: L4 in 6/8 + L5 in Carefulness + L4+ in Reporting
- SDET: L4 all 8 + L5 in Automation + framework adopted on a project
- Owned strategy + sign-off for ≥2 releases
Portfolio (CORE)
- Test strategy docs from 2 releases
- Sign-off + evidence trail
- Automation framework PR (SDET) OR Prevention case study (Analyst)
Verification path
1Declare preferred sub-track
2Multi-reviewer calibration
3ODC Lead + Head of D3 sign-off
Alternative sub-track at QA3
QA3 · Analyst
Manual-heavy, prevention-focused. Strong on requirements-side quality, exploratory testing.
When to consider
- Your strength is test design + exploratory + prevention
- You read BRDs early and shape testability
- You're not driven by automation framework ownership
Automation required
L3
Comp parity
Same band
QA3 · SDET
Automation-heavy. Owns and evolves the test automation framework across UI/API/perf/CI.
When to consider
- You love framework design and tooling
- You're effective writing code, debugging flakes, building CI
- You want to scale quality through automation, not headcount
Automation required
L5
Comp parity
Same band
How to choose / switch sub-tracks
1. Declare during grandfathering window2. 1-on-1 with supervisor3. 1-cycle trial4. Confirm at next quarter
FAQ for QA role
FAQ items will be added as questions surface from the team.
Self-assessment
Self-assess your QA level
Score yourself on each dimension and get a live radar chart of your competency profile. Scores stay in your browser — never saved or shared.