United Kingdom · Technology and data · Principal/Manager (12-16 years)

QA Manager / Principal SDET

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Start my QA Manager / Principal SDET plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Upskilling a team in this role? Talk to us

Experience bandPrincipal/Manager (12-16 years)
Direct reports10-25 reports
Reports toDirector of Quality Engineering
UK framework levelUsually someone running a function, or a director

Also advertised as Quality Engineering Manager · Lead Quality Assurance Manager · Principal Software Development Engineer in Test

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

EAL Level 4 Diploma in Engineering and Advanced Manufacturing (Development Competence) Excellence, Achievement & Learning Limited · Level 4 · covers 5 of 10 standards

EAL Level 4 NVQ Diploma in Engineering Manufacture Excellence, Achievement & Learning Limited · Level 4 · covers 2 of 10 standards

EAL Level 4 NVQ Extended Diploma in Engineering Manufacture Excellence, Achievement & Learning Limited · Level 4 · covers 2 of 10 standards

EAL Level 4 Diploma in Rail Engineering Advanced Technician Competence Excellence, Achievement & Learning Limited · Level 4 · covers 1 of 10 standards

IAO Level 5 Diploma in Leadership and Management Innovate Awarding · Level 5 · covers 1 of 10 standards

City & Guilds Level 3 NVQ Extended Diploma in Engineering Technical Support City & Guilds Limited · Level 3 · covers 5 of 10 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Engineering software testing EAL Level 4 Diploma in Engineering and Advanced Manufacturing (Development Competence)

Implement Quality Assurance Methods and Procedures EAL Level 4 NVQ Diploma in Engineering Manufacture

Managing quality and quality systems IAO Level 5 Diploma in Leadership and Management

Testing Engineering Software City & Guilds Level 3 NVQ Extended Diploma in Engineering Technical Support

The future skills this job leans on

AI Fluency working with AI as a thinking partner

Data Fluency turning numbers into a decision

Automation Fluency building AI into how work runs

Sustainability Fluency building care for people and planet into the work

Foresight Fluency seeing round the corner

Start my QA Manager / Principal SDET plan, free

Your Plan Illustration

Built for QA Manager / Principal SDET

4 units that map to this job, from the qualifications that cover it.

Engineering software testing Excellence, Achievement & Learning Limited · covers 5 of 10 standards Level 4
Implement Quality Assurance Methods and Procedures Excellence, Achievement & Learning Limited · covers 2 of 10 standards Level 4
Managing quality and quality systems Innovate Awarding · covers 1 of 10 standards Level 5
Testing Engineering Software City & Guilds Limited · covers 5 of 10 standards Level 3

These are the real units behind this job, in the order they rank for it. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

2AI and this work

Will AI change your work as a QA Manager / Principal SDET?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

AI-Driven Test Orchestration & Optimisation
Observability-Driven Testing (ODT)

Why each one is rising

The future skills this job leans on

AI Fluencyworking with AI as a thinking partner
Data Fluencyturning numbers into a decision
Automation Fluencybuilding AI into how work runs
Sustainability Fluencybuilding care for people and planet into the work
Foresight Fluencyseeing round the corner

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your QA Manager / Principal SDET plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my QA Manager / Principal SDET plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

A QA Manager or Principal SDET sets testing standards and leads a team responsible for software quality. The role involves defining testing strategy, coaching testers, and making quality part of how software gets built, rather than testing individual features alone.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Jira (with Xray or Zephyr plugins) Strategic

Defining enterprise-wide standards for test management, reporting, and defect tracking within Jira. Designing custom workflows for complex bug lifecycles and integrating test results from various automation frameworks. You'll be the go-to person for optimising our use of Jira for quality.

Cypress / Selenium WebDriver Architect

Selecting and evolving the primary UI automation framework for the organisation. Designing the overall test architecture for UI automation, including best practices for component reusability, reporting, and integration into CI/CD. You won't be writing every script, but you'll set the technical direction and standards.

