QA Engineer Job Description Template 2026

Last updated: May 10, 2026

A QA engineer designs test strategies, writes automated and manual tests, and prevents defects from reaching production, with U.S. salaries ranging from $84,000 at entry level to $152,000 for senior SDETs depending on whether the role is manual, automation-focused, or full-stack testing. The template below is built from QA job descriptions that actually filled, not from the generic postings that collect 300 applications and zero hires.

Nine out of ten QA job descriptions on the internet are the same post. “Strong attention to detail.” “Experience with automated testing frameworks.” “Ability to work in an Agile environment.” Those three phrases appear in roughly 90% of QA postings across every major job board, and they filter exactly nobody. A candidate with six months of Udemy coursework checks all three boxes. So does a 12-year veteran who’s built custom test harnesses for distributed payment systems processing 40,000 transactions per hour.

The problem is not that companies write bad JDs on purpose. The problem is that “QA engineer” is three different jobs wearing one title, and most hiring managers don’t realize they’re writing a posting for the wrong one until the resumes start arriving.

Mike Carter. I work QA and engineering searches at KORE1 across our IT staffing practice, and QA roles are consistently where I see the widest gap between what a JD asks for and what the team actually needs. We collect a placement fee when you hire through us, so weigh accordingly. The template and the salary data below work whether you use a staffing partner or not.

Three Roles Hiding Behind One Title

QA engineering splits into three distinct hiring profiles in 2026: manual QA analysts who execute test cases and file bugs, automation engineers who build and maintain test suites in code, and SDETs who architect testing infrastructure at the platform level.

This is not a semantic distinction. It is a $60,000 salary gap. Write a JD for the wrong one and you will spend six weeks interviewing candidates who cannot do the actual work.

Manual QA / QA Analyst

Runs test cases. Files bugs. Validates user stories against acceptance criteria. Tools are Jira, TestRail, maybe Postman for API spot checks. This person is not writing code. They are reading requirements, clicking through the application, documenting what breaks, and working closely with developers to reproduce issues. Entry-level manual QA roles start around $55,000 to $70,000, and mid-level sits in the $75,000 to $95,000 range depending on the product complexity, industry vertical, and whether the role includes any light automation scripting alongside the manual test execution work. Companies that need manual QA but post an “Automation Engineer” title because it sounds more modern will scare away the right candidates and attract the wrong ones.

QA Automation Engineer

Writes test scripts. Maintains automated regression suites. Integrates tests into CI/CD pipelines. This person codes daily. Playwright, Cypress, or Selenium for UI tests. Pytest, JUnit, or TestNG for unit and integration layers. They understand page object models, test data management, and flaky test triage. Mid-level automation engineers run $100,000 to $130,000, with seniors pulling $125,000 to $150,000 in most metros and clearing $160,000 in San Francisco, Seattle, and New York where the cost of living and the density of automation-heavy engineering orgs both push comp upward. The candidate pool here is deeper than it was three years ago because Playwright’s adoption has lowered the barrier to writing reliable browser tests, but the quality variance is enormous. A lot of resumes list “Selenium” based on following a tutorial.

Playwright now leads with 45% adoption among QA professionals, overtaking Selenium at 22% for the first time, according to TestDino’s 2026 market analysis. That shift matters for your JD. Requiring Selenium-only in 2026 narrows your pool unnecessarily. Requiring Playwright-only screens out experienced engineers who’ve been running Selenium for eight years in enterprise environments where migration is ongoing. Best approach: name the tools your team actually uses, note which ones are acceptable alternatives.

SDET (Software Development Engineer in Test)

Different animal entirely. SDETs write production-quality code. They build test frameworks that other engineers use. They design test architecture at the platform level, think shared libraries, custom assertion engines, test environment provisioning, performance benchmarking harnesses. They sit closer to the development team than to a traditional QA function. Compensation reflects that proximity: mid-level SDETs earn $110,000 to $140,000, and senior SDETs command $140,000 to $175,000 or higher at well-funded companies. The $45,000 to $55,000 premium over a senior manual QA engineer exists because SDETs write code at the same complexity level as the developers they support.

So before you write a single line of your job description, figure out which of those three roles your team actually needs. If the answer is not obvious after a 15-minute conversation with the hiring manager, the JD will attract all three and filter none of them.

