QA Engineer resume example

QA Engineer resume example: a Playwright framework of 900+ tests, regression cut from 3 days to 40 minutes, 60% fewer production bugs, under 1% flaky.

Cover letter for this role

Brandon Lee

QA Engineer (SDET) | Test Automation, Playwright, API Testing and CI

Raleigh, NC5 years of experience

Summary

QA Engineer with 5 years in SaaS and insurance software, moving from manual testing to building automation frameworks. Writes UI and API tests in Playwright, TypeScript and Python, runs them in CI on every pull request and works with developers to prevent bugs rather than just find them.

Experience

QA Engineer (SDET)Feb 2023 - Present

Oakcrest Software

  • Built a Playwright and TypeScript test framework with 900+ automated tests; full regression now runs in 40 minutes instead of 3 days of manual testing.
  • Production bugs reported by customers dropped 60% over 2 years after tests were added to every pull request in GitHub Actions.
  • Wrote 350 API tests in Python and pytest for the billing and permissions services.
  • Brought flaky test rate from 8% to under 1% by fixing waits, test data and environment setup.
  • Coach 3 developer teams on writing testable code and their own unit and integration tests.
QA AnalystJun 2021 - Jan 2023

Wake Insurance Solutions

  • Tested a policy administration system across 2-week sprints, writing and running 1,200+ manual test cases.
  • Logged and tracked 400+ defects in Jira with clear reproduction steps.
  • Automated the 60 highest-priority smoke tests with Selenium and Java, which the team ran before every release.

Skills

  • Test Automation
  • Playwright
  • TypeScript
  • Python (pytest)
  • API Testing (REST, Postman)
  • Selenium WebDriver
  • CI/CD (GitHub Actions)
  • Test Planning and Strategy
  • SQL for Test Data
  • Jira and TestRail
  • Agile and Scrum

Certifications

  • ISTQB Certified Tester Foundation Level (CTFL)

Education

BS in Information Technology, North Carolina State University, 2021

Fictional candidates and employers. Any resemblance to a real person or company is coincidental.

Now for your own experience and a real posting

Jobiko writes a resume and a cover letter from what you have actually done, for the posting you choose, and shows you both before anything is sent.

Build my resume →

What hiring managers check first

Automation you built

Hiring managers want to know whether you built a framework or added to one. Give test counts and run times.

Quality outcomes

Escaped bugs, flaky rate and release speed show that your testing made a difference.

Modern tools

Playwright, Cypress, Selenium and API testing tools are common filters. Name what you use.

Collaboration with developers

Shift-left practices and coaching developers show senior-level thinking.

Keywords the applicant tracking system matches

  • QA Engineer
  • SDET
  • Test Automation
  • Playwright
  • Selenium
  • API Testing
  • Python
  • TypeScript
  • CI/CD
  • Regression Testing
  • Agile
  • Jira
  • ISTQB

Use the ones that are true of you, in the words the posting uses.

Mistakes to avoid

  1. Counting test cases only

    Numbers of test cases do not show quality. Pair them with outcomes like fewer production bugs.

  2. Leaving out manual experience

    Exploratory and manual testing still matter. Include them, especially for complex domains.

  3. Unclear title

    QA Analyst, QA Engineer and SDET mean different things. Use the one that matches your work and the posting.

Questions

Is ISTQB certification useful?
It helps early in your career and with some employers, but automation skills and results matter more for most engineering teams.
How long should a QA engineer resume be?
One page up to about 6 years of experience. List your tools clearly in the skills section.
How do I move from manual testing to automation?
Learn one language and one framework, such as Python with pytest or TypeScript with Playwright, and automate tests at your current job.

More examples

← All resume examples