Postman / Insomnia Strategic

Defining the API testing strategy for your product area, including contract testing, service virtualisation, and performance testing at the API layer. You'll ensure your team is using these tools effectively for comprehensive API validation and automation.

Apache JMeter / k6 Strategic

Owning the non-functional testing strategy for your domain, including performance, load, and stress testing. Setting performance budgets, service level objectives (SLOs), and ensuring your team has the capabilities to design, execute, and analyse complex performance tests.

Jenkins / GitLab CI (and Git) Architect

Designing and optimising the entire CI/CD pipeline for quality gates, efficient feedback loops, and automated test execution. You'll ensure our automated tests run reliably and provide fast, actionable results, integrating quality checks seamlessly into the development process. You'll also set standards for Git usage for your team.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choice	Coming in	Where you are now	The step above
Technical Approach & Tooling	Follows prescribed tools and methods; escalates deviations.	Chooses appropriate tools/methods for routine tasks within established frameworks.	Proposes and implements new tools/methods for specific projects; influences team standards.
Budget Allocation	No budget authority; requests resources from supervisor.	Manages small project budgets (e.g., £1K-£5K for specific tools/training) with manager approval.	Recommends budget for specific projects up to £20K; consults on larger departmental budgets.
Hiring & Performance Management	No authority; provides feedback on interviews.	Participates in interviews; provides input on performance reviews.	Leads interviews; makes recommendations for hiring junior roles; mentors new joiners.
Release Readiness & Quality Gates	Reports test results; highlights blocking issues to supervisor.	Recommends go/no-go for features based on test results; flags critical bugs.	Makes go/no-go recommendations for specific features or minor releases; negotiates bug deferrals with Product.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Cost of Quality (CoQ) Ratio

This looks at how much we spend on preventing defects versus how much it costs us to fix them once they're found (especially in production). It's about being smart with our quality investment.

Target · Improve CoQ ratio by 15-20% year-over-year, shifting spend from failure costs to prevention costs.

If Q1's CoQ ratio was 1:3 (one unit spent on prevention for three units on failure), your target would be to get it to, say, 1:2.5 or better by Q1 next year by investing more in automation and shift-left activities.

Mean Time to Resolution (MTTR) for Production Defects

How quickly we fix major issues that slip into production. Your team's ability to provide clear, actionable bug reports and support developers in reproduction and verification directly impacts this.

Target · Reduce average MTTR for critical/high severity production incidents by 25% within 12 months.

If our average MTTR for a critical bug was 4 hours last quarter, you'd aim to get that down to 3 hours or less by streamlining our bug triage, reporting, and verification processes.

Release Cadence & Stability

How frequently we can confidently release new features to customers without introducing significant regressions or downtime. This is a big one, showing how well your quality gates are working.

Target · Enable a 20% increase in deployment frequency (e.g., from bi-weekly to weekly) for your product area while maintaining or improving production uptime (e.g., 99.95% to 99.98%).

Successfully moving from a bi-weekly release cycle to a weekly one for your core service, with no increase in critical production bugs over a 6-month period, would be a clear win here.

Team Automation Coverage & Reliability

The percentage of our codebase covered by automated tests (UI, API, unit) that are actually stable and provide quick feedback. It's not just about the number, but the *quality* of the automation.

Target · Increase automation coverage for your team's primary services from 60% to 80% within 12 months, reducing flaky test rates to below 2%.

Your team successfully adds automated API tests for all new endpoints, bringing API test coverage from 70% to 90% and reducing the number of 'red' builds caused by flaky tests by half.

Team Effectiveness & Morale

How well your team works together, their individual growth, and their overall job satisfaction. A happy, effective team is a productive team, simple as that.

Regular positive feedback from direct reports (e.g., through 1-on-1s and engagement surveys). Your team members are actively mentoring each other and taking on new challenges. You see a low attrition rate within your team, and they're hitting their personal development goals.

Strategic Influence & Collaboration

