Resume template · Updated October 2026
Test automation engineer resume template
Short answer
FAANGPath is the pick for a test automation engineer: the job is writing code, and FAANGPath prints the languages and frameworks in labelled rows above the jobs. The fictional sample is an SDET in Pune with seven years of automation, now on a retail commerce platform, with a Playwright and TypeScript framework running 1,100 tests per pull request, flaky runs cut below one percent, contract tests and a small open-source reporter.
Download the test automation engineer sample
Rohan is a fictional test automation engineer (SDET). Replace every detail with your own before you send it.
The files are made in your browser by Resumity's own exporters, from this sample. The builder opens it as your own resume: click any line to replace it. Free plan, no watermark.
Why FAANGPath suits a test automation engineer resume
FAANGPath places a labelled skills block above the jobs, and the dot after each label keeps rows such as "Technical · TypeScript, Java" tidy. Automation engineers are screened as developers first, on language and framework, and FAANGPath's minimal centred page was built for technical candidates like that; it also prints projects before education for a tool you have published.
Second choice: Meridian. Meridian is the editor default with an identical section order; its heading rules run to the right of each title and its skill labels end in a colon, a difference of style only.
What goes in each section, in FAANGPath's order
FAANGPath prints its sections in a fixed order, the same in the PDF and the Word file. Here is that order for this sample, and what to put in each section.
- Professional Summary. Say what you automate (web, API, mobile, performance), in which language, and how the tests run: in CI, on every pull request, in parallel. Include "SDET" if the posting uses it.
- Skills. Programming languages first, then frameworks, then CI and infrastructure. A row that reads like a tool catalogue with no language in it weakens an automation resume, because the reader cannot tell whether you write the framework or only the scripts.
- Work Experience. Measure the suite as an engineering system: how many tests, how long a run takes, how often tests flake, what they caught. One bullet on the people side (developers writing their own tests, reviews of test code) shows you raise the team's testing, not just your own.
- Projects. A small open-source tool, a reporter or a test data library lets anyone read your code. Describe the problem it solves in one line and who uses it.
- Education. One line at the end. An engineering degree is common, but the framework work above it carries the page.
The sample resume as text
The same content as the files above, so you can copy a line or compare it with your own.
Rohan Deshpande
Test Automation Engineer (SDET), Playwright and TypeScript
Pune, India | rohan.deshpande@example.com | +91 20 555 0153 | github.com/sample-rohan-deshpande | linkedin.com/in/sample-rohan-deshpande
Test automation engineer with seven years building frameworks for web, API and mobile testing, the last four as the SDET on a retail commerce platform. Writes test code to the same standard as product code, runs suites in parallel in CI, and treats a flaky test as a bug to fix rather than a failure to retry.
Experience
Senior Test Automation Engineer (SDET), Sahyadri Commerce Labs, Pune, India (06/2022 to Present)
- Designed a Playwright and TypeScript framework with page objects, API fixtures and test data factories; 1,100 end-to-end tests now run on every pull request in 14 minutes across 8 parallel workers.
- Cut flaky runs from about 6% to under 1% by quarantining unstable tests, tagging owners and fixing waits and shared test data.
- Added Pact contract tests between the checkout service and four consumers, catching breaking API changes before merge.
- Built a k6 load test for the sale-day checkout path and ran it with the platform team before each major sale.
- Coach developers on writing their own tests; they now write about half of new end-to-end tests.
Automation Test Engineer, Bluepeak Fintech Solutions, Pune, India (07/2019 to 05/2022)
- Built Selenium WebDriver tests in Java and TestNG for a loan origination web app, replacing a three-day manual regression cycle.
- Wrote REST Assured API tests that ran nightly in Jenkins with Allure reports.
- Automated Android smoke tests with Appium on a small in-house device farm.
Projects
flake-ledger (open source): A Playwright reporter that records retries per test across CI runs and flags tests that pass only on retry.
- Used by the commerce team and three other teams at the company to decide which tests to fix first.
Education
Bachelor of Engineering, Computer Engineering, Indrayani College of Engineering (06/2019)
Skills
TypeScript, Java, Test framework design, API and contract testing, Parallel test execution, Performance testing, Playwright, Selenium WebDriver, REST Assured, Pact, Appium, k6, GitHub Actions, Jenkins, Docker, Coaching developers on testing, Test strategy reviews
How to make the sample yours
Swap the stack for yours
Selenium with Java, Cypress, WebdriverIO, Appium or Robot Framework: change the headline, the first skills row and the framework bullet together.
Give suite size, run time and flake rate
1,100 tests in 14 minutes on 8 workers, flaky runs below 1%. Your CI history holds these numbers; quote them as they are.
Show tests that block a bad merge
Tests that run before merge, contract tests between services, required checks. A suite nobody waits for does not prevent anything.
Separate retries from real fixes
The sample quarantines flaky tests, assigns owners and fixes waits and shared data. If your suite simply retries failures, do not describe that as stability work.
Link only code you may share
An open-source reporter or a demo framework on GitHub is good; code copied from an employer repository is not.
Keywords to keep where they are true
Terms this kind of resume is usually searched for. Use the posting's exact wording, and only for work you have done.
- test automation
- SDET
- Playwright
- Selenium WebDriver
- TypeScript
- Java
- API testing
- REST Assured
- contract testing
- Pact
- CI/CD
- parallel test execution
- flaky test reduction
- performance testing
- page object model
Mistakes to avoid
- Counting tests without saying what they cover or how long they take.
- Record-and-playback tools as your main skill when the role is code-first.
- Retries presented as a cure for flaky tests.
- Promising to automate everything. Reviewers expect you to know which tests are worth automating and which are not.
How the sample PDF reads in text extractors
We exported this sample with Resumity's PDF exporter in Chrome on 2026-10-29 and read the file back with three open-source text extractors. This shows whether software that turns a PDF into text can recover it; it is not a test of any commercial applicant tracking system. How we test templates.
| Extractor | Name, email, phone | Headings | Bullets intact |
|---|---|---|---|
| pdf.js 4.10.38 | All found | 5 of 5 | 9 of 9 |
| pdftotext (Xpdf) 4.00 | All found | 5 of 5 | 9 of 9 |
| pypdf 6.13.0 | All found | 5 of 5 | 9 of 9 |
Frequently asked questions
Is an SDET the same as a test automation engineer?
Often, yes; companies use the titles for similar work. SDET postings tend to expect more software design (frameworks, tooling, code review), so if you do that, use both terms, as in "Test Automation Engineer (SDET)".
Should I list both Selenium and Playwright?
List both if you have built real suites in each, with the one you use now first. Interviewers will ask why you chose one over the other, so have an answer from your own projects.
How do I show the impact of test automation?
Before and after: manual regression days removed, minutes per CI run, flaky rate, defects caught before merge. Tie at least one number to something the business noticed, such as a sale day that went smoothly.
Do I need a GitHub profile as a test automation engineer?
It helps, because your work is code. A small tool or a clean demo framework with a README is enough; leave out forks you never changed.
How much manual testing should an automation resume mention?
A line, if it shaped what you chose to automate. The page should make clear that most of your time goes into writing and maintaining test code.
Will applicant tracking systems read this FAANGPath PDF?
The sample PDF read back with its contact details, all 5 section headings and all 9 bullets intact in three open-source text extractors (pdf.js, pdftotext and pypdf). Commercial systems such as Workday, Greenhouse or Taleo were not tested, and each employer configures its own.
Guides and templates for this resume
More in resume templates by job title.