07
H
1st Edition · Premium Guide
Levels & Titles
Decoded, so you place the right level every time.
"QA Engineer" hides three different jobs. Know which one.
This guide is the exclusive intellectual property of Hofler Enterprises LLC, protected under US and international copyright law.
This guide is for the recruiter who places QA engineers and is tired of screening for a role nobody ever explained in plain terms. You do not need to code. You need to understand the work well enough to source, screen, and place with confidence.
Every page here comes from the other side of the interview. It is what a working senior QA engineer would tell a recruiter he trusted.
Read it once, start to finish. Then keep it open beside you on your next QA screen and use the sections as a reference. The questions at the end of each section are meant to be used, not admired.
The titles, the levels, and the pay bands, so you place for the real job instead of matching on a word.
Why one title hides three different jobs
In QA, the title on the req is not a reliable description of the job — the gap between a manual tester and a senior SDET is wider than junior-to-senior in most other roles, yet they can carry the identical title. You’ll learn to name the single fact that makes QA uniquely tricky to recruit on, and see exactly how misreading a level costs you the deal. The section closes with the fast rule that anchors the entire guide: three different jobs can wear the exact same title, and the level is what tells them apart.
QA Analyst, QA Engineer, SDET, QE Lead, and the rest
QA has a thicket of titles used inconsistently across companies, and this section is your translation table — QA Analyst, QA Engineer, SDET, QE Lead, QA Manager, and QA Architect, decoded into what they actually signal. You’ll learn to spot “QA Engineer” as the one title that gives you nothing and requires interrogation, and to tell apart the two AI titles that look alike on paper: Profile 3 — AI-Augmented Test Engineer, who uses AI to test software faster, versus Not Profile 3 — AI Test Engineer / AI Evals Engineer, who tests AI systems themselves, a genuinely different discipline. The section closes by separating the people track (QA Manager) from the top of the technical track (QA Architect).
Junior to principal — and what actually changes
Underneath every title sits the thing that actually defines the job: level — and in QA, level tracks ownership, not years in seat. You’ll learn the four-rung ladder (junior, mid, senior, staff/principal) and, more concretely, the four ownership verbs behind it — executes within a system, contributes to it, builds it, or directs across systems. The section closes with the key gut-check: ownership is the one thing on a resume that can’t be borrowed from the team.
The work transitions that define seniority
Not every level jump is equal — two transitions change the actual kind of work far more than a normal step, and they’re what separate manual testing, automation, and SDET-level work into three genuinely different jobs. You’ll learn to name Break #1 (manual to automation) and Break #2 (automation to SDET/build-level), and how to ask the one question that places a role against both breaks in seconds. The section closes on candidates actively crossing a break, often your best growth hires precisely because the market hasn’t priced them yet.
Putting the decode to work in seconds
The decode only pays off once you run it live, on the req in your inbox and the resume in front of you — because the same “QA Engineer” title can describe wildly different work. You’ll learn the four-step read (title signal, which break, which ownership rung, which stack) on both a live job requisition and a submitted resume. The section closes with the fast rule for both directions: when the title and the substance disagree, believe the substance.
Closing — the full series comes together
This is the wrap-up of both the guide and the full seven-part series: the QA title that used to be a black box is now something you can open in a sentence. You’ll learn how accurate level reading changes three specific conversations — the intake call, the screen, and the submission. The section closes on the promise of the whole series: hearing the difference between someone who has done the work and someone who has only listed it.
Rehearse the screen — 2 reps + sample script
Knowing the ladder and freezing on a live call are two different problems, and this section closes the second one: two rehearsals plus a full mock screening exchange, so the level-locating questions become automatic. You’ll practice placing a candidate on the ownership ladder from how they describe their own scope, then hearing someone actively crossing a break. The section closes with a full sample screening dialogue you can read aloud.
The Levels & Titles Quick-Reference
This is the one-page version of the entire guide — a quick-reference built to sit next to the phone during a live screen. You’ll get the title-decoder table for all ten QA titles side by side with the ownership ladder, the two breaks, and the four-step read you can run on any req or resume without looking anything up. The section closes on the one rule the whole series distills to: title is the label, the work is the truth.
A clear map of the QA titles and levels you will meet, what each one actually does, and how to place for the real job instead of a keyword.
The words QA Engineer sit on three very different jobs, at three very different pay bands. Placing on the title alone is how mismatches happen.
One company's QA Engineer clicks through the product by hand. Another company's QA Engineer writes automation frameworks in code. A third calls that same coding role an SDET. The title did not change; the job did.
If you place on the title, you will send a manual tester into an automation role and a coder into a role with no coding. Both are bad hires that looked perfect on paper.
Almost every QA title collapses into one of three real jobs. Learn these three and most resumes sort themselves.
When a req says QA Engineer, your first job is to figure out which of these three it actually is. The intake and the tool stack usually tell you within a minute.
QA Engineer hides three different jobs at three different pay bands. The full guide decodes the titles and levels so you place the right one every time.
Get this guide →Start the series with the plain-terms foundation.
All 7 recruiter guides in one bundle. Source, screen, and place QA talent end to end.