Your ability to shape quality strategy, influence engineering practices, and build strong relationships with Product and Engineering. You're not just a manager; you're a strategic partner.

You're consistently invited to early-stage product design and engineering architecture discussions. Your input is actively sought on release readiness decisions. You're seen as a trusted advisor by your peers and leadership, and you're able to drive quality initiatives across teams without direct authority.

Talent Development & Mentorship

How effectively you're growing the skills and careers of your direct reports, preparing them for their next steps.

You've successfully coached team members into more senior roles or new specialisations. Your team members have clear development plans that are regularly reviewed and acted upon. You're actively creating opportunities for your team to learn new technologies and take on leadership responsibilities.

Process Optimisation & Innovation

Your knack for identifying bottlenecks in our quality processes and implementing smart, effective improvements.

You've led initiatives that have demonstrably improved our testing efficiency or effectiveness (e.g., introduced a new tool, streamlined a workflow). Your team is experimenting with new testing techniques or technologies. You're regularly sharing insights and improvements with other QA teams.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy

Building High-Performing Teams

You'll spend time coaching individual team members, helping them unblock technical challenges, and designing career development plans. You'll celebrate team successes and learn from failures together. Seeing your team grow and deliver exceptional work will be a major driver.

A junior QA engineer you've mentored for a year successfully leads a complex automation project, and you feel a real sense of pride in their development.

Driving Systemic Quality Improvement

You'll be looking for patterns in bug reports, analysing root causes, and proposing changes to our development lifecycle to prevent issues from recurring. This means working with engineering leads to implement better coding standards, or with product to refine acceptance criteria. It's about fixing the machine, not just its output.

After a series of similar bugs, you identify a gap in our API contract testing. You then lead the initiative to implement a new framework that prevents these bugs before they even hit QA.

Strategic Technical Leadership

You'll be involved in high-level discussions about product architecture, technology choices, and release strategies. You'll be the voice of quality, making sure that technical decisions consider testability, reliability, and maintainability. You'll get to shape the technical direction of your area.

You successfully advocate for a new performance testing tool that becomes a standard across the entire engineering department, significantly improving our ability to scale.

What frustrates people

Organisational politics around release schedules and quality compromises.
Budget limitations preventing investment in crucial tools or headcount.
Dealing with the aftermath of production incidents, even when your team did everything right.
The constant challenge of hiring and retaining top QA talent in a competitive market.
Legacy systems that are incredibly difficult and time-consuming to test effectively.
Having to repeatedly educate non-technical stakeholders on the importance and complexity of quality assurance.

What this role does not give you

A quiet, heads-down coding environment for the majority of your day.
Complete autonomy without needing to justify decisions to senior leadership or collaborate with other teams.
A role where you're solely focused on individual technical contributions without people management responsibilities.
An environment where quality is always the top priority, regardless of business pressures or deadlines.

8Who you work with

You'll directly influence the reliability and user satisfaction of our core products, which directly impacts customer retention and our brand's reputation. Your decisions about team structure, tooling, and quality gates will shape the efficiency of our entire development lifecycle, affecting everything from engineering velocity to operational costs. Essentially, you're a guardian of our product integrity and a key enabler of our growth.

Inside the business

Director of Quality Engineering
Product Managers and Product Leads
Engineering Managers and Technical Leads
Other QA Managers (for cross-team alignment)
Head of Engineering / CTO

Outside the business

Key vendors for testing tools or services
Industry peers (for best practice sharing)
Select strategic customers (for feedback loops)

9What you need before you start

Not a wish list. The things you would be expected to already have.

Proven experience as a Senior QA Engineer or Staff QA Engineer, having owned complex test automation frameworks and driven significant quality improvements at a project level.
Deep expertise in at least one major UI automation framework (e.g., Cypress, Selenium) and one API testing tool (e.g., Postman) with a track record of building robust, scalable automation.
A solid understanding of CI/CD pipelines and how to integrate automated tests effectively to provide rapid feedback to developers.
Demonstrated ability to mentor junior engineers, conduct code reviews, and contribute to team-wide best practices.
Strong analytical skills, capable of performing detailed root cause analysis and understanding complex system interactions.
Excellent communication skills, both written and verbal, with the ability to articulate complex technical issues clearly to both technical and non-technical audiences.

