QA engineer job description template: manual or automation, release pressure, ISTQB and exempt status
On this page
"QA engineer" can mean a tester who explores a mobile app before each release, an engineer who builds and maintains the automated test framework, or a specialist who load-tests an API. Postings that list "manual and automated testing, Selenium, Cypress, Playwright, API testing, performance testing, CI/CD" ask for all three and describe none. The facts that matter to a candidate are what is tested, how often it ships, how much is automated today and what the quality engineer is expected to change. Below is a copy-ready QA engineer job description template, the ISTQB and classification lines checked against sources, screening questions and scorecard rows, and the mistakes that make QA postings unreadable. The general method is in how to write a job description that screens.
Describe the testing seat, not the tool list
| Seat | What fills the sprint | Must-have that separates it |
|---|---|---|
| Exploratory and functional QA | Test design, exploratory sessions, regression passes, bug reports | Has found serious bugs that scripted tests missed, and written reports developers could act on |
| Test automation (SDET) | Writing and maintaining UI and API tests, fixing flaky tests, CI pipeline work | Has built or maintained an automated suite that ran in CI and was trusted |
| Performance and reliability | Load and stress tests, capacity findings, test environment setup | Has designed a load test and turned results into a fix |
| Mobile QA | Device and OS coverage, app store builds, crash and network edge cases | Has tested native apps across real devices and release channels |
| QA lead | Test strategy, release sign-off, coaching testers, metrics | Has owned a release decision and the quality process for a team |
Then set down the context: the product (web, mobile, API, embedded), the release cadence, the ratio of developers to QA, how much regression is automated today, and whether QA can block a release. A candidate reading "one QA engineer for twelve developers, weekly releases, about a third of regression automated" (an invented example) knows exactly what they are walking into.
The QA engineer job description template
[Senior] QA Engineer, [Exploratory / Automation / Performance]
[Company], [city] — [On-site / Hybrid: days / Remote within: states]
Pay: $[min]–$[max] per year. [Benefits summary, if required.]
[Exempt / overtime-eligible, after review.]
SUMMARY
You will test [product: web app / mobile apps / public API] used by
[customers]. We release [every N days / weekly / continuously], with
[N] developers and [N] QA engineers. About [share] of our regression
is automated in [framework]; your job is to [raise that / keep it
trustworthy / find what automation misses]. You will report to
[title].
WHAT YOU WILL DO
- Design tests from requirements and from how customers actually use
[product].
- [Exploratory: run focused test sessions before each release and
report what you find.]
- [Automation: write and maintain [UI / API] tests in [language and
framework], and fix flaky tests at the cause.]
- Write bug reports with steps, evidence and impact that developers
can act on.
- Take part in release decisions: [sign off / advise on] go or
no-go.
- Work with developers early, in story refinement and code review.
YOU MUST HAVE
- Tested a [product type] that shipped to real users on a regular
cadence.
- Found and reported bugs that mattered, and explained their impact.
- [Automation: written automated tests in [language] that ran in
CI.]
- [API seats: tested APIs directly, including error cases.]
NICE TO HAVE
- ISTQB Certified Tester Foundation Level or advanced level.
- Experience with [framework], [CI tool], [device cloud].
- [Domain: payments, healthcare, regulated software.]
If you meet the must-haves and none of these, please apply.
FIXED CONDITIONS
- Release nights or weekend checks: [how often, how handled].
HOW WE HIRE
[Recruiter screen; conversation with [title]; a [60-minute live
testing session on a sample app / take-home of at most N hours];
meeting the team.]
[EEO STATEMENT]
Contact [address] for any adjustment to the process.ISTQB, classification and pay lines
Not legal advice. Classification points were checked against the Department of Labor and federal regulations as of October 2026. Some states set different thresholds for computer professionals; confirm with counsel.
ISTQB. The current foundation certification is the Certified Tester Foundation Level (CTFL) v4.0, and ISTQB describes it as the prerequisite for its other certifications where Foundation Level is required, including the advanced Test Analyst, Technical Test Analyst and Test Management certifications (ISTQB). Use it as a nice-to-have. It shows shared vocabulary, not the ability to find a bug no one expected or to keep a test suite fast.
Exempt or nonexempt. The computer employee exemption covers employees whose primary duty includes the "design, development, documentation, analysis, creation, testing or modification of computer systems or programs," paid at least $684 a week on a salary basis or $27.63 an hour (DOL Fact Sheet 17E). The same fact sheet says job titles do not determine the result, and the regulation excludes employees whose work depends on computers but who are not primarily engaged in systems analysis and programming work (29 CFR 541.401). An automation engineer writing test code is a different case from a tester following scripts someone else wrote; have the duties reviewed and post the result.
Pay. Post the approved range; see pay transparency laws by state. BLS covers this work in the Occupational Outlook Handbook profile Software Developers, Quality Assurance Analysts, and Testers (last modified August 27, 2026), which reports quality assurance analysts and testers separately from developers. This page does not quote figures. Close with your EEO statement and an accommodation contact.
From must-haves to screening questions and scorecard rows
| Must-have | Screening question | Scorecard competency | Evidence of a strong answer |
|---|---|---|---|
| Finding bugs that matter | "What is the most serious bug you found before release? How did you think to look there?" | Test design and curiosity | A risk-based reason for looking, not luck; explains the user impact |
| Bug reporting | "Tell me about a bug a developer could not reproduce. What did you do?" | Clear evidence | Narrowed conditions, captured logs or data, worked with the developer rather than around them |
| Automation in CI (automation seats) | "How did you deal with flaky tests in your last suite?" | Automation quality | Found causes such as timing or shared data; quarantined, fixed or deleted with a reason |
| Release judgment | "When did you recommend not shipping, and what happened?" | Quality judgment | Weighed risk against cost, stated it plainly, accepted the decision and followed up |
| Working early with developers | "How do you get involved before code is written?" | Collaboration | Asks questions in refinement, adds acceptance criteria, pairs on testability |
The full first call is in QA engineer phone screen questions, and the first quarter after hiring is planned in the 30-60-90 day plan for QA engineers. If the role is mostly product code with some testing, the software engineer job description template fits better. For take-home exercises, see how to evaluate a take-home assignment.
Common mistakes in QA engineer job descriptions
Every framework as a requirement
Requiring three UI frameworks and two languages tells candidates you have not decided. Require the language the suite is written in and treat the rest as environment.
"Manual" said dismissively
Skilled exploratory testing finds the bugs that automation cannot. If you need it, describe it with respect, or you will attract people looking for the exit.
Hiding the ratio
One QA engineer for fifteen developers is a very different job from one for four. State it.
No authority
Say whether QA can stop a release. A tester expected to own quality without any say in shipping will leave.
Unpaid automation projects
A take-home that builds a framework from scratch is free consulting. Cap the time and provide a starter project.
Before you publish
- The product, release cadence, team ratio and current automation level are stated.
- The seat (exploratory, automation, performance, mobile, lead) is clear in the title and summary.
- Only the languages and frameworks in daily use are required.
- Release authority and any release-night work are described.
- Classification is reviewed, and an approved pay range, the EEO statement and an accommodation contact close the posting.
Paste the final posting into Interview Signal and the screen's guide follows these must-haves; the scorecard then quotes the bugs and test suites the candidate described.
Questions people ask
Should a QA engineer job description require ISTQB certification?
Usually as a nice-to-have. The ISTQB Certified Tester Foundation Level (CTFL) shows a shared vocabulary for testing, and it is the prerequisite for ISTQB's advanced levels, but it does not show whether someone can find important bugs or build a maintainable automation suite. Screen for that work directly.
What is the difference between a QA engineer and an SDET posting?
Titles vary by company. In general, an SDET or automation engineer spends most of the week writing test code and test infrastructure, close to a developer, while a QA engineer may split time between exploratory testing, test design and some automation. Describe the split rather than relying on the title.
Is a QA engineer exempt from overtime?
Many are, under the computer employee exemption, which lists testing of computer systems or programs among qualifying primary duties and requires at least $684 a week on a salary basis or $27.63 an hour. Job titles do not decide it. A tester who mainly runs scripts written by others needs a closer review of the actual duties.
Should QA candidates do a take-home exercise?
A short, bounded exercise works well: give a small app or specification and ask for a test approach and the bugs they find, or a few automated tests against a provided project. Cap the time, use the same rubric for everyone and discuss their choices afterward.