6 templates for teams hiring their first or next automation engineer: general automation, SDET, mobile, API, performance, and automation lead. Download as DOCX.
The first QA automation job description I ever wrote was wrong in a way that took two months to discover. I listed a framework we used, asked for five years of it, and got a stack of resumes from people who had written the same brittle test suite five times. The engineer we eventually hired had never touched that framework and rebuilt our testing in six weeks.
That is the recurring failure in this posting. QA automation is one of the few engineering roles where the tool list is easy to write and almost entirely beside the point, so it crowds out the things that actually predict success: whether the framework already exists, what the release cadence is, and how much of the week is genuinely spent writing code.
At FirstHR we build hiring templates for teams without a recruiting function. The six below cover a general automation engineer, an SDET, mobile, API, performance, and an automation lead, each with the classification note and screening guidance that generic postings leave out. More sit in the hiring templates library.
TL;DR
A QA automation engineer writes and maintains the code that tests your product inside your build pipeline. It is a coding hire, not a manual testing hire. The role is usually exempt under the computer employee rules, which require both a qualifying duty and $684 per week or $27.63 per hour. The closest federal wage benchmark is $104,300. Six templates below.
What a QA Automation Engineer Actually Owns
A QA automation engineer owns the automated tests and the pipeline that runs them, which makes this a software engineering hire rather than a testing hire. The output is code: test suites, fixtures, and the tooling that keeps them fast enough to run on every change.
The distinction from manual QA is not seniority, it is the nature of the work. Both are legitimate roles and both find real defects. But they draw from different candidate pools at different price points, and a posting that blurs them attracts people who fit neither.
Automation engineer
Writes the tests
Builds and maintains automated suites against an existing framework, triages failures, and expands coverage. The most common hire, and the one most small teams actually need first.
SDET
Builds what tests run on
A software engineer pointed at quality. Owns frameworks, harnesses, test data, and pipeline execution. Reviewed as a developer, paid as a developer, and scarce at the salary most small teams budget.
Manual QA or tester
Different job, different pay band
Tests by hand, explores, and exercises judgment about user experience. Genuinely valuable and genuinely cheaper. Posting for automation when you want this attracts candidates you cannot afford.
Automation lead or architect
Owns the strategy
Decides what gets automated, which tools the company standardizes on, and what blocks a release. Worth hiring when several teams are duplicating test effort, not before.
Say Whether the Framework Already Exists
This is the single most useful sentence you can add, and almost no posting includes it. Extending a working framework and building one from nothing are different jobs requiring different experience levels. A candidate who thrives adding coverage to a mature suite may struggle to make architectural decisions from a blank repository, and an engineer who loves greenfield work will be bored maintaining someone else's. Write one line: the framework exists and needs expanding, or there is nothing yet and you will design it.
The fourth responsibility, and the one that separates a good automation engineer from an expensive one, is judgment about what not to automate. A suite that tries to cover every path becomes slow and unstable, and once engineers stop trusting a red build they start ignoring it. Coverage without trust is worse than no coverage.
What Belongs in the Posting
A job description does four jobs at once: it sells the work, it filters unqualified applicants, it protects you legally, and it closes the candidate. Most engineering postings do the first and the second badly and skip the other two entirely. Here is the full inventory.
The parts engineers read first
The product and what makes testing it interesting
Team size and release cadence
Which layers you automate today and which you do not
Whether the framework exists or needs building
The parts that filter applicants
Languages and frameworks, marked required or preferred
CI/CD systems actually in use
Years of experience stated as a range, not a floor
How much of the week is coding versus manual testing
The parts that protect you
FLSA classification stated on the posting
Essential functions written plainly
Equal opportunity statement
On-call or release-window expectations, if any
The parts that win the hire
Salary range in good faith
Autonomy over tooling decisions
Who the role reports to and works beside
Whether test work is respected or treated as overhead
The omission that costs small teams most is the release cadence. An engineer evaluating an automation role wants to know how often you ship, because that determines whether the suite must run in eight minutes or can run overnight, and that single fact shapes the entire technical approach. Our guide to writing a job description covers the general structure in more depth.
Download all six as one file or copy them individually. Each follows the same structure: company overview, position summary, key responsibilities, required and preferred qualifications, a classification note, an equal opportunity statement, and how to apply. The bracketed fields are the only parts you need to change.
Download All 6 QA Automation Engineer Job Description Templates
General automation, SDET, mobile, API, performance, and automation lead. All in one download.
QA Automation Engineer
The general hire
The standard role: writes and maintains suites, keeps the pipeline green, and decides what is worth automating. Start here unless you have a reason not to.
SDET
Infrastructure ownership
For teams that need the framework built rather than extended. Screened and paid as a software engineering hire, because that is what it is.
Mobile Test Automation
Devices and store releases
For app teams: device matrix, simulators, store submission gates, and the offline and upgrade paths that only break on real hardware.
API / Backend Automation
Service-layer coverage
For service-heavy products: contract tests, request and response validation, test data ownership, and integration coverage without a browser.
Performance / Load
Finds the breaking point
For traffic spikes and scaling questions: load, stress, and soak scenarios, performance budgets, and bottleneck analysis tied to real fixes.
Automation Lead / Architect
Strategy plus hands-on
For organizations with several teams and no shared standard. Owns tooling decisions, release gates, and the quality numbers leadership reads.
Template 1: QA Automation Engineer (General)
The standard role: writing and maintaining suites, keeping the pipeline green, and deciding what is worth automating. Start here unless you have a specific reason not to.
QA Automation Engineer Job Description (General)
QA AUTOMATION ENGINEER JOB DESCRIPTION
Company: __ ([City, State])
Location: [on-site / hybrid / remote]
Reports to: [QA Lead / Engineering Manager / VP Engineering]
Employment type: Full-time
FLSA status: Exempt (computer employee; confirm by duties and pay)
Compensation: $_____ to $_____ per year
ABOUT [COMPANY NAME]
[Company Name] builds [product description] for [customer type]. Our engineering
team is [number] people shipping to production [daily / weekly / every sprint].
We are hiring our [first / next] QA Automation Engineer to make that release
cadence safe to keep.
POSITION SUMMARY
The QA Automation Engineer designs, writes, and maintains the automated tests
that verify our [web / mobile / API] product before it reaches customers. This is
a coding role: you will treat test suites and test infrastructure as production
software, and you will own the health of the pipeline that runs them.
KEY RESPONSIBILITIES
•Write and maintain automated tests at the [unit / API / UI] layers
•Own the test framework: structure, helpers, fixtures, and test data
•Integrate suites into the CI/CD pipeline so tests run on every change
•Triage failures daily and separate real defects from unstable tests
•Reduce suite run time and keep the pass rate trustworthy
•Decide with the team what to automate and what stays exploratory
•Work with developers on testability before features are built
•Report coverage, escaped defects, and release risk in plain language
REQUIRED QUALIFICATIONS
•[2-5]+ years writing test automation or application code
•Experience with [Playwright / Cypress / Selenium / your framework]
•Hands-on experience with CI/CD [GitHub Actions / GitLab CI / Jenkins]
•Comfort with version control, code review, and reading application code
•Judgment about what is worth automating and what is not
PREFERRED
•API testing, contract testing, or performance testing experience
•Experience in [your domain: fintech, health, e-commerce, devtools]
•ISTQB or an equivalent test certification
CLASSIFICATION NOTE (read before posting)
Most QA automation roles meet the FLSA computer employee exemption, which
requires both a qualifying primary duty (systems analysis, design, development,
or testing of computer systems or programs) and pay of at least $684 per week on
a salary basis, or at least $27.63 per hour. Both halves must be true. A junior
tester who mainly executes scripted test cases by hand may not qualify and would
be non-exempt and owed overtime. Classify on the actual duties, not the title.
This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_____ to $_____ per year, [benefits summary]
To apply, email __ with your resume and a link to test code
you have written.
Template 2: SDET (Software Development Engineer in Test)
For teams that need the framework built rather than extended. Screen and pay this as a software engineering hire. If the scope is closer to general application work, the software engineer templates are the better starting point.
SDET (Software Development Engineer in Test) Job Description
SDET JOB DESCRIPTION (SOFTWARE DEVELOPMENT ENGINEER IN TEST)
Company: __ ([City, State])
Location: [on-site / hybrid / remote]
Reports to: [Engineering Manager / Head of Platform]
Employment type: Full-time
FLSA status: Exempt (computer employee)
Compensation: $_____ to $_____ per year
ABOUT THIS ROLE
[Company Name] is hiring an SDET to build the tooling that other engineers test
with. This is a software engineering role that happens to point at quality: you
will spend most of your week writing code that is not product code, and the
people who depend on it are developers.
POSITION SUMMARY
The SDET builds and owns test frameworks, harnesses, fixtures, and environments,
then makes them fast and reliable enough that the whole engineering team uses
them without being asked. Writing individual test cases is part of the job but
not the center of it.
KEY RESPONSIBILITIES
•Design and build the test framework and shared test libraries
•Build test data management, seeding, and environment provisioning
•Own CI/CD test execution: parallelization, sharding, and run time
•Instrument flaky-test detection, quarantine, and reporting
•Write tests at the layer where they are cheapest to maintain
•Review other engineers' test code and raise the standard
•Build tooling for local reproduction of pipeline failures
•Partner with platform and release engineering on deployment gates
REQUIRED QUALIFICATIONS
•[3-6]+ years in software engineering, with test infrastructure ownership
•Strong programming skills in [language]; you will be reviewed as a developer
•Deep CI/CD experience and comfort with containers and build systems
•Track record of taking a slow, unreliable suite and making it trustworthy
•Ability to influence developers who do not report to you
PREFERRED
•Experience with distributed systems or microservice test strategy
•Open-source contributions to testing tools
•Experience standing up a test practice from scratch
CLASSIFICATION NOTE
An SDET is a software engineer and is exempt under the FLSA computer employee
exemption when paid at least $684 per week on a salary basis, or $27.63 per hour,
and when the primary duty is the design, development, or testing of computer
systems or programs. The exemption does not depend on the job title. This is
general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_____ to $_____ per year, [equity], [benefits]
To apply, email __ with your resume and a repository or
sample of test infrastructure you designed.
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
For app teams: the device matrix, simulators and real hardware, store submission gates, and the offline, permission, and upgrade paths that only break outside the simulator.
Mobile Test Automation Engineer Job Description
MOBILE TEST AUTOMATION ENGINEER JOB DESCRIPTION
Company: __ ([City, State])
Platforms: [iOS / Android / both]
Reports to: [QA Lead / Mobile Engineering Manager]
Employment type: Full-time
FLSA status: Exempt (computer employee)
Compensation: $_____ to $_____ per year
ABOUT THIS ROLE
[Company Name] ships a [iOS / Android / cross-platform] app to [number] users on
a [weekly / biweekly] release train. App store review makes a bad release
expensive to undo, so we are hiring a Mobile Test Automation Engineer to catch
problems before submission rather than after.
POSITION SUMMARY
The Mobile Test Automation Engineer builds and maintains automated test coverage
across real devices and simulators, keeps the mobile pipeline green, and owns the
device and OS version matrix we commit to supporting.
KEY RESPONSIBILITIES
•Build automated UI and integration tests for [iOS / Android / both]
•Maintain the device and OS version matrix and the test lab or device cloud
•Integrate mobile test runs into CI on every pull request and release build
•Automate checks for offline behavior, permissions, deep links, and upgrades
•Investigate crashes and correlate them with crash reporting data
•Verify accessibility behavior with platform accessibility tooling
•Run pre-submission regression before each store release
•Keep test run time inside the release train's schedule
REQUIRED QUALIFICATIONS
•[2-5]+ years automating mobile applications
•Experience with [Appium / XCUITest / Espresso / Maestro]
•Experience with a device farm or physical device lab
•Understanding of mobile release mechanics and store review timelines
PREFERRED
•Experience with [React Native / Flutter] test tooling
•Performance and battery profiling on device
•Experience with staged rollouts and release health monitoring
CLASSIFICATION NOTE
This is an exempt computer employee role when the pay tests are met ($684 per
week salaried or $27.63 per hour) and the primary duty is the design and testing
of computer programs. If the role is structured as contract or agency device
testing, review the working relationship carefully before treating anyone as an
independent contractor. This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_____ to $_____ per year, [benefits summary]
To apply, email __ with your resume and the app stores or
projects you have tested.
Template 4: API / Backend Test Automation Engineer
For service-heavy products: contract tests between services, request and response validation, test data ownership, and integration coverage that runs without a browser.
API / Backend Test Automation Engineer Job Description
API / BACKEND TEST AUTOMATION ENGINEER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [QA Lead / Backend Engineering Manager]
Employment type: Full-time
FLSA status: Exempt (computer employee)
Compensation: $_____ to $_____ per year
ABOUT THIS ROLE
[Company Name] runs [number] services behind [a public API / an internal
platform]. Most of our real risk lives below the interface, where a contract
change breaks a consumer nobody remembered. We are hiring an API Test Automation
Engineer to make that class of failure visible in the pipeline.
POSITION SUMMARY
The API Test Automation Engineer builds automated coverage at the service layer:
request and response validation, contract tests between services, data setup and
teardown, and integration tests that run without a browser.
KEY RESPONSIBILITIES
•Write automated tests against [REST / GraphQL / gRPC] endpoints
•Build and maintain contract tests between producer and consumer services
•Own test data: fixtures, factories, seeding, and cleanup
•Validate authentication, authorization, and error handling paths
•Mock or stub third-party dependencies so suites stay deterministic
•Add regression coverage for every production incident with a service cause
•Keep service-layer suites fast enough to gate every pull request
•Document the coverage map so the team knows what is not tested
REQUIRED QUALIFICATIONS
•[2-5]+ years automating tests against services and APIs
•Proficiency in [Python / JavaScript / Java / Go]
•Experience with [Postman / REST Assured / pytest / your stack]
•Solid understanding of HTTP, status codes, auth flows, and JSON schemas
•Working knowledge of SQL and the ability to verify state in a database
•Comfort reading backend application code
PREFERRED
•Contract testing experience [Pact or equivalent]
•Message queue or event-driven testing experience
•Experience testing in a microservice environment
CLASSIFICATION NOTE
Exempt computer employee when the primary duty is the design, development, or
testing of computer systems or programs and the pay test is met ($684 per week
salaried or $27.63 per hour). This is general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_____ to $_____ per year, [benefits summary]
To apply, email __ with your resume and a description of a
contract or integration bug your tests caught.
Template 5: Performance / Load Test Automation Engineer
For scaling and traffic questions: load, stress, and soak scenarios, performance budgets agreed with engineering, and bottleneck analysis that ends in a fix. Where the work leans toward infrastructure, compare it against the DevOps engineer templates.
Performance / Load Test Automation Engineer Job Description
PERFORMANCE / LOAD TEST AUTOMATION ENGINEER JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [QA Lead / Platform Engineering Manager]
Employment type: Full-time [or contract for a defined engagement]
bursts]. We are hiring a Performance Test Automation Engineer to tell us where
the system breaks before our customers find out, and to keep that answer current
as the product changes.
POSITION SUMMARY
The Performance Test Automation Engineer designs and automates load, stress, and
soak tests, sets the performance budgets the team commits to, and turns results
into specific engineering work rather than a report nobody acts on.
KEY RESPONSIBILITIES
•Build automated load, stress, spike, and soak test scenarios
•Define performance budgets and service level objectives with engineering
•Run performance suites on a schedule and before major releases
•Profile results and identify the bottleneck: application, database, or network
•Correlate test results with production monitoring and tracing data
•Build realistic traffic models from production usage patterns
•Report findings with reproducible evidence and a recommended fix
•Track performance regressions release over release
REQUIRED QUALIFICATIONS
•[3-6]+ years in performance engineering or performance testing
•Experience with [k6 / JMeter / Gatling / Locust]
•Ability to read application code and profile a running system
•Working knowledge of database query performance and caching
•Experience with observability tooling: metrics, logs, and traces
•Ability to explain a bottleneck to people who did not run the test
PREFERRED
•Cloud infrastructure and autoscaling experience
•Capacity planning or cost-per-request analysis
•Chaos or resilience testing experience
CLASSIFICATION NOTE
Exempt computer employee when the duties and pay tests are met ($684 per week
salaried or $27.63 per hour). If you engage this role as a short-term contractor
for a single load-testing engagement, apply the economic reality test honestly:
setting the schedule, the tools, and the method points toward employment. This is
general information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_____ to $_____ per year, [benefits summary]
To apply, email __ with your resume and a performance
problem you found and helped fix.
Template 6: QA Automation Lead / Test Architect
For organizations with several teams and no shared standard: tooling decisions, release gates, mentoring, and the quality numbers leadership reads. For a people-management role with broader quality scope, use the QA manager templates instead.
QA Automation Lead / Test Architect Job Description
QA AUTOMATION LEAD / TEST ARCHITECT JOB DESCRIPTION
Company: __ ([City, State])
Reports to: [VP Engineering / CTO]
Direct reports: [number, or none if this is a technical leadership role]
Employment type: Full-time
FLSA status: Exempt (computer employee, or executive if managing people)
Compensation: $_____ to $_____ per year
ABOUT THIS ROLE
[Company Name] has [number] engineers and [an inherited test suite / no test
strategy / several disconnected suites]. We are hiring a QA Automation Lead to
set the strategy, rebuild what needs rebuilding, and raise the testing standard
across the whole engineering organization.
POSITION SUMMARY
The QA Automation Lead owns the test strategy end to end: which layers get
automated, which tools the company standardizes on, what gates a release, and how
quality is measured. The role combines architecture decisions with hands-on
implementation and mentoring.
KEY RESPONSIBILITIES
•Own the automation strategy and the test pyramid across all teams
•Choose and standardize frameworks, tools, and conventions
•Define release gates and the quality metrics leadership sees
•Mentor engineers on writing tests that stay maintainable
•Build the roadmap for coverage, run time, and reliability targets
•Run root cause reviews for escaped defects and close the gaps
•Report quality and release risk to engineering leadership
•[Hire, manage, and develop the QA team, if this role carries reports]
REQUIRED QUALIFICATIONS
•[5-8]+ years in test automation, including framework design
•Experience setting test strategy across multiple teams or products
•Strong programming background and current hands-on ability
•Track record of measurable improvement in coverage, run time, or escape rate
•Ability to argue for quality investment in business terms
PREFERRED
•Experience in a regulated or high-consequence domain
•People management experience
•Experience introducing automation where none existed
CLASSIFICATION NOTE
This role is exempt. If the primary duty is technical, the computer employee
exemption applies at $684 per week salaried or $27.63 per hour. If the primary
duty becomes managing two or more full-time employees with real authority over
hiring and firing, the executive exemption applies instead and carries the $684
weekly salary requirement with no hourly alternative. This is general
information, not legal advice.
EEO STATEMENT
[Company Name] is an equal opportunity employer and provides reasonable
accommodations for the essential functions of this role.
COMPENSATION AND HOW TO APPLY
Compensation: $_____ to $_____ per year, [equity], [benefits]
To apply, email __ with your resume and a short note on a
test strategy you owned and what it changed.
Overtime and the Computer Employee Exemption
A QA automation engineer is usually exempt from overtime under the computer employee exemption, but that exemption has two halves and both must be satisfied. The primary duty must be qualifying technical work, and the pay must clear a specific floor.
A QA automation engineer is usually exempt, but the exemption is not automatic and it is not granted by the job title. The Department of Labor requires a qualifying primary duty (the application of systems analysis techniques, or the design, development, documentation, analysis, creation, testing, or modification of computer systems or programs) and a pay floor of at least $684 per week on a salary basis, or at least $27.63 per hour. Both halves must be satisfied. The hourly alternative is unusual in the exemption rules and it exists precisely because contract technical work is common in this field. What it does not do is cover someone whose day is running scripted test cases by hand at an hourly rate below that figure. This is general information, not legal advice.
A tester who does not write code may be non-exempt
The most common misclassification in QA is treating everyone on the quality team as exempt because one of them writes automation. The exemption turns on the individual's primary duty. Someone who executes test plans written by others, follows scripted steps, files tickets, and does not design or modify programs sits outside the computer employee exemption and may be outside the professional exemption too, which would make them hourly and owed overtime past forty hours in a week. That matters in QA specifically because release crunches produce long weeks. If you are running a mixed team, classify each person on what they actually do, track hours for anyone non-exempt, and revisit the call when a role changes. This is general information, not legal advice.
Contractors and staffing arrangements need a real test
Short-term automation work is often staffed through contractors, and QA is one of the areas where that gets stretched past what the law supports. Setting the schedule, supplying the tools and repository access, directing the method, and integrating someone into the team's standups and sprint commitments all point toward employment rather than an independent business. Misclassification exposure here is not theoretical: it includes back overtime, payroll taxes, and penalties. If the engagement is genuinely project-scoped with a deliverable and an independent contractor running their own business, document it that way. If you are effectively hiring an employee for six months, hire an employee for six months. This is general information, not legal advice.
Pay transparency changes what the posting must say
A growing number of states and cities require employers to publish a good-faith salary range in the job posting itself, and several extend the requirement to remote roles that could be performed in the covered jurisdiction. That last part catches small companies off guard, because a remote automation role posted from a state with no requirement can still fall under another state's rule based on where the work could be done. Automation roles are almost always posted remote or hybrid, so this is a live question for nearly every posting on this page. Check the rules for every state you are willing to hire in, publish a range you would actually honor, and keep the reasoning on file. This is general information, not legal advice.
Anyone who falls outside the exemption needs hours tracked and overtime paid past forty in a week, which is a live issue in QA because release weeks run long. If you are unsure which side a specific role sits on, our breakdown of exempt versus non-exempt classification works through the tests in order.
Naming the Stack Without Shrinking the Pool
Name your stack, then split it into what is required and what is teachable. Requiring every tool you use is the most common way a small team turns a healthy candidate pool into an empty one, because it filters on the fastest thing to learn.
Programming language is genuinely slow to switch and belongs in the required list. Pipeline experience transfers less easily than people expect, so general CI/CD familiarity belongs there too. Specific browser automation frameworks belong in preferred, since an engineer who has built maintainable suites in one will be productive in another within weeks.
Requirement
Required or preferred
Why
Programming language
Required
The slowest thing to switch and the thing you will review them on
Test framework
Preferred
Transfers quickly between modern tools; a poor filter for ability
CI/CD experience
Required
Pipeline thinking transfers less easily than framework syntax
Version control and code review
Required
This is a coding role and the work goes through review
Domain knowledge
Preferred
Learnable in weeks; rarely worth losing a strong engineer over
Framework design experience
Depends
Required if you have no framework; optional if one exists
Manual and exploratory testing
Preferred
Judgment about what not to automate is the scarcer skill
Certification
Preferred
Rarely predictive on its own; never use it as a hard gate
One more thing worth stating explicitly: how much of the week is coding. Some automation roles are ninety percent test code, others are half manual testing with automation added where it fits. Both are real jobs, and candidates sort themselves correctly when you say which one this is.
What to Pay a QA Automation Engineer
There is no federal occupation code specifically for QA automation engineers, so no published median describes this role exactly. The closest classification is software quality assurance analysts and testers, which blends manual and automated testing and therefore understates automation-specific pay.
The Closest Federal Benchmark, and Its Limits
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), software quality assurance analysts and testers had a national median annual wage of $104,300 ($50.14 per hour), with the tenth percentile at $61,440 and the ninetieth at $167,010. Software developers, the other useful anchor because strong automation engineers can take development roles, had a median of $135,980 (U.S. Bureau of Labor Statistics, OEWS national estimates).
Benchmark
National median (BLS OEWS, May 2025)
How to use it for an automation role
Software QA analysts and testers
$104,300 per year
Closest classification; blends manual and automation, so treat as a floor
Same occupation, 25th percentile
$80,310 per year
Roughly where a junior automation hire lands in a low-cost market
Same occupation, 75th percentile
$133,180 per year
Realistic band for an experienced automation engineer or SDET
Same occupation, 90th percentile
$167,010 per year
Automation leads and test architects in high-cost markets
Software developers
$135,980 per year
What your candidate can earn by taking a development job instead
Two adjustments matter. An SDET should be benchmarked against your software engineering bands rather than the QA occupation, because that is the market you are competing in. And where pay transparency laws apply, publish a good-faith range, remembering that several states extend the requirement to remote roles that could be performed there. Employment across software developers, QA analysts, and testers is projected to grow 15 percent from 2024 to 2034, so the competition for these candidates is not easing.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
Screen with a small work sample read like a pull request, because interviews reward people who talk fluently about testing rather than people who write maintainable tests. Ask candidates to automate two or three scenarios against a public site or a sandbox of your product, timeboxed to about ninety minutes.
What matters in the result is not whether the tests pass. It is the structure: how selectors are chosen, whether waiting is handled properly or with fixed sleeps, whether the test would survive a small UI change, and whether a failure message would tell you anything useful at two in the morning. Our QA engineer interview questions cover the conversation side.
The Two Questions That Sort Candidates Fastest
Ask about a flaky test they fixed and what the root cause turned out to be. Anyone who has maintained a real suite has a specific, slightly weary answer involving timing, test data, or shared state. Then ask about something they decided not to automate and why. Engineers who have only written tests to hit a coverage target have no answer to the second question, because they have never had to defend the maintenance cost of a suite against the value it delivers.
Keep the process short. These candidates are often holding a competing offer for a straight development role, and a four-week interview loop with three panels is how small companies lose them. Two conversations and one work sample is enough to make a confident decision.
Hiring Automation Engineers Without an HR Department
Small team hiring for this role fails in three predictable places: the posting is copied from a company that does not resemble yours, the compensation conversation arrives too late, and the onboarding paperwork is improvised after the offer is signed. Each has a fix.
You are the CTO, the hiring manager, and the HR department at the same time
At a company small enough that the founder still reviews pull requests, the person writing the automation job description is the same person who will interview for it, negotiate it, and then figure out the paperwork. The usual result is a posting copied from a large-company careers page, which asks for eight years of experience with a framework the company does not use and says nothing about the actual work. Strong automation engineers read that and correctly conclude nobody has thought about the role. The fix is a fixed structure you reuse: describe the product, state the release cadence, say honestly whether the framework exists or needs building, list the stack you really run, and give a range. The specifics are the only part worth rewriting each time.
You are competing for engineers who can also take a straight development job
Anyone who can write maintainable test automation can write application code, and the market prices that accordingly. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), software developers had a median annual wage of $135,980 against $104,300 for software quality assurance analysts and testers, so the candidate you want is often weighing your automation role against a developer offer worth more. You will not always win on salary. Compete on the things a small team genuinely has: ownership of the whole test strategy instead of one corner of it, tooling decisions the candidate gets to make, visible impact on release confidence, and a hiring process that takes a week rather than six. Say those things in the posting.
The offer is signed and then the onboarding paperwork starts from nothing
Engineering onboarding at a small company tends to be strong on the technical side and improvised everywhere else. The repository access and the laptop get sorted on day one, while the offer letter, the confidentiality and IP assignment agreement, the handbook acknowledgment, the equity paperwork, the emergency contacts, and the security policy sign-off scatter across email threads and a shared drive. FirstHR was built for that gap. The onboarding wizard runs the same sequence for every engineering hire, built-in e-signature handles the offer letter and the IP agreement, document management keeps signed policies against each employee profile, and training modules cover security and code-of-conduct orientation before the first sprint. Applicant tracking is coming soon to FirstHR. Note that FirstHR is an onboarding and HR platform, not a payroll provider.
Once the offer is accepted, the work becomes a repeatable onboarding checklist: signed offer letter, confidentiality and IP assignment agreement, handbook and security policy acknowledgments, equipment and access, and a first-week plan that gets the new engineer to a merged pull request quickly.
Key Takeaways
A QA automation engineer is a coding hire: the output is test code and pipeline tooling, not manual test execution, and posting it as a testing role attracts the wrong candidates.
State whether the test framework already exists or needs building, because extending a working suite and designing one from nothing are different jobs at different experience levels.
Most automation roles are exempt computer employees, which requires both a qualifying primary duty and pay of at least $684 per week salaried or $27.63 per hour; both halves must be met.
Require the programming language and CI/CD experience, but list specific test frameworks as preferred, because framework syntax transfers quickly and filtering on it empties your pipeline.
No federal occupation code matches this title exactly; the closest is software QA analysts and testers at a $104,300 median (BLS OEWS, May 2025), against $135,980 for software developers.
Screen with a ninety-minute work sample read like a pull request, and keep the process to two conversations, because these candidates hold competing development offers.
Engineering onboarding tends to be strong on repository access and weak on everything else. FirstHR runs the same sequence for every hire, with e-signature for the offer letter and IP agreement, document storage for signed policies, and training modules for security orientation before the first sprint. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What does a QA automation engineer do?
A QA automation engineer writes and maintains the code that tests your product automatically, then keeps that code running inside your build pipeline. The day splits roughly three ways: writing new automated tests for features being built, maintaining and repairing existing suites as the product changes underneath them, and triaging failures to separate real defects from unstable tests. The best ones also do a fourth thing that rarely appears in job postings: they decide what should not be automated, because a suite that tries to cover everything becomes slow and untrusted, and an untrusted suite gets ignored. The role is a coding role. If the person you have in mind will mostly click through the product by hand, you want a manual QA tester instead, which is a different skill set at a different pay band.
What is the difference between a QA automation engineer and an SDET?
The difference is what they build. A QA automation engineer writes tests using a framework, expands coverage, and keeps suites healthy. An SDET, or software development engineer in test, builds the framework itself along with the harnesses, test data systems, and pipeline tooling that other engineers then use. The distinction matters commercially because an SDET is screened and paid as a software engineer, and the candidate pool is smaller and more expensive. A useful rule for a small team: if your framework already exists and works, hire an automation engineer. If you have no framework, an inherited suite nobody trusts, or several teams duplicating effort, an SDET pays for itself. Many companies use the two titles interchangeably, so define the scope in the posting rather than assuming the title communicates it.
Is a QA automation engineer exempt from overtime?
Usually yes, under the FLSA computer employee exemption, but the exemption has two halves and both must be met. The primary duty must involve systems analysis, or the design, development, documentation, analysis, creation, testing, or modification of computer systems or programs. The pay must be at least $684 per week on a salary basis, or at least $27.63 per hour, which is an unusual hourly alternative that exists because contract technical work is common in this field. A title alone never establishes the exemption. The practical risk in QA is applying it to the whole quality team when only some members write code: someone who executes scripted test cases written by others and does not design or modify programs is likely non-exempt and owed overtime past forty hours in a week, which matters during release crunches. This is general information, not legal advice.
How much does a QA automation engineer make?
There is no federal occupation code specifically for QA automation engineers, so the closest benchmark is software quality assurance analysts and testers. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), that occupation had a national median annual wage of $104,300, with the tenth percentile at $61,440 and the ninetieth at $167,010. Treat the median as a floor rather than a target for an automation-specific role, because the occupation blends manual and automated testing and automation skews toward the upper half of the range. The other useful anchor is software developers, whose median was $135,980 in the same survey, because a strong automation engineer can generally take a development job instead. Benchmark against your local market and your engineering salary bands rather than the national figure.
Should the job description name specific tools like Playwright or Selenium?
Name your stack, then separate what is required from what is teachable. Candidates need to know what they will work with, and a posting that lists no tools at all reads as if nobody has decided. The mistake is treating every tool as a hard requirement, which filters out strong engineers over a framework they could learn in two weeks. A practical split: require the programming language, because that is genuinely slow to switch, and require general CI/CD familiarity, because pipeline thinking transfers less easily than it looks. Then list the specific test framework as preferred rather than required. Someone who has built maintainable suites in one modern browser automation framework will be productive in another quickly. Being explicit about which is which also signals that you understand the work, which strong candidates notice.
When should a small company hire its first QA automation engineer?
Hire when manual regression testing has become the bottleneck in your release cycle, not before. The honest signals are specific: releases slip because nobody has finished testing, the same class of bug keeps reaching production, engineers avoid refactoring because they cannot tell what they will break, or the team has quietly stopped releasing on Fridays. Before that point, developer-written tests and a short manual checklist usually cover the risk more cheaply. Hiring automation too early produces a suite covering a product that changes weekly, which is expensive to maintain and gets abandoned. One caution about sequencing: if you have no automated tests at all, your first hire needs framework-building ability, so scope the role toward the SDET end even if you call it an automation engineer.
How do I hire a QA automation engineer without an HR department?
Run a short, fixed sequence and give the technical screen real weight. Post a specific description with the stack, the release cadence, and a salary range stated up front. Screen with a small, realistic work sample: ask candidates to automate two or three scenarios against a public site or a sandbox of your product, timeboxed to about ninety minutes and paid if it runs longer. Read the result the way you would read a pull request, looking at structure, waiting strategy, and how the test would age, rather than whether it passes. Follow with a conversation about a flaky test they fixed and a decision not to automate something. Then move fast, because these candidates hold competing developer offers. FirstHR handles the onboarding sequence afterward with e-signature, document management, and policy tracking. Applicant tracking is coming soon to FirstHR.
