Part 5 of 5 in The QA Director's Playbook — a series on running quality engineering as a leader, not just a tester.
Somewhere around the ten-year mark, most senior QA engineers hit the same wall. They're excellent at the craft — they can design a test strategy, spot the risk nobody else saw, mentor juniors, maybe lead a squad's quality practice. And then they look at the director title above them and assume it's the same job, just bigger: more squads, more strategy documents, more meetings. It isn't. I've made this jump myself, watched dozens of engineers make it under my mentorship, and watched at least as many stall out one level below it for years because nobody told them the job changes shape, not just size.
The job doesn't scale — it changes
A senior QA engineer's value is measured by the quality of their own judgement, applied directly. A director's value is measured by the quality of judgement across a function they can't personally exercise it on. That's not a bigger version of the same skill. It's a different skill, and it's one most technical career paths never actually teach, because everything up to that point has rewarded you for being the person with the answer.
The tell that someone hasn't made this shift yet, even with a director title: they're still the person everyone routes the hardest bug to. That's a compliment and a trap. If the org still runs through you personally, you haven't built a function — you've built a bottleneck with a nicer title.
Four skills that actually separate the two roles
1. Translating quality into business language, on demand
I've written a whole article on this because it's the single most common gap I see in senior engineers reaching for a director role. As a senior IC, you can get away with talking in coverage and defect counts, because your audience is other engineers. As a director, your primary audience shifts to people who allocate budget and don't share your vocabulary. If you can't reframe a testing problem as a risk, speed, or cost problem in one sentence, on the spot, you're not ready for the rooms a director sits in — not because you lack the judgement, but because nobody in that room will be able to act on it.
Practical move: for the next month, every time you write a status update, rewrite the headline sentence in business terms before you send it — even if nobody but you ever sees the rewrite. It's a habit you need to already have before the promotion, not one you pick up during it.
2. Hiring and evaluating judgement in other people
A senior engineer is evaluated on their own decisions. A director is evaluated on the quality of the decisions made by people they hired, most of whom they'll never personally supervise line by line. That means hiring well becomes a core competency, not a periodic task — I go deep on how that interview loop actually works in part 2 of this series. If you've never sat on the hiring side of that conversation, start finding ways to shadow it before you're the one accountable for the outcome.
3. Holding a position under commercial pressure — at scale
Every senior QA engineer has had the experience of saying "this isn't ready" to a delivery lead under deadline pressure. A director has that conversation constantly, often several times a week, across multiple teams, sometimes with people two levels above them in the org chart. What changes isn't the courage required — it's the need to have a repeatable, defensible framework so the conversation doesn't depend on your personal conviction each time. That's exactly what the budget and vendor frameworks in this series are for: they turn a one-off argument you have to win from scratch into a structure the room already trusts because you've used it consistently.
4. Building a function that survives you leaving the room
This is the one that took me longest to internalise. A senior engineer's impact is visible in what they personally shipped or caught. A director's impact is visible in what still works when they're on leave for three weeks. That means writing down the standard instead of holding it in your head, federating ownership to squads instead of centralising every decision, and building the kind of quality index and escalation paths I described in the 0-1-n scaling piece. If your team can't function without you in every thread, you've built a very good senior engineer's fiefdom, not a director's function.
What to build before the promotion, not after
Waiting for the title before building these skills is the most common mistake I see. Every one of the four skills above can be practised at senior-engineer level, in miniature, well before anyone gives you the director title for it:
- Volunteer to present quality metrics to a stakeholder outside engineering, even once.
- Sit in on a hiring loop as an interviewer, not just a technical panellist.
- Write the framework you'd use to defend a "not ready" call, before you're forced to use it live.
- Document one process so thoroughly that someone else could run it without asking you a single question.
None of these require a title change. All of them are the actual audition for one.
An honest note on levelling
A lot of the frustration I hear from senior engineers isn't really about skill gaps — it's about not knowing where they genuinely stand against the bar above them, especially when titles are inconsistent across companies. If that's where you are, it's worth getting an outside calibration rather than guessing from your current company's internal ladder, which may or may not reflect the market. If you want structured 1:1 support making this specific jump, that's exactly what my mentorship programme is built for.
Related reading
- What a CTO Actually Wants to Hear About Quality — part 1 of this series.
- Hiring for Judgement: Interviewing SDETs and QA Leads in the AI Era — part 2 of this series.
- Building Engineering at Scale: The 0-1-n Quality Problem — the function-building skill this article's fourth point draws on.