QA Engineer Resume Example (2026 Guide)
QA Engineer resume example
A complete sample in the Modern template FitMyRole exports. The person and employers are fictional; the structure, skills and bullet style are what to copy.
Brandon Keller
[email protected] • (555) 010-6712 • Atlanta, GA • linkedin.com/in/brandonkeller
Professional Summary
QA Automation Engineer with 8 years in software testing, moving from manual test execution to building the automation frameworks and CI quality gates for an insurance SaaS platform. Owns a Playwright and TypeScript suite of 1,900 UI and API tests that runs on every pull request in under 12 minutes across 4 parallel shards, and is retiring the older Selenium suite. Cut production defect escapes by 58% in two years and replaced a 3-day manual regression with a 40-minute automated run, which let the team move from monthly to weekly releases. Works inside scrum teams with developers and product owners, writing test plans from acceptance criteria and pairing on testability.
Technical Skills
- Test Automation: Playwright, Cypress, Selenium WebDriver, TypeScript, JavaScript, Java, Python, page object model, test data factories
- API & Contract Testing: REST API testing, Postman and Newman, REST Assured, Pact, OpenAPI schema validation, GraphQL testing
- CI/CD & Tooling: GitHub Actions, Jenkins, Docker, test sharding and parallelization, Allure reports, Git
- Test Strategy & Planning: Test plans, risk-based testing, regression testing, smoke testing, exploratory testing, UAT, acceptance criteria review
- Performance & Accessibility: k6, JMeter, axe-core accessibility checks, Lighthouse
- Defect & Test Management: Jira, TestRail, Xray, defect triage, flaky test quarantine, quality metrics (escape rate, pass rate)
- Databases: SQL, SQL Server, PostgreSQL, test data management
Education & Certification
- Coursework focus: Software Engineering, Software Testing and Verification, Database Systems and Web Programming.
Work Experience
Senior QA Automation EngineerJune 2022 – PresentFieldstone Insurance Technology, Atlanta, GA
- Replaced a 3-day manual regression cycle with a 40-minute automated run by building a Playwright and TypeScript framework with page objects, test data factories and 4-way sharding in GitHub Actions.
- Cut production defect escapes by 58% over two years by adding a CI quality gate that blocks merges on failed smoke, API contract or accessibility checks across all 9 product repositories.
- Built 650 API tests for the policy, quoting and billing REST services with Playwright’s request context and Postman collections run in Newman, validating every response against the OpenAPI schema.
- Brought the suite’s flaky-test rate from 7% to under 1% by replacing fixed waits with web-first assertions, isolating test data per run and quarantining unstable tests in a weekly triage.
- Retired 400 of 700 Selenium WebDriver tests in Java by migrating the highest-value journeys to Playwright first, ranked by production defect history and customer usage.
- Write test plans and risk-based test strategies for each quarterly feature set from Jira acceptance criteria, and lead exploratory testing sessions before every major release.
- Added Pact contract tests between the quoting front end and 5 backend services, catching 14 breaking API changes before they reached the staging environment.
- Mentor 3 QA engineers on automation design and code review, and run a monthly testability session with developers on test IDs, seeded data and feature flags.
QA EngineerJanuary 2020 – May 2022Cobblestone Commerce, Atlanta, GA
- Shortened manual regression per release from 5 days to 1 by automating 450 checkout, cart and account tests in Cypress and JavaScript, run nightly in Jenkins.
- Created API test suites in Postman and REST Assured for the order and payment services, covering 120 endpoints with positive, negative and boundary cases.
- Caught a tax calculation defect affecting 3 states while testing a pricing change, preventing an estimated $90K in incorrect charges during the holiday season.
- Ran k6 load tests before Black Friday that showed checkout failing at 1,800 requests per second, giving engineers time to fix connection pooling before peak traffic.
- Logged and triaged 300+ defects a year in Jira with clear reproduction steps, logs and screenshots, working in daily standups and sprint planning with two scrum teams.
QA AnalystJune 2018 – December 2019Southline Medical Billing, Alpharetta, GA
- Executed manual test plans for 14 releases of a web-based medical billing application, covering claim entry, payment posting and reporting.
- Wrote 600 test cases in TestRail from requirements and user stories, organized into smoke, regression and UAT suites the team kept using after automation began.
- Started the team’s first automated smoke suite with Selenium WebDriver and Python, covering 40 critical paths that ran before each deployment.
- Validated claim data with SQL queries against SQL Server, finding 25 data mapping defects in 837 and 835 EDI file processing before release.
- Supported user acceptance testing with 8 billing staff, preparing UAT scripts and logging their findings in Jira.
Want yours to read like this? Upload your resume and a job posting, and FitMyRole rewrites it for that job in this template.
Tailor my resumeWhy This Resume Works
- The automation story has numbers a QA manager trusts: 1,900 tests under 12 minutes on 4 shards, regression cut from 3 days to 40 minutes, and flaky tests brought from 7% to under 1%.
- Quality is measured by outcomes, not test counts alone: defect escapes down 58% and a release cadence that moved from monthly to weekly because of the CI quality gate.
- Playwright, Selenium, Cypress, Postman, Pact and k6 each appear in a bullet that says what they tested, so the resume matches "test automation" and "API testing" keyword screens with evidence.
- Test planning still shows (test plans from Jira acceptance criteria, risk-based strategies, exploratory sessions), which keeps an automation engineer from reading as someone who only writes scripts.
- The path from manual QA analyst to Cypress automation to owning a Playwright framework is visible, and two ISTQB certifications are dated at the start and the senior stage of that path.
Common Resume Mistakes
- Listing only "tested software" without automation or outcome.
- No coverage or quality metrics.
- Missing automation or tool keywords.
Keywords Recruiters Look For
- QA
- Test automation
- Selenium
- Cypress
- API testing
- Regression
- Test plan
- Jira
Get more interviews. Tailor your resume automatically
Want to tailor your resume to the job you want? Use FitMyRole to analyze your resume and rewrite it for the role. Before sending your next application, run your resume through FitMyRole to tailor it to the job description.
Try FitMyRole free