5.2The Three Major Tracks
Track 1: Individual Contributor (IC)
The IC track is for people who want to keep doing the work directly -- testing, building automation, designing test strategies -- rather than managing people.
| Level | Title (Typical) | Scope | Key Responsibilities |
|---|---|---|---|
| IC1 | Junior QA Engineer | Single feature, guided | Execute test cases, learn the product, file bugs, write basic automation |
| IC2 | QA Engineer | Multiple features, independent | Design test plans, build and maintain automation, participate in sprint ceremonies |
| IC3 | Senior QA Engineer | Full product area, influencing | Define test strategy for a team, mentor juniors, drive quality improvements, contribute to architecture |
| IC4 | Staff QA Engineer | Multiple teams, organizational impact | Set quality standards across teams, design test infrastructure, influence engineering-wide practices |
| IC5 | Principal QA Engineer | Organization-wide, strategic | Define the company's quality vision, evaluate and adopt new technologies, represent QA in executive decisions |
The jump from IC3 to IC4 is the hardest. It requires shifting from "I am excellent at my team's quality" to "I make multiple teams better at quality." This means working through influence rather than direct execution.
Track 2: Management
The management track is for people who want to amplify quality through people -- hiring, mentoring, process design, and organizational strategy.
| Level | Title (Typical) | Scope | Key Responsibilities |
|---|---|---|---|
| M1 | QA Lead | One team (3-6 people) | Technical leadership, sprint-level planning, mentoring, hands-on testing and automation |
| M2 | QA Manager | Multiple teams (6-15 people) | Hiring, performance management, process design, cross-team coordination |
| M3 | Director of QA | QA organization (15-50 people) | Strategy, budget, tooling decisions, executive reporting, organizational design |
| M4 | VP of Quality | Company-wide quality | Quality vision, board-level reporting, vendor management, quality culture across the company |
The QA Lead role is a hybrid. You are still doing hands-on technical work, but you are also responsible for the team. As you move to QA Manager and above, the hands-on work decreases and the people/strategy work increases. Many engineers move to QA Lead and realize they miss the technical work -- that is a signal to stay on the IC track.
Track 3: Specialist
Specialist tracks are for people who want to go deep in a specific area of quality engineering.
| Specialization | Focus | Typical Title |
|---|---|---|
| Test Automation | Framework design, tooling, CI/CD integration | Automation Architect, SDET |
| Performance Engineering | Load testing, profiling, capacity planning, SRE overlap | Performance Engineer, Reliability Engineer |
| Security Testing | Penetration testing, vulnerability assessment, compliance | Security Tester, Application Security Engineer |
| Accessibility Testing | WCAG compliance, assistive technology testing, inclusive design | Accessibility Specialist, Accessibility Engineer |
| Mobile Testing | Platform-specific testing, device farms, mobile CI/CD | Mobile QA Engineer, Mobile Test Architect |
| AI/ML Testing | Model validation, data quality, bias detection | ML Test Engineer, AI Quality Engineer |