QA engineer job description templates and guide: manual, automation/SDET, analyst, lead, and junior, with FLSA classification and when-to-hire guidance.
Six editable templates for general, manual, automation/SDET, analyst, lead, and junior QA roles, plus the when-to-hire, role-disambiguation, and FLSA guidance most templates skip.
A QA engineer makes sure software works the way it should before it reaches customers: designing and running tests, finding and documenting defects, and working with developers to ship reliable releases. The title is broad, though, and it covers very different jobs at very different pay tiers, from hands-on manual testing to coding-heavy automation. Getting the role, type, and classification right matters more than the duties list.
This guide explains what a QA engineer does, how the manual, automation, and lead variants differ, when a growing company actually needs one, and what the role pays, with six editable templates to download. For the fundamentals behind any posting, the guide to writing a job description is a useful companion.
TL;DR
A QA engineer tests software to catch defects before release. The title spans tiers: manual QA (lower cost), automation/SDET (coding-heavy, higher pay), and QA lead (management). Most software QA roles are exempt salaried professionals, with the closest federal occupation at a $102,610 median. Many early startups should wait and rely on developer testing first. Six editable templates below, by type, with FLSA and when-to-hire guidance built in.
What a QA Engineer Does
A QA engineer designs and runs tests, finds and documents defects, and works with developers to ship reliable software. The work blends hands-on testing with process: writing test cases, reproducing bugs, running regression before releases, and helping improve how the team catches problems before customers do.
The closest federal occupation is software quality assurance analysts and testers. The specific work varies widely by the type of QA role, which is why naming the type is the first and most important step in writing the description.
Manual vs Automation vs Lead
QA engineer is a vague title that spans different jobs and pay tiers. The single most important decision before posting is which type you actually need, because it determines the candidate pool, the skills you screen for, and the salary range.
Role
Focus
Coding
Typical pay tier
Manual QA / QA Analyst
Hand testing, bug finding
Little to none
Lower (genuine sub-$80K tier)
QA Engineer
Mixed manual and some automation
Some scripting
Mid (around the median)
QA Automation / SDET
Building automated test suites
Heavy
Higher
QA Lead / Manager
Strategy and people
Varies
Highest (management band)
A manual QA or QA analyst tests by hand and is the genuine lower-cost tier; a QA automation engineer or SDET writes test code and is a software engineering hire; a QA lead owns strategy and people. Posting a generic description when you need a specific type attracts the wrong candidates and misprices the role.
Duties and Responsibilities
QA duties cluster into four areas: test design and execution, defects and quality, automation and tooling, and collaboration and reporting. A strong job description picks the responsibilities that match the specific QA type, rather than listing every possible task.
Test design and execution
Design and write test cases and plans
Run functional and regression tests
Perform exploratory and edge-case testing
Defects and quality
Find and reproduce defects
File clear, reproducible bug reports
Verify fixes before release
Automation and tooling
Build and maintain automated tests
Integrate tests into CI/CD
Improve test frameworks and reliability
Collaboration and reporting
Work with developers and product
Define acceptance criteria together
Report quality and release readiness
The weighting shifts by role: a manual tester leans on the first two areas, an automation engineer on the third. For a structured way to scope the role, the guide to defining job responsibilities walks through the process.
Which Template Should You Use?
Pick the template by the type of QA role and the seniority. The core is the same across all six, but each emphasizes the duties, skills, and classification that fit a specific kind of QA hire.
QA Engineer (General)
Cross-purpose
The standard version: design and run tests, find and document defects, and work with developers to ship reliable releases. The baseline to adapt.
Manual QA / QA Analyst
Hands-on testing
For careful human testing rather than an automation build: run cases, validate features, file bugs. Often the most accessible QA hire for a smaller team.
QA Automation / SDET
Coding-heavy
For building automated test suites and CI/CD integration. A software engineering role that treats test infrastructure as code.
QA Analyst
Process focus
For a structured, analytical approach: test strategy, requirements analysis, test design, and quality metrics rather than pure automation.
QA Lead / Manager
Leadership
For owning test strategy and leading a QA team: standards, process, automation strategy, and people management across teams.
Junior / Entry-Level
First QA role
For a first hire into QA: run cases, file bugs, and learn the process with mentorship and a clear path to grow.
Match the Template to the Role
General-purpose QA: QA Engineer (General). Hands-on human testing: Manual QA / QA Analyst. Building automated tests and CI/CD: QA Automation / SDET. A structured, analytical approach: QA Analyst. Owning strategy and leading a team: QA Lead / Manager. A first hire into QA with mentorship: Junior / Entry-Level.
6 Editable QA Engineer Job Description Templates
Download all six as a single editable Word document, or copy individual templates. Each follows the same structure: company and job summary, key responsibilities, qualifications, a compensation block, and how to apply, with an EEO statement. Fill in the brackets and post.
Download All 6 Job Description Templates
General, manual, automation/SDET, analyst, lead, and junior. One editable DOCX.
Template 1: QA Engineer (General)
The standard version: design and run tests, find and document defects, and work with developers to ship reliable releases. The baseline to adapt.
[One or two sentences about your product, your engineering team, and the quality
challenges this QA engineer will help solve.]
JOB SUMMARY
[Company Name] is hiring a QA Engineer to make sure our software works the way it
should. You will design and run tests, find and document defects, and work with
developers to ship reliable releases. The role blends hands-on testing with
process: writing test cases, reproducing bugs, and helping improve how we catch
problems before customers do.
KEY RESPONSIBILITIES
•Design, write, and execute test cases and test plans
•Find, reproduce, and document defects with clear repro steps
•Verify fixes and run regression testing before releases
•Collaborate with developers and product on quality and acceptance criteria
•Perform functional, integration, and exploratory testing
•Contribute to test automation where appropriate
•Track quality metrics and report on release readiness
REQUIRED QUALIFICATIONS
•Bachelor's in computer science or related field, or equivalent experience
•[2-4] years in software QA or testing
•Strong understanding of QA methodology and the software lifecycle
•Experience with test case management and bug tracking tools
•Some scripting or automation experience a plus
•Detail-oriented, methodical, and a clear communicator
COMPENSATION AND HOW TO APPLY
Salary range: $_____ to $_____ per year
This role is exempt (computer employee / professional).
To apply, send your resume to __.
[Company Name] is an equal opportunity employer.
Template 2: Manual QA / QA Analyst
For careful human testing rather than an automation build: run cases, validate features, and file bugs. Often the most accessible QA hire for a smaller team.
For building automated test suites and CI/CD integration: a coding-heavy software engineering role for someone who treats test infrastructure as software.
[Company Name] is hiring a Junior QA Engineer to start a career in software
quality. This is an entry-level role: you will run test cases, file bugs, and
learn our testing process, with mentorship and a clear path to grow. We are
looking for a detail-oriented person who is curious about how software breaks, not
years of experience.
KEY RESPONSIBILITIES
•Run test cases and validate features against requirements
•File clear, reproducible bug reports
•Help with regression and exploratory testing
•Learn test automation basics with mentorship
•Maintain test documentation
•Support the QA team and grow your testing skills
REQUIRED QUALIFICATIONS
•Degree, bootcamp, or equivalent interest in software/QA
•0-2 years of experience; internships or projects count
•Detail-oriented, curious, and methodical
•Willingness to learn testing tools and automation
•Clear written communication
GROWTH PATH
Clear path from Junior QA to QA Engineer, then to QA Automation Engineer or QA
Lead with experience and strong performance.
COMPENSATION AND HOW TO APPLY
Salary range: $_____ to $_____ per year
To apply, send your resume to __.
[Company Name] is an equal opportunity employer.
When to Hire, Classification, and Pay
The decisions that make or break this hire come before the duties list: whether you need dedicated QA yet, which type you need, how to classify it, and how to set the pay. Get these right and the posting attracts the right candidate at the right cost.
Before product-market fit, usually skip a dedicated QA hire
The strong practitioner consensus is that a very early startup should not rush to hire a dedicated QA engineer. Before product-market fit, the product changes too fast for a formal test process to pay off, and developer-owned testing plus modern tooling usually covers the need. A dedicated QA hire tends to make sense at the scaling stage, often somewhere around Series A to Series B, when the codebase, the team, and the cost of bugs have all grown enough that quality needs a dedicated owner. Hiring too early ties up budget that an early team usually needs elsewhere. If you are still searching for fit, developer testing and lightweight tooling are typically the better call.
Know which QA role you actually need
QA engineer is a vague title that spans very different jobs and pay tiers. A manual QA or QA analyst runs test cases by hand and finds the bugs automation misses, and is the genuine lower-cost tier. A QA automation engineer or SDET writes test code and builds CI/CD test infrastructure, which is a software engineering role at a software engineering salary. A QA lead or manager owns strategy and people. Posting for a generic QA engineer when you need a manual tester, or vice versa, attracts the wrong candidates and misprices the role. Decide which job you are filling first, then use the matching template on this page.
Most software QA roles are exempt salaried professionals
A software QA engineer typically qualifies as exempt under the FLSA computer-employee or professional exemption, meaning the role is salaried and not entitled to overtime, provided it is paid at or above the federal threshold of $684 per week or $27.63 per hour for the computer-employee test. This is a white-collar professional, not an hourly operational worker. The exception is a routine, execution-only manual QA role, which can be non-exempt depending on its duties. Exemption is determined by the actual duties and salary, not the title. Classify each role on its facts. This is general information, not legal advice.
Expect a six-figure budget, less at the junior and manual tier
QA engineering is a six-figure role at the median, and the budget scales with the type of QA work and the company size. The closest federal occupation, software quality assurance analysts and testers, reports a median around $102,610, with automation and SDET roles at the higher end and manual QA at the lower. The junior and manual-QA tier, roughly the low-$60,000s to low-$80,000s, is the slice closest to a smaller company's budget, and the market has been compressing pay on routine manual work as AI-assisted testing absorbs some of it. Set the range to the specific QA role and your market, not to the generic title. This is general information, not compensation advice.
A Six-Figure, Usually Exempt Role
The closest federal occupation, software quality assurance analysts and testers, had a median annual wage of $102,610 in May 2024, with a range from about $60,690 to $166,960 (O*NET / BLS). Most software QA roles are exempt (salaried at or above $684 per week, or $27.63 per hour under the computer-employee test). This is general information, not legal advice.
QA hiring screens for different skills by tier, but a few things hold across the board. Scale the requirements to the specific role rather than copying a generic list.
Requirement
What to look for
Education
Bachelor's in CS or related, or equivalent experience; flexible for manual roles
Experience
0-2 years junior, 2-5 mid, 5-8+ for lead, scaled to the tier
Methodology
Understanding of QA methodology and the software lifecycle
Tools
Jira, TestRail, and bug tracking; automation frameworks for SDET roles
Coding
Little for manual QA; heavy for automation and SDET
Classification
Exempt for most software QA; non-exempt for routine manual roles
Keep the posting neutral and inclusive, since the EEOC prohibits job advertisements that show a preference based on a protected characteristic. For the operational quality roles outside software, the quality assurance and quality analyst templates cover those settings.
From Hiring to Onboarding
Once a candidate accepts, the job description becomes the basis for the offer and onboarding. A QA hire especially benefits from a structured first week, since they need access to repos, test environments, and tools, plus a clear picture of your release process before they can be effective.
Send and sign the offer
Confirm the salary, exempt classification, and start date in writing, with an offer letter the new hire can e-sign.
Onboard into the codebase and process
Set up access to repos, test environments, and tools, and walk through your QA process and release workflow.
Set the first 30, 60, 90 days
Give a new QA hire clear early goals: learn the product, own a test area, and ramp into automation or strategy.
Store the records
Keep the signed offer, tax forms, and onboarding documents organized in one place.
Once your offer is ready, the offer letter template handles the next step, and an onboarding template gives the new hire a structured start. FirstHR connects the offer, e-signature, onboarding workflow, and document management in one place, so a growing company can run the full process from one system. FirstHR is an onboarding and HR platform, not a testing or engineering tool, and it does not run payroll, so connect those separately. Applicant tracking is coming soon to FirstHR.
Key Takeaways
A QA engineer tests software to catch defects before release; the title spans very different jobs and pay tiers.
Decide which type you need first: manual QA (lower cost), automation/SDET (coding-heavy, higher pay), or QA lead (management).
Most software QA roles are exempt salaried professionals; routine manual QA can be non-exempt. Classify by duties, not title.
The closest federal occupation reports a $102,610 median, with manual roles lower and automation and lead roles higher.
Many early startups should wait and rely on developer-owned testing; dedicated QA usually makes sense at the scaling stage.
Use the template that matches the type and seniority, and set the salary range to that specific tier.
Frequently Asked Questions
What does a QA engineer do?
A QA engineer makes sure software works the way it should before it reaches customers. Day to day, that means designing and running test cases, finding and documenting defects with clear reproduction steps, verifying fixes, running regression testing before releases, and working with developers and product on quality and acceptance criteria. Depending on the role, a QA engineer may focus on manual and exploratory testing, build automated test suites, or both. The goal is to catch problems early and reduce the cost and risk of shipping broken software. The closest federal occupation is software quality assurance analysts and testers. The work blends hands-on testing with process, and the specific mix depends heavily on whether the role is manual QA, automation, or analysis. This is general information, not legal advice.
What is the difference between manual QA, automation QA, and an SDET?
These are different jobs at different pay tiers, even though the titles get used loosely. A manual QA or QA analyst tests software by hand: running test cases, validating features, doing exploratory testing, and filing bugs, with little or no coding. This is the genuine lower-cost tier. A QA automation engineer or SDET (software development engineer in test) writes code to build automated test suites and integrate them into the CI/CD pipeline; this is a software engineering role at a software engineering salary. Some roles blend the two. Knowing which one you need before you post is the single most important decision, because it determines the candidate pool, the pay range, and the skills you screen for. Posting for a generic QA engineer when you need a manual tester wastes everyone's time. This is general information, not legal advice.
Is a QA engineer exempt or non-exempt under the FLSA?
A software QA engineer is typically exempt under the FLSA computer-employee or professional exemption, meaning the role is salaried and not entitled to overtime, provided it is paid at or above the federal threshold of $684 per week, or $27.63 per hour under the computer-employee test. The role is a white-collar software professional, which is the profile the exemption is designed for. The main exception is a routine, execution-only manual QA role whose duties do not meet the exemption test; that role can be non-exempt. Exemption is always determined by the actual job duties and salary, not by the job title. Classify each role on its specific facts, and when in doubt, treat a routine role as non-exempt. This is general information, not legal advice.
How much does a QA engineer make?
A QA engineer is a six-figure role at the median. The closest federal occupation, software quality assurance analysts and testers, reported a median annual wage of $102,610 as of the May 2024 federal data, with the lowest 10 percent under about $60,690 and the highest 10 percent over about $166,960. Pay varies sharply by the type of QA: manual QA and QA analyst roles sit at the lower end, often in the low-$60,000s to low-$80,000s, while automation engineers and SDETs earn well into six figures, and QA leads and managers higher still. Company size matters too, with smaller companies paying less than large tech employers. Set the range to the specific QA role and your local market rather than to the generic title. This is general information, not compensation advice.
When should a startup hire its first QA engineer?
Most early-stage startups should wait. The common practitioner guidance is to skip a dedicated QA hire before product-market fit, because the product is changing too fast for a formal test process to pay off, and developer-owned testing plus modern tooling usually covers the need. The inflection point for a dedicated QA engineer tends to come at the scaling stage, often somewhere around Series A to Series B, when the codebase, team, and cost of bugs have grown enough that quality needs a dedicated owner. A fully loaded QA hire is a significant cost, so hiring too early ties up budget an early team usually needs elsewhere. If you do hire, decide whether you need manual QA, automation, or a lead, and use the matching template. This is general information, not legal advice.
Do you need a QA engineer if developers test their own code?
Not always, especially early on. Many successful engineering organizations rely on developer-owned quality, where engineers write and maintain their own tests rather than handing testing to a separate QA function, and some large tech companies operate this way deliberately. For an early-stage or small team, developer testing combined with automated tooling is often enough, and it keeps the team lean. A dedicated QA engineer earns its cost when the product and team scale, when the cost of bugs in production grows, or when the testing needs exceed what developers can reasonably own alongside building features. The decision is about scale and risk, not a rule that every team needs QA. Assess where your product and team actually are. This is general information, not legal advice.
What skills should a QA engineer have?
It depends on the type of QA role. A manual QA or QA analyst needs strong attention to detail, methodical thinking, clear bug-reporting skills, and familiarity with test case management and bug tracking tools like Jira and TestRail. A QA automation engineer or SDET needs all of that plus solid coding skills in a language like Python, JavaScript, Java, or C#, experience with automation frameworks such as Selenium, Playwright, or Cypress, and familiarity with CI/CD pipelines and version control. Across all QA roles, a strong understanding of QA methodology and the software development lifecycle matters, along with clear communication for working with developers and product. Match the required skills to the specific role you are hiring, not to a generic checklist. This is general information, not legal advice.
What should a QA engineer job description include?
Start by deciding which QA role you actually need: general, manual, automation/SDET, analyst, lead, or junior. Include a short company summary, a job summary that makes the focus clear, and responsibilities grouped into test design and execution, defects and quality, automation and tooling, and collaboration and reporting. State the FLSA classification, exempt for most software QA roles, non-exempt for routine manual roles, and set a salary range matched to the specific tier and your market. List the required skills and experience for that tier, and for a junior role name the career path. Close with an equal opportunity statement and clear apply instructions, then bridge into onboarding. Above all, do not post a generic QA engineer description when you need a specific type. This is general information, not legal advice.
