QA Automation Engineer résumé example, in the Beacon design
A lab technician turned test engineer, written around what the automation caught rather than how many tests exist.
Written for United States, at entry level, in the software field, shown in the Beacon design. Every name, employer, address and number below is invented.
Test engineer who moved from a hospital diagnostics bench into software testing in 2023. Built the Playwright suite that now gates every release of a scheduling product used by 1,200 clinics, taking escaped defects from 19 a quarter to 4.
Experience
QA Automation Engineer, Verdal Health Systems · September 2024 – present
Release quality for a scheduling product used by 1,200 clinics.
Built the Playwright suite that gates release, covering 118 flows and finishing in 9 minutes on four shards; escaped defects fell from 19 a quarter to 4.
Replaced a six-hour manual regression pass with an automated smoke run, freeing two testers for exploratory work on the booking rewrite.
Wrote the quarantine rule that pulls a test after two non-deterministic failures, taking suite reliability from 86% to 99.2%.
Added contract tests between the scheduler and the billing API, catching a field rename that would have dropped 3,000 appointments.
QA Analyst, Foxhill Software · March 2023 – August 2024
Wrote the first automated API checks for a claims tool, moving 240 manual cases into a nightly run that reported before standup.
Rebuilt the bug template around reproduction steps and environment detail; developer requests for clarification dropped by two-thirds.
Tested the record-import path against 14 malformed real-world files and found three crashes that had already reached production twice.
Clinical Laboratory Technician, Rowan Diagnostics · June 2019 – February 2023
Ran 60 specimen assays a shift under CLIA protocol, holding a documented error rate below 0.3% across four years.
Automated the daily quality-control log in Python, replacing a paper checklist and cutting shift close-out from 45 minutes to 5.
Education
B.S. Biology · University of North Carolina at Chapel Hill · August 2015 – May 2019
Practice: Test strategy, CI gating, Exploratory testing, Accessibility checks, Defect triage
Certifications
Certified Tester Foundation Level — ISTQB
GitHub Actions Certification — GitHub
Why this QA Automation Engineer résumé works
The Playwright suite is described by what it caught, not how big it is: escaped defects “from 19 a quarter to 4”, with 118 flows finishing in 9 minutes, the measure a QA lead actually reports upward.
Flaky tests are dealt with head-on: the quarantine rule took suite reliability from 86% to 99.2%, a detail that shows the judgement automation engineers are hired for beyond writing scripts.
The Rowan Diagnostics years are cut to two bullets that already look like QA work, CLIA protocol with an error rate below 0.3% and a Python script replacing a paper checklist, so the career change reads as continuity.
The contract test that caught a field rename which would have dropped 3,000 appointments turns an abstract skill into a single, concrete save a hiring manager remembers.
QA Automation Engineer résumé: common questions
How do you write a QA resume when changing careers?
Keep the earlier job but shorten it to the bullets that show testing habits: following protocol, documenting errors, automating a manual check. Put the QA roles first and lead the summary with what your automation has shipped or caught since the switch.
Is ISTQB certification worth putting on a QA automation resume?
Yes for entry-level roles, since many US job posts list it as preferred. Put the ISTQB Foundation Level in a certifications section with the year; it carries more weight beside a bullet showing a working test suite.
What tools should a QA automation engineer resume list?
Group them: frameworks (Playwright, Cypress, pytest), API and load testing (Postman, k6), languages (TypeScript, Python) and CI. Name the frameworks the job post names, and make sure each appears in at least one bullet with a result.