Sources: ZipRecruiter (March 2026), Glassdoor (2026). Ranges represent 25th to 75th percentile. Geography, industry, and company stage shift these significantly. Coastal metros add 15-25%. Fintech and healthcare add 10-20%. See our QA engineer salary guide for the full breakdown.

QA Engineer Job Description Template

Copy this. Edit the bracketed sections. Delete anything that does not match your actual role. The notes in parentheses explain why each section exists and what to change.

Job Title

[QA Engineer / QA Automation Engineer / SDET / QA Analyst]

(Pick the title that matches what the person will actually do 80% of the time. “QA Engineer” is the most common search term and the broadest net. Use “QA Automation Engineer” if coding is required daily. Use “SDET” if the role is more dev than test. Use “QA Analyst” if the role is primarily manual. Mixing signals here is where most postings go wrong.)

About the Role

(Two to three sentences. What does this person own? What product or system do they test? Who do they report to? Skip the company boilerplate paragraph. Candidates scan past it.)

[Company Name] is hiring a [title] to own quality across [product/platform/system name]. You will [primary responsibility: build and maintain automated test suites / design test strategies / execute manual test plans] for [what the product does in one phrase], reporting to [Engineering Manager / QA Lead / Director of Engineering]. This role is [remote / hybrid in {city} / onsite in {city}].

What You Will Do

(List 6-8 specific responsibilities. Avoid generic bullets like “ensure product quality.” Every line should describe a task someone could start doing on day one. Include the tools and systems they will actually touch.)

• Design and execute test plans for [specific product area or feature set], covering functional, regression, and [integration / performance / security] testing
• Write and maintain automated tests using [Playwright / Cypress / Selenium / Pytest / JUnit] integrated into our [GitHub Actions / Jenkins / GitLab CI / CircleCI] pipeline
• Triage test failures in CI, distinguish between real defects and flaky tests, and own the fix for flaky tests in the automation suite
• Collaborate with [frontend / backend / mobile / platform] engineers during sprint planning to identify testability gaps before code is written
• Own test data management for [staging / QA / pre-prod] environments, including [fixture creation / database seeding / synthetic data generation]
• Review pull requests from a quality perspective, flagging untested edge cases and suggesting test coverage for new features
• Track and report on defect escape rate, test coverage metrics, and [mean time to detection / regression pass rate] on a [weekly / sprint] cadence
• Participate in production incident postmortems and translate findings into new automated regression tests to prevent recurrence

What You Bring

(Split into required and preferred. Be honest about which qualifications are actually required versus which ones would be nice to have. Inflating the required list shrinks your candidate pool for no reason.)

Required:

• [3-5 / 5-8 / 8+] years of experience in software quality assurance, with [at least X years] focused on [automation / manual testing / test architecture]
• Proficiency in [specific language: Python / Java / JavaScript / TypeScript] for writing automated tests
• Hands-on experience with [Playwright / Cypress / Selenium WebDriver] for browser automation, or [Pytest / JUnit / TestNG] for API and unit testing
• Familiarity with CI/CD pipelines ([GitHub Actions / Jenkins / GitLab CI]) and the ability to debug build failures caused by test flakiness
• Experience testing [REST APIs / GraphQL / microservices / monolithic applications] using tools like [Postman / REST Assured / Insomnia]
• Understanding of [SQL databases / NoSQL databases] sufficient to write queries for test data setup and validation

Preferred:

• Experience with [performance testing tools: k6 / JMeter / Gatling / Locust]
• Familiarity with [containerized environments: Docker / Kubernetes] for test environment provisioning
• Exposure to [mobile testing: Appium / Detox / XCUITest / Espresso]
• [ISTQB Foundation Level / CSTE / AWS Certified] or equivalent certification
• Experience in [your industry: fintech / healthcare / e-commerce / SaaS] domain

Compensation and Benefits

(Include a salary range. Candidates skip postings without one. The range does not need to be narrow. A $30K band is fine. It signals seniority level and filters out mismatches before anyone wastes interview time.)

• Base salary: $[X] – $[Y] depending on experience and qualifications
• [List 3-4 benefits that matter: healthcare, 401k match, PTO policy, remote flexibility, professional development budget]

About [Company Name]

(Keep this to 2-3 sentences. Product, stage, team size. Candidates care about what they will build and who they will work with, not your mission statement.)

What Most QA Job Descriptions Get Wrong

Looked at 40 QA engineer postings on LinkedIn last week. Pulled a random sample from different industries and company sizes. The same five mistakes showed up in over 30 of them.