10What to practise next

Where the job is going, and what to do about it starting this week.

Advanced Security Testing Integration

Security is no longer an afterthought; it needs to be an integral part of our quality process from day one. As threats evolve, our testing needs to become more sophisticated, moving beyond basic scans to integrated, continuous security validation. This is critical within 6-12 months.

Integrating SAST (Static Application Security Test · Understanding common attack vectors and how to mod · Penetration testing fundamentals and working with · Supply chain security for third-party libraries an · Threat modelling for new features and architecture

This month: Complete an online course on OWASP Top 10 and common web application vulnerabilities.
Next quarter: Work with our security team to understand their tools and processes; identify integration points for QA.
Month 6: Implement basic security scanning (e.g., dependency checks) into your team's CI pipeline.
Month 9: Coach your team on how to write security-focused test cases for new features.

Quick win: Ensure all new features have at least one test case specifically designed to check for a common security vulnerability (e.g., SQL injection, XSS).

Distributed System Testing & Resilience Engineering

Our systems are becoming increasingly distributed (microservices, cloud-native). Testing these complex, interconnected systems requires new strategies that focus on resilience, fault tolerance, and end-to-end transaction integrity across multiple services. This is important within 12-18 months.

Contract testing between microservices (e.g., Pact · Service virtualisation and mocking for complex dep · Chaos engineering experiments to test system resil · End-to-end trace analysis for distributed transact · Testing for eventual consistency and data integrit

This quarter: Research tools and methodologies for contract testing and service virtualisation.
Next quarter: Identify a critical microservice interaction and implement contract testing for it.
Month 6: Lead a 'game day' or chaos engineering experiment with a small, non-critical service.
Month 9: Develop a strategy for end-to-end testing that accurately reflects distributed system behaviour.

Quick win: For any new microservice, ensure there's a clear contract defined (e.g., OpenAPI spec) and that your team is testing against it rigorously.

11Staying current once you are in

What people here do to keep up

Regularly attending industry conferences and meetups (e.g., EuroSTAR, Agile Testing Days) to stay current with trends and network with peers.
Contributing to open-source testing frameworks or tools, or writing technical blogs about quality engineering best practices.
Participating in leadership development programmes or executive coaching to refine your management and strategic thinking skills.
Mentoring junior QA engineers or acting as a guest lecturer/speaker at local universities or bootcamps.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

AI-Driven Test Orchestration & Optimisation

AI isn't just generating tests; it's getting smarter about how and when to run them. Tools are emerging that can analyse code changes, user behaviour, and historical test failures to intelligently select the most impactful tests to run, reducing feedback cycles and optimising resource use. This is critical within 12 months.

Predictive test selection based on code changes (e
Risk-based testing prioritisation informed by AI m
Automated failure analysis and root cause suggesti
Dynamic test environment provisioning based on tes
Self-healing test automation (e.g., auto-updating

Observability-Driven Testing (ODT)

Testing is shifting from 'did it break?' to 'how is it performing in production?'. ODT uses production telemetry (logs, metrics, traces) to inform and validate testing efforts, allowing for more realistic test scenarios and quicker feedback loops. This is becoming important within 18 months.

Integrating testing with APM (Application Performa
Using production data to generate realistic test d
Synthetic monitoring and real user monitoring (RUM
Chaos engineering principles to test system resili
Proactive identification of performance degradatio

13What you’ll use

What you’ll use

Skills this role draws on

Technical

Agile/Scrum Methodologies (Optimisation & Implementation)
Test Case Design & Management (Strategic Frameworks)
Bug Triage & Root Cause Analysis (Leadership & Process)
Regression Testing Strategy (Optimisation & Automation)
Exploratory Testing (Championing & Coaching)
Shift-Left Testing Principles (Driving Organisational Adoption)

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

1
From Staff QA Engineer
Typically 2-4 years as a Staff QA Engineer.
Skills to master
- As a Staff QA, you'd have mastered complex automation, owned significant technical initiatives, and started mentoring. To move to Manager, you'd need to develop stronger people leadership, strategic planning, and cross-functional influence skills.
You're ready to move on when
- Successfully led a major test automation framework overhaul or implementation.
- Consistently mentored 2-3 junior engineers with demonstrable impact on their growth.
- Proactively identified and solved systemic quality issues across multiple projects.
- Demonstrated ability to influence technical decisions beyond your immediate team.
2
From Lead QA Engineer (Team Lead)
Roughly 2-3 years leading a small team (3-5 people).
Skills to master
- You'd already have some people management experience. The jump to Manager means scaling that up, managing managers (potentially), owning a larger P&L, and taking on broader strategic responsibility for an entire product area.
You're ready to move on when
- Successfully managed a small team, including performance reviews and development plans.
- Owned the quality strategy for a specific feature or component end-to-end.
- Consistently delivered high-quality releases with your team.
- Actively participated in hiring and onboarding for your team.
3
From Principal SDET (Individual Contributor Path)
Around 3-5 years as a Principal SDET.
Skills to master
- As a Principal SDET, you're a top-tier technical expert. To move into management, you'd need to shift your focus from individual contribution to enabling others, developing strong coaching and delegation skills, and embracing the strategic and administrative aspects of leading a team.
You're ready to move on when
- Architected and implemented complex, enterprise-level test automation solutions.
- Recognised as a technical authority and go-to expert across the engineering organisation.
- Demonstrated passion for mentoring and growing other engineers, even without formal reports.
- Exhibited an interest in broader organisational strategy and process improvement.

15Where this role leads

The long view: This role can lead into technical leadership positions such as VP of Engineering or Head of Quality, or into wider roles like CTO or Head of Product.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how QA Manager / Principal SDET is actually changing.

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Engineering software testing, worked against QA Manager / Principal SDET.

Engineering software testing Level 4

Applied to your work in QA Manager / Principal SDET

This unit aims to enable learners to understand and apply the principles of engineering software testing. Learners will gain the ability to plan, conduct, analyse, and evaluate software testing processes using appropriate tools and techniques, ensuring the effectiveness and quality of software development.

How the thinking builds

1 Remember
2 Understand
3 Apply
4 Analyse
5 Evaluate
6 Create

An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my QA Manager / Principal SDET plan, free

See Your Progress Grow Illustration

QA Manager / Principal SDET

Agile/Scrum Methodologies (Optimisation & Implementation)
Test Case Design & Management (Strategic Frameworks)
Bug Triage & Root Cause Analysis (Leadership & Process)
Regression Testing Strategy (Optimisation & Automation)
Exploratory Testing (Championing & Coaching)
Shift-Left Testing Principles (Driving Organisational Adoption)

This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

16The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

QA Manager / Principal SDET is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

Director of Quality Engineering
Roughly 3-5 years in a QA Manager/Principal SDET role.

This is a significant step up, moving from managing a team or specific product area to owning the quality strategy for an entire business unit or multiple product lines. You'll be managing other managers and have a much larger P&L.
- Defining enterprise-wide quality metrics and reporting to senior leadership.
- Leading M&A due diligence from a quality and technical debt perspective.
- Driving large-scale cultural change initiatives around quality.
- Establishing and managing relationships with key external partners and vendors at a strategic level.
Principal Architect / Distinguished SDET (Individual Contributor)
Around 3-5 years in a QA Manager/Principal SDET role.

This path is for those who want to remain deeply technical, becoming the ultimate technical authority and innovator in quality engineering without formal people management. You'd be shaping our technical future.
- Designing and implementing next-generation test automation frameworks and platforms.
- Solving the most complex, intractable quality challenges across the entire product portfolio.
- Evaluating and integrating cutting-edge testing tools and technologies.
- Acting as an internal consultant for multiple teams on advanced quality engineering problems.

Working with AI on the job

Working with AI

Where AI is starting to help

As a QA Manager or Principal SDET, your time is precious. You're juggling team management, strategic planning, and hands-on problem-solving. Imagine if your team could automate away some of the tedious, repetitive tasks, freeing them up for more complex, exploratory testing and innovation. That's where AI comes in.

We're not talking about replacing your team; we're talking about giving them superpowers. AI tools can handle the grunt work, allowing your engineers to focus on what truly matters: deep analysis, creative problem-solving, and ensuring our products are genuinely robust. For you, this means less time chasing minor issues and more time on strategic initiatives, team development, and driving real quality improvements.

Automated Test Script Generation

Imagine your team feeding user stories or even design mockups into an AI tool, and it spits out baseline UI and API test scripts. This isn't perfect, but it handles the repetitive boilerplate code, giving your engineers a massive head start. It means less time writing mundane scripts and more time refining complex scenarios or exploring edge cases.

Intelligent Flaky Test Analysis

Flaky tests are a nightmare, eroding trust and wasting developer time. AI can analyse thousands of CI/CD test runs, spot patterns in intermittent failures, and even suggest root causes ('this test only fails on Tuesdays after a database migration'). This helps your team quickly diagnose and fix the real issues, keeping your automation suite reliable.

Advanced Edge Case & Test Data Generation

Feed a new feature's requirements to a generative AI and ask it to 'act as a malicious user' or 'identify 10 tricky edge cases for this payment flow'. It can also create realistic, varied test data (think names, addresses, transaction histories) that would take hours to manually concoct. This ensures your team catches those obscure bugs before they hit production.

AI-Assisted Bug Report & Documentation

Your team can use AI assistants to turn quick observations or voice notes into perfectly formatted bug reports, complete with auto-populated fields, suggested severity, and prompts for necessary logs. It also helps in drafting comprehensive test plans, strategy documents, and team knowledge base articles. Less admin, more impact.

Common questions

How do you become a QA Manager / Principal SDET?

Common routes in include From Staff QA Engineer (Typically 2-4 years as a Staff QA Engineer.), From Lead QA Engineer (Team Lead) (Roughly 2-3 years leading a small team (3-5 people).) and From Principal SDET (Individual Contributor Path) (Around 3-5 years as a Principal SDET.). Times vary with prior experience.

Where can a QA Manager / Principal SDET progress to?

This role can lead on to Director of Quality Engineering (Roughly 3-5 years in a QA Manager/Principal SDET role.) and Principal Architect / Distinguished SDET (Individual Contributor) (Around 3-5 years in a QA Manager/Principal SDET role.), depending on the skills you build.

What new skills matter most for a QA Manager / Principal SDET?

Increasingly, AI-Driven Test Orchestration & Optimisation and Observability-Driven Testing (ODT). These are the skills our record of this role lists as growing.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my QA Manager / Principal SDET plan, free What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.

QA Manager / Principal SDET

Where should we send it?

Two short quizzes about you

Will AI change your work as a QA Manager / Principal SDET?

What's rising in its place

AI-Driven Test Orchestration & Optimisation

Observability-Driven Testing (ODT)

Skills this role draws on

Technical

How you actually get there, here

From Staff QA Engineer

From Lead QA Engineer (Team Lead)

From Principal SDET (Individual Contributor Path)

The credential is what you can do today. These are what keep you valuable.

Roles this leads to

One to one, on the work you already do

Everything else the record holds

The career path, and where it branches

Director of Quality Engineering

Principal Architect / Distinguished SDET (Individual Contributor)

Where AI is starting to help

Automated Test Script Generation

Intelligent Flaky Test Analysis

Advanced Edge Case & Test Data Generation

AI-Assisted Bug Report & Documentation

Common questions

Want a read on where you stand?