--- title: "QA Engineer: The Job, the Ladder, and the Layoff Risk" description: "What a QA engineer does, how it differs from a tester and an SDET, the ladder up to QA lead and head of QA, and why the last gate is the first one cut." url: "https://www.marian.coach/qa-engineer-role/" lang: "en" image: "https://www.marian.coach/_astro/portrait-leaned-in-hero.DEA9tiuB_Z2otIvV.jpg" --- A **QA engineer** is the person on a software team who learns how the product breaks before a customer does. They build the tests, checks and release signals that stop it breaking the same way twice. QA stands for quality assurance. The title gets used for four different jobs, though, and the difference between them decides your pay, your ladder and how safe you are in the next reorg. ## QA tester vs QA engineer vs SDET vs quality engineer Most job boards treat these as one title. Postings don’t. Here is how they split once you read past the headline: | | QA tester | QA engineer | SDET | Quality engineer | | --- | --- | --- | --- | --- | | The question they answer | Does this feature work as specified? | Is this release safe to ship? | Can a machine tell us that on every commit? | Why do defects reach production at all? | | Writes code | Rarely | Often, scripts and automated checks | Always, it’s a developer role | Yes, plus test infrastructure | | Main output | Bug reports, test runs | Test plans, automation, release readiness | Frameworks, CI suites, tooling | Strategy, metrics, platforms developers use | | Usually sits | At the end of the sprint | In the team, close to release | Next to developers | Across teams | | Natural next step | QA engineer | QA lead or SDET | Software engineer or test architect | Head of QA, quality engineering director | SDET means software development engineer in test. Microsoft ran the title at scale and then [retired it in 2014](https://blog.pragmaticengineer.com/how-microsoft-does-qa/), folding testers into a single engineer role. ## A week in the job Strip the adjectives from a dozen live postings and the work looks similar from Prague to San Francisco: - **Before code exists:** sit in grooming and design reviews, write test cases and edge cases on the ticket. A [Bloomreach QA posting](https://job-boards.greenhouse.io/bloomreach/jobs/8249295) puts it plainly: “You make the whole team better at testing, not the place work gets handed off to.” - **While it’s built:** keep the automated suite in the pipeline green, chase flaky tests, add checks for the new feature. - **Before release:** exploratory testing on real devices and browsers, the regression pass, a readiness summary somebody signs. - **After release:** turn production incidents into regression tests, so the same bug can’t come back quietly. The share of each depends on the company. A manual-heavy posting spends most of the week in the third bullet. A good product team pushes as much as possible into the first two. ## The ladder above senior QA Most explainers stop at “senior QA engineer”. The interesting decisions start there. ![Marian Kamenistak leading a two-day engineering leadership workshop for a small group of managers, presenting at a screen.](https://www.marian.coach/_astro/talk-26.CMdq9dhg_Z22CnP3.webp) Past senior, the QA ladder forks: lead the framework, or lead the people. **QA lead** means two different things. In one company it’s a framework architect with no reports, the person who owns the test automation charter. In another it’s a player-coach who runs performance reviews, writes test plans and still builds automation. Ask which one before you accept the title, because only the second one prepares you for management. **QA manager or head of QA** owns the quality strategy for several teams, the hiring of testers and SDETs, and the metrics leadership sees. The good version of this job changes how developers work. The weak version is a department that receives builds and returns verdicts. **Director or senior manager of quality engineering** is where the role is being reinvented. [Samsara’s senior manager posting](https://www.samsara.com/company/careers/roles/8139255?gh_jid=8139255) describes self-service test platforms and escaped-regression rates, closer to a platform team than a test team. [Machinify’s director posting](https://job-boards.greenhouse.io/machinifyinc/jobs/4339442009) asks for someone to rethink QA “where AI generates the majority of code”, at $225,000 to $250,000. For a baseline, the US [Bureau of Labor Statistics](https://www.bls.gov/oes/current/oes151253.htm) puts the median for software QA analysts and testers at $104,300 (May 2025). In Central Europe, the Bloomreach QA Engineer II role above lists 732,000 to 1,110,000 CZK base for Czechia. Sideways moves are common: SDET into software engineering, quality engineering into platform or developer experience, and senior QA into release management or technical program management, where knowing how releases fail is a large part of the job. ## The last gate gets cut first QA work tends to sit at the end of the line, and the end of the line is visible only when something fails. When nothing fails, it looks like cost. That’s the structural risk of the role, and it has a history. Yahoo removed its QA team around 2015 and had engineers ship without a QA safety net; [IEEE Spectrum](https://spectrum.ieee.org/yahoos-engineers-move-to-coding-without-a-net) reported the company’s chief architect saying it was working. Microsoft’s 2014 move ended a setup where teams commonly ran about two developers per SDET, according to [The Pragmatic Engineer](https://newsletter.pragmaticengineer.com/p/how-big-tech-does-qa). Atlassian went a different route years ago and renamed the job: its QA team does [“quality assistance”](https://www.atlassian.com/blog/development/introducing-atlassian-qa), coaching developers to test their own work instead of testing it for them. Read today’s postings closely and you can see the same pressure in the wording. [Robinhood’s staff quality engineer posting](https://boards.greenhouse.io/robinhood/jobs/8082056) calls the team “the final line of defense for product quality”. An [Okta SDET posting](https://www.okta.com/company/careers/opportunity/8240685?gh_jid=8240685) asks you to “hold the release bar”, a paragraph later says you’ll work “as an engineer, not a gatekeeper”, and lists an on-call rotation further down. Machinify wants a director who can hold the bar on rigor “without becoming the bottleneck on velocity”, while code volume multiplies “without proportional headcount growth”. Each of those lines is reasonable alone. Together they describe a seat that collects the blame for escaped bugs and the blame for slow releases, with no added people to handle AI-written code. If you see two of these phrases in one ad, ask how many QA people the team had a year ago. ### Moving upstream In all of these versions the way out is to make quality something developers produce, and to be the person who built it. ![Marian Kamenistak facilitating a workshop, mid-gesture, in front of a slide about roadmap delivery.](https://www.marian.coach/_astro/talk-16.BOCFjZmx_Z2cP3Aa.webp) The release date is set in the planning session. Testing time should be set there too. 1. **Get into grooming.** Test cases and failure modes go on the ticket before anyone writes code. That’s where most bugs are cheapest to fix. 2. **Put QA in the estimate.** If testing time isn’t in the estimate, QA will usually look like the reason a date slipped. I wrote about building an [estimation checklist](https://www.marian.coach/blog/dont-let-yourself-be-held-hostage-by-estimates/) that names code review, QA and deployment explicitly. 3. **Own the gate as code.** A CI suite developers run on every commit protects you better than a manual pass only you can run. 4. **Report escaped defects, not executed test cases.** Leadership reads one number: how many bugs customers found, and whether it’s falling. 5. **Turn sign-off into a written risk statement.** You describe what was tested and what wasn’t; the product owner accepts the residual risk. Your name on a release shouldn’t mean you personally guarantee it. ### Self-check: gate or coach? Answer each with yes or no: - Do developers on your team write and run tests without being asked? - Do you see features in design, or first in the “ready for QA” column? - Does the sprint estimate include testing time? - If you took two weeks off, would releases stop, or would the suite keep catching regressions? - Can you say how many defects escaped to production last quarter? - Does your manager know which incidents your tests prevented? - Is your sign-off a written statement of risk, or your name on a release? Mostly “no” means you are the gate, and the gate is what gets cut first in a reorg. Mostly “yes” means you’re building the system, as opposed to standing at the end of it, which is the profile that gets promoted into QA lead and quality engineering roles. ![Hand-drawn diagram titled Gate or coach?: in The gate, a large manual pass and a small CI suite; in Building the system, the sizes swap and the CI suite is the large one.](https://www.marian.coach/images/blog/qa-engineer-role/infographic.webp) If you’re a QA lead choosing between people management and quality engineering, or trying to move out of the last-gate seat before a reorg moves you, that’s the kind of career decision I help people to think through in [1:1 career mentoring](https://www.marian.coach/engineering-career-coach/). ## Titles QA people move into - [AI QA engineer: testing AI, or testing with AI](https://www.marian.coach/ai-qa-engineer-role/) - [Platform engineer: the team developers build on](https://www.marian.coach/platform-engineer-role/) - [Technical program manager: what the role owns](https://www.marian.coach/technical-program-manager-role/) - [Engineering manager: the job after the senior title](https://www.marian.coach/engineering-manager-role/) - [Team lead vs tech lead vs engineering manager](https://www.marian.coach/team-lead-role-vs-tech-lead-vs-engineering-manager/) ## Frequently asked What does a QA engineer do?+ A QA engineer finds out how software breaks before customers do. In a normal week that means test cases written on the ticket, automated checks in the pipeline, bug reports developers can reproduce, and a release readiness call. Senior people also decide what is worth testing at all, which matters more than the test count. Is coding required for a QA engineer?+ Manual testers often don't code, but most QA engineer roles at product companies expect Python, Java or TypeScript. Add a framework like Playwright or Selenium. The further up the ladder you go, the more code you write or review, because the job moves from running tests to building the system developers test with. Is QA a good career choice?+ QA is a good entry into software and a weak place to stay still. Manual testing is the most exposed part of the field. QA engineers who automate, sit in design reviews and own the CI gate have a real ladder up to QA lead, head of QA and quality engineering director, or a sideways move into development. How much do QA engineers earn?+ In the US the median for software QA analysts and testers was $104,300 in May 2025, per the Bureau of Labor Statistics. SDET and senior quality engineering roles at product companies post well above that. In Czechia, a mid-level QA engineer posting from a scale-up listed 732,000 to 1,110,000 CZK base. Will QA get replaced by AI?+ AI will take over parts of QA work, though the judgment calls are harder to hand over. Generating regression scripts and triaging failures are already moving to AI tools, and at least one director-level posting plans for more code without more testers. Deciding what to test, defining release criteria and judging AI output still need someone who knows the product. [1:1 mentoring](https://www.marian.coach/engineering-manager-mentor/) ## Ready to move this from advice to action? 1:1 mentoring for engineering leaders. 317 mentees since 2019. Rate a session under 7/10 and you don't pay for it. First intro is free. [Book a free 30-min intro →](https://www.marian.coach/meet) ## Read next - [![Marian Kamenistak speaking at an engineering leadership event.](https://www.marian.coach/_astro/talk-21.BdOplLV4_mJDuE.webp) ### AI Platform Engineer: What You Build and What You Own AI platform engineer: how the role differs from ML platform and MLOps, the five layers you run, who owns what, and a plan for your first 90 days. 9 October 2026 · By Marian Read → ](https://www.marian.coach/ai-platform-engineer-role/) - [![Marian Kamenistak speaking at an engineering leadership event.](https://www.marian.coach/_astro/talk-11.BJeQ21aF_1QQ2Eh.webp) ### AI QA Engineer: Two Jobs Behind One Title AI QA engineer can mean testing AI systems with evals or testing software with AI tools. How to tell them apart, what each pays, and how to spot a gig. 9 October 2026 · By Marian Read → ](https://www.marian.coach/ai-qa-engineer-role/) - [![Marian Kamenistak standing in front of a brick wall, hands together, smiling.](https://www.marian.coach/_astro/portrait-outdoor.CdyTp4cl_wWxqm.webp) ### Member of Technical Staff Meaning: Why AI Labs Use One Title Member of technical staff meaning: the flat title OpenAI, Anthropic and xAI give engineers and researchers, what it hides, and what to ask before you sign. 9 October 2026 · By Marian Read → ](https://www.marian.coach/member-of-technical-staff/) ### New posts, straight to your inbox. Your emailSubscribe You're on it. Nothing hits your inbox today. First send goes out once the list is live, and you're already on it. [Connect on LinkedIn →](https://www.linkedin.com/in/mariankamenistak/)[See the free tools →](https://www.marian.coach/ai-coaching-tools/) ## Structured data ```json {"@context":"https://schema.org","@type":"ProfessionalService","name":"Marian Kamenistak | Engineering Leadership Mentoring","url":"https://www.marian.coach/qa-engineer-role/","image":"https://www.marian.coach/_astro/portrait-leaned-in-hero.DEA9tiuB_Z2otIvV.jpg","description":"What a QA engineer does, how it differs from a tester and an SDET, the ladder up to QA lead and head of QA, and why the last gate is the first one cut.","serviceType":["Engineering leadership mentoring","Engineering manager coaching","CTO coaching","Fractional CTO","Leadership development for software engineers"],"hasOfferCatalog":{"@type":"OfferCatalog","name":"Engineering leadership mentoring and advisory","itemListElement":[{"@type":"Offer","itemOffered":{"@type":"Service","name":"1:1 engineering leadership mentoring","description":"One-to-one mentoring for engineering leaders from Staff Engineer to CTO. 60-minute sessions, weekly or bi-weekly.","url":"https://www.marian.coach/pricing/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Engineering manager coaching","description":"Coaching for first-time and experienced engineering managers: delegation, performance, hiring, team scaling.","url":"https://www.marian.coach/engineering-manager-mentor/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"CTO and VP Engineering mentoring","description":"Mentoring for CTOs, VPs of Engineering and Heads of Engineering running 30-200 person organisations.","url":"https://www.marian.coach/cto-mentor/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Mentor in Residence","description":"A dedicated onsite mentor for your engineering organisation, booked by the quarter.","url":"https://www.marian.coach/mentor-in-residence/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Fractional CTO","description":"Part-time CTO engagements for companies without a full-time technology leader.","url":"https://www.marian.coach/fractional-cto/"}}]},"telephone":"+420 736 519 879","email":"marian@marian.coach","sameAs":["https://www.linkedin.com/in/mariankamenistak/","https://www.youtube.com/@engineeringleaders","https://github.com/marian-kamenistak","https://www.engineeringleaders.io/","https://www.elc-conference.io/","https://www.marianslist.com/","https://www.mentoringhub.io/"],"address":{"@type":"PostalAddress","streetAddress":"Varšavská 715/36, Vinohrady","addressLocality":"Praha 2","postalCode":"12000","addressCountry":"CZ"},"geo":{"@type":"GeoCoordinates","latitude":50.0734418,"longitude":14.4385757},"openingHoursSpecification":[{"@type":"OpeningHoursSpecification","dayOfWeek":["Monday","Tuesday","Wednesday","Thursday","Friday"],"opens":"09:00","closes":"17:00"}],"priceRange":"296–395 EUR","areaServed":[{"@type":"Place","name":"Europe"},{"@type":"Country","name":"Czechia"},{"@type":"Country","name":"Slovakia"},{"@type":"Country","name":"Poland"},{"@type":"Place","name":"North America"}]} {"@context":"https://schema.org","@type":"Person","@id":"https://www.marian.coach/#person","name":"Marian Kamenistak","url":"https://www.marian.coach/","image":"https://www.marian.coach/_astro/portrait-leaned-in-hero.DEA9tiuB_Z2otIvV.jpg","jobTitle":["Engineering Leadership Mentor","Fractional CTO & Chief AI Officer","Founder, Engineering Leaders Community","Engineering Manager Coach","CTO Coach","Keynote Speaker"],"hasOccupation":[{"@type":"Occupation","name":"Engineering Leadership Mentor"},{"@type":"Occupation","name":"Fractional CTO & Chief AI Officer"}],"worksFor":{"@type":"Organization","name":"Engineering Leaders Community","url":"https://www.engineeringleaders.io/"},"alumniOf":[{"@type":"Organization","name":"Mews"},{"@type":"Organization","name":"Databricks"}],"knowsLanguage":["English","Czech","Slovak"],"knowsAbout":["Engineering leadership","Engineering management","Scaling engineering teams","CTO mentoring","Engineering org design","VP of Engineering role","Engineering director role","CTPO role","Team lead development","Staff engineer career path","Fractional CTO engagements","AI-assisted engineering leadership","Conference keynotes on engineering leadership","Panel moderation","Podcast guest — engineering leadership"],"homeLocation":{"@type":"Place","name":"Prague, Czechia"},"sameAs":["https://www.linkedin.com/in/mariankamenistak/","https://www.youtube.com/@engineeringleaders","https://github.com/marian-kamenistak","https://www.engineeringleaders.io/","https://www.elc-conference.io/","https://www.marianslist.com/","https://www.mentoringhub.io/","https://www.crunchbase.com/person/marian-kamenistak","https://www.wikidata.org/wiki/Q140488098","https://developers.mews.com/author/marian/","https://startupdisrupt.com/speakers/marian-kamenistak/","https://theorg.com/org/engineering-leaders-community/org-chart/marian-kamenistak"]} {"@context":"https://schema.org","@type":"WebPage","url":"https://www.marian.coach/qa-engineer-role/","name":"QA Engineer: The Job, the Ladder, and the Layoff Risk","inLanguage":"en","dateModified":"2026-10-09T00:00:00.000Z"} {"@context":"https://schema.org","@type":"FAQPage","inLanguage":"en","mainEntity":[{"@type":"Question","name":"What does a QA engineer do?","acceptedAnswer":{"@type":"Answer","text":"A QA engineer finds out how software breaks before customers do. In a normal week that means test cases written on the ticket, automated checks in the pipeline, bug reports developers can reproduce, and a release readiness call. Senior people also decide what is worth testing at all, which matters more than the test count."}},{"@type":"Question","name":"Is coding required for a QA engineer?","acceptedAnswer":{"@type":"Answer","text":"Manual testers often don't code, but most QA engineer roles at product companies expect Python, Java or TypeScript. Add a framework like Playwright or Selenium. The further up the ladder you go, the more code you write or review, because the job moves from running tests to building the system developers test with."}},{"@type":"Question","name":"Is QA a good career choice?","acceptedAnswer":{"@type":"Answer","text":"QA is a good entry into software and a weak place to stay still. Manual testing is the most exposed part of the field. QA engineers who automate, sit in design reviews and own the CI gate have a real ladder up to QA lead, head of QA and quality engineering director, or a sideways move into development."}},{"@type":"Question","name":"How much do QA engineers earn?","acceptedAnswer":{"@type":"Answer","text":"In the US the median for software QA analysts and testers was $104,300 in May 2025, per the Bureau of Labor Statistics. SDET and senior quality engineering roles at product companies post well above that. In Czechia, a mid-level QA engineer posting from a scale-up listed 732,000 to 1,110,000 CZK base."}},{"@type":"Question","name":"Will QA get replaced by AI?","acceptedAnswer":{"@type":"Answer","text":"AI will take over parts of QA work, though the judgment calls are harder to hand over. Generating regression scripts and triaging failures are already moving to AI tools, and at least one director-level posting plans for more code without more testers. Deciding what to test, defining release criteria and judging AI output still need someone who knows the product."}}]} {"@context":"https://schema.org","@type":"Article","headline":"QA Engineer: The Job, the Ladder, and the Layoff Risk","description":"What a QA engineer does, how it differs from a tester and an SDET, the ladder up to QA lead and head of QA, and why the last gate is the first one cut.","inLanguage":"en","articleSection":"career","datePublished":"2026-10-09T00:00:00.000Z","dateModified":"2026-10-09T00:00:00.000Z","author":{"@id":"https://www.marian.coach/#person"},"publisher":{"@type":"Organization","name":"Marian Kamenistak","url":"https://www.marian.coach/","logo":{"@type":"ImageObject","url":"https://www.marian.coach/favicon-192x192.webp","width":192,"height":192}},"image":{"@type":"ImageObject","url":"https://www.marian.coach/_astro/portrait-leaned-in-hero.DEA9tiuB_Z2otIvV.jpg","width":1200,"height":630},"mainEntityOfPage":{"@type":"WebPage","@id":"https://www.marian.coach/qa-engineer-role/"},"keywords":"career, engineering, quality","wordCount":1423,"timeRequired":"PT6M","isAccessibleForFree":true} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://www.marian.coach/"},{"@type":"ListItem","position":2,"name":"Resources","item":"https://www.marian.coach/resources/"},{"@type":"ListItem","position":3,"name":"QA Engineer: The Job, the Ladder, and the Layoff Risk","item":"https://www.marian.coach/qa-engineer-role/"}]} ```