Listing every testing type as a requirement. “Experience with functional, regression, integration, performance, security, accessibility, load, stress, smoke, and sanity testing.” Nobody is doing all of those. If your team needs a performance testing specialist, say that. If you need someone who owns regression automation, say that. Listing every testing type in the dictionary tells candidates you do not actually know what you need, and the ones who do know will skip your posting because it reads like a company that does not understand QA.

The second mistake is worse. Requiring a bachelor’s degree in computer science. Some of the strongest QA engineers I have placed came through bootcamps, self-taught paths, or career switches from adjacent technical roles. One of our best placements last year was a former civil engineer who taught herself Python and Playwright over 18 months. Her degree was in structural engineering. She also had an instinct for edge cases that most CS grads do not develop until years into their career, because engineering training teaches you to think about failure modes. The CS degree requirement eliminates candidates like her from your pipeline before a human ever sees their resume.

Third: vague seniority signals. “3-5 years of experience” means nothing without context. Three years of what? Manual testing at a consultancy where you ran the same regression suite every sprint? Or three years building a test automation framework from scratch at a Series B startup with no existing test infrastructure? Those are radically different candidates at radically different price points, and your JD needs to signal which one you want by describing what the test infrastructure looks like today and what the hire will be expected to build, maintain, or scale during their first year.

Four, no mention of the product. QA candidates want to know what they are testing. “Our platform” is not enough. Is it a consumer mobile app? An enterprise SaaS dashboard? A payments API? A data pipeline? The testing challenges for each of those are completely different, and experienced QA engineers who have spent years in one domain know that testing a payments API for rounding errors across currency conversions is a fundamentally different skill than testing a consumer mobile app for gesture recognition bugs on twelve different screen sizes.

Five: listing 15+ tools. “Selenium, Cypress, Playwright, Appium, JMeter, Postman, SoapUI, TestRail, Jira, Confluence, Jenkins, GitHub Actions, Docker, Kubernetes, AWS.” No one is proficient in all of those simultaneously. List the 3-4 tools your team actually uses. Note 1-2 acceptable alternatives. That is all you need in the tools section, and anything more than that reads like a wish list written by someone who searched “QA tools” and pasted everything that came up.

When to Require Certifications (and When to Skip Them)

ISTQB Foundation Level is the most recognized QA certification globally. Comes up in roughly a third of the QA postings I see. Worth requiring? That depends on what seniority level you are hiring for and what the certification actually proves at each tier.

For junior roles where you are hiring someone with limited professional QA experience, ISTQB Foundation demonstrates baseline vocabulary. The candidate knows what boundary value analysis means. They can articulate the difference between verification and validation. Not a substitute for hands-on ability, but a reasonable signal that someone has invested time in learning testing theory formally, which is more than you can say for most candidates at the junior level who learned QA by Googling “how to write test cases” during their first week on the job and never looked back.

For mid-level and senior roles, it is mostly noise. A senior automation engineer with eight years of Playwright and Selenium experience who has never taken the ISTQB exam is not a weaker candidate than someone who passed it. The certification tests vocabulary and theory. Senior roles test judgment and execution. Those are different things.

ISTQB did release a Certified Tester AI Testing (CT-AI) module in 2025 that covers testing AI-based systems, including probabilistic behavior, non-determinism, and data quality validation. If your product uses ML models in production and the QA engineer needs to validate model outputs, CT-AI actually signals relevant, current knowledge. That is a narrow use case but a legitimate one.

The practical recommendation: list certifications under “Preferred,” never under “Required,” unless regulatory compliance demands it. Healthcare, fintech, and defense sometimes do. Most SaaS companies do not.

QA Engineer Salary Benchmarks 2026

Three sources. They disagree. The disagreement tells you something useful about where the market actually sits versus where salary aggregators think it sits.

The BLS groups QA analysts with software developers and testers into one occupation, which makes their median less useful for QA-specific budgeting. ZipRecruiter’s average sits lower because it captures junior and entry-level postings that Glassdoor’s self-reported data tends to miss. If you are budgeting a QA automation engineer hire for 2026, plan on $85,000 to $105,000 for a mid-level candidate with three to five years of hands-on automation experience, and $120,000 to $150,000 for a senior who has built or inherited and maintained a full regression suite in production. If the role requires SDET-level framework architecture, add $15,000 to $25,000 to those ranges.

The Bureau of Labor Statistics projects 15% growth for software developers, QA analysts, and testers through 2034, calling it “much faster than average.” The automation testing market specifically is growing at 17% annually and projected to reach $51.4 billion by 2031, per Vervali Systems. That growth rate is pulling QA salaries upward, particularly for engineers with Playwright and CI/CD pipeline experience. Contract QA engineers, which are relevant if you are staffing through contract or contract-to-hire models, average $107,182 annually according to ZipRecruiter, roughly a 12% premium over the permanent equivalent.

KORE1’s placement data across 30+ U.S. metros shows the biggest comp jumps happen at the manual-to-automation transition (typically a $20,000 to $35,000 base increase) and again at the automation-to-SDET transition (another $15,000 to $25,000). Candidates who make both jumps within five years are rare and command accordingly. Our salary benchmark tool can help you calibrate ranges for your specific market and seniority level.

Tools and Frameworks Worth Naming in the JD

The testing framework landscape shifted hard in 2025-2026. Get the tool requirements wrong and you are either screening out your best candidates or attracting people whose experience does not transfer to your stack.

Browser automation: Playwright is the default now. 45% adoption among QA professionals. 30+ million monthly npm downloads. Microsoft backs it. If your team is starting fresh or migrating, Playwright is where the candidate pool is growing fastest. That said, Selenium is not dead. 22% market share, 49,000+ companies still running it, and a massive installed base in enterprise Java shops. If your existing suite is Selenium, requiring Playwright experience makes no sense. Require what you use. Note what is acceptable as equivalent.

Cypress holds 14% and has stabilized. Strong in the React and Vue.js ecosystem. Weaker for cross-browser testing and any scenario requiring multiple browser tabs, iframes, or file downloads.

API testing. Postman for manual and semi-automated API testing. REST Assured for Java-based automation. Pytest with requests for Python shops. K6 or Gatling for performance testing of APIs under load. Name the one your team uses.

CI/CD. GitHub Actions, Jenkins, GitLab CI, CircleCI. Your QA engineer will spend significant time debugging test failures in the pipeline. Name the platform. “Experience with CI/CD” without specifying which platform is unhelpful because the debugging experience between Jenkins and GitHub Actions is meaningfully different.

Test management. TestRail, Zephyr, qTest, or Xray for Jira. If your team tracks test cases formally, name the tool. If your team tracks tests as code in the repository with no separate management platform, say that instead. That distinction tells experienced candidates a lot about how your team operates.

74.6% of QA teams now use two or more automation frameworks simultaneously, according to TestDino’s 2026 survey. Your JD should reflect reality: name the primary framework, list acceptable alternatives, and note whether the hire will need to work across multiple tools.

Customizing the Template by Industry

The template above is a skeleton. What makes it work is the domain-specific detail you add. Here is what that customization looks like for two of the industries where we place QA engineers most frequently and where the compliance layer changes the entire shape of the job description.

Healthcare / regulated environments. Add HIPAA compliance testing to the responsibilities. Mention validation documentation if the product falls under FDA software regulations (IEC 62304 or 21 CFR Part 11). Require experience with audit trail testing and PHI data handling. None of that is optional in a regulated setting. If your product touches patient data and your QA engineer does not understand compliance testing, you have a regulatory gap that no amount of Playwright skill compensates for.

Fintech / payments. Add PCI-DSS compliance awareness. Mention transaction accuracy testing, reconciliation validation, and edge cases around currency formatting, timezone handling, and rounding behavior. If your platform processes payments, the QA engineer needs to understand that a $0.01 rounding error across 50,000 daily transactions is not a minor bug. It is a $500-per-day financial discrepancy that compounds. Require experience testing financial calculations and specify whether the role involves testing real payment processor integrations (Stripe, Adyen, FIS) versus internal ledger systems.

E-commerce, SaaS, and marketplace platforms each have their own testing surface areas. The template works for all of them, but the “About the Role” and “What You Will Do” sections must reflect the actual product. Generic JDs attract generic candidates, and in a market where the testing automation segment alone is growing at 14.5% annually and every company with an engineering team is competing for the same pool of experienced automation engineers, a generic posting is the fastest way to lose the candidates who have options.

Things People Ask About QA Engineer Job Descriptions

Do I actually need a separate QA engineer, or can developers test their own code?

Yes, developers should test their own code, and the good ones write unit tests, integration tests, and review each other’s pull requests. That is baseline engineering hygiene, not a substitute for a dedicated QA function. The QA engineer owns the test strategy, the regression suite, the edge cases that developers do not think about because they are too close to their own implementation to see the cracks, and the cross-functional testing that spans multiple services or teams where a change in one microservice quietly breaks a workflow three services downstream. Companies that eliminate QA roles and expect developers to cover everything tend to discover the gap about six months later, usually through a production incident that a dedicated QA engineer would have caught during the pre-release regression pass. Small teams with fewer than 10 engineers can sometimes defer a QA hire. Past that threshold, the cost of defect escapes, meaning bugs that reach production because nobody was systematically looking for them before the deploy went out, typically exceeds the fully loaded cost of a dedicated QA hire within the first six months.

How specific should I get on tools in the posting?

Name 3-4 tools your team actually uses and 1-2 acceptable alternatives. That is the right level. Too specific (“must have 3+ years of Playwright with TypeScript in a Next.js monorepo”) and you screen out excellent candidates who could ramp in two weeks. Too generic (“experience with test automation tools”) and you learn nothing from the resume. We ran a QA search last quarter where the client initially required “Selenium with Java” and got 12 applicants in three weeks. Broadened to “Selenium or Playwright, Java or Python” and got 47 in the next two weeks, including the person they eventually hired, a Playwright-Python engineer who had never once opened a Selenium project but was writing production-grade browser tests hooked into their GitHub Actions pipeline within her first sprint on the team.

Is a CS degree really necessary for QA roles?

Not for the vast majority of QA roles being hired today. For automation and SDET roles, coding ability matters and the person needs to write real code in Python, Java, or TypeScript that runs in production CI pipelines every day. The path to that ability does not. Computer science programs do not teach software testing in depth. Most QA-specific skills, test design, automation framework architecture, defect triage, CI/CD integration, are learned on the job or through focused training programs. Require the skills. Make the degree “preferred” or drop it entirely. You will widen your candidate pool by 30-40% without lowering quality, and in a market where the BLS projects 15% growth for this occupation through 2034, a wider pool is not optional.

What is the difference between QA engineer and SDET, really?

About $40,000 to $55,000 in annual salary at the senior level, which is the blunt way to frame it. SDETs write production-quality test infrastructure that other engineers consume. QA engineers write and execute tests for specific features or products. The SDET builds the testing platform. The QA engineer uses it. In practice, the line blurs at many companies, especially smaller ones where one person wears both hats. But if your job description says “QA Engineer” and the actual work involves building shared test frameworks, custom assertion libraries, and test environment provisioning tooling, call it an SDET and pay accordingly. Mislabeling the role costs you candidates who would apply to the honest title and would be excellent at the actual work, while simultaneously attracting people who saw “QA Engineer” in the headline and expected a completely different job than the one described in the interview.

Should I include salary in the posting?

Always. Twelve states plus multiple cities now require it by law, and even where it is not legally mandated, postings with salary ranges get 2-3x more qualified applicants. Use a band. $100K-$130K is fine. It tells candidates where the role sits on the seniority spectrum and prevents everyone from wasting time on a $40K mismatch that would have surfaced in the first phone screen anyway. The fear that posting salary invites lowball candidates is backwards. Posting salary filters out candidates who need $160K when your ceiling is $130K, which saves you from running those people through four rounds of interviews, getting emotionally committed to an offer, discovering the comp mismatch at the finish line, and losing three weeks while your best backup candidate accepts somewhere else.

Contract or direct hire for QA engineers?

Depends on timeline and uncertainty. If you need a QA engineer for a specific project or release cycle with a defined end date, contract staffing at roughly $50-$65/hour gets you someone productive without a long-term commitment. If you need ongoing QA ownership of a product, direct hire at the salary ranges above. Contract-to-hire works when you are not sure about the role’s scope yet. Start with a 3-6 month contract, evaluate fit, convert if it works. KORE1 fills QA roles across all three models, and the right structure depends on your team’s roadmap, not on which one sounds cheaper upfront.

Next Steps

Copy the template. Fill in the brackets with your actual product, tools, and team context. Delete the notes in parentheses. Post it.

If you need help writing a QA-specific JD for your team, calibrating salary ranges for your market, or sourcing qualified QA engineers directly, reach out to our team. We fill QA roles in 17 days on average across 30+ U.S. metros, through contract, contract-to-hire, and direct hire. Read the full QA engineer hiring guide for the complete process, or check our QA engineer interview questions to prepare your evaluation loop once candidates start applying.