Technology · Mid-career
Automation Tester Resume Example
This example is for a tester who spends most of the week writing and maintaining test code. Set at a manufacturing software company, it shows how to present a framework you designed, how the suite runs in CI and how reliable it is, which are the questions an automation resume has to answer.
The example resume
Laid out in the Brief template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.
Diego Salazar
Automation Tester
- diego.salazar@example.com
- +1 555 0146
- Monterrey, Mexico
- github.example.com/diego-salazar
Professional summary
Automation tester with seven years of experience building and maintaining UI and API test suites for manufacturing software. Designed a Playwright and TypeScript framework that runs 1,400 tests on every pull request in under 15 minutes. Aims for stable, readable tests that developers trust enough to fix themselves.
Work experience
Automation Tester
Cerro Alto Manufacturing Systems, Monterrey
Feb 2022 – Present
- Designed a test framework in Playwright and TypeScript with page objects, fixtures and API-based test data setup for a production scheduling web application
- Grew the suite from 150 to 1,400 automated tests, run on every pull request in GitHub Actions and sharded across 8 runners to finish in 14 minutes
- Reduced flaky failures from 9% of runs to under 1% by replacing fixed waits with web-first assertions and isolating test data per worker
- Built 320 API tests with contract checks against the OpenAPI specification, catching 17 breaking changes before they reached the shop-floor tablet app
- Published Allure reports with traces to each pull request and trained 6 developers to write Playwright tests; developers now add about half of new tests
Test Engineer
Norte Planta Software, Monterrey
Jul 2019 – Jan 2022
- Automated 400 regression cases for an inventory and work-order system with Selenium WebDriver, Java, TestNG and Cucumber, run across 3 browsers on Selenium Grid in Docker
- Cut the manual regression cycle from 4 days to 1 by moving stable scenarios into a nightly Jenkins job
- Wrote REST Assured tests for the label printing and barcode scanning services, covering 45 endpoints
- Tested barcode scanner and label printer integrations by hand on a test bench before automating the scenarios that had settled
Skills
Automation: Playwright, Selenium WebDriver, Appium, Cucumber, REST Assured, Postman
Languages: TypeScript, Java, SQL, Bash
Framework design: page object model, fixtures, test data builders, parallel execution, contract testing
CI and reporting: GitHub Actions, Jenkins, Docker, Selenium Grid, Allure
Performance: k6 load scripts
Projects
playwright-data-fixtures
Open-source library
2024 – Present
- Published a small TypeScript library for creating and cleaning up test data through APIs, with documentation and its own CI pipeline
Education
BEng Computer Systems Engineering
Instituto Tecnológico Sierra Clara, Monterrey
2015 – 2019
Open this example in the resume builder Start empty with this template
Why this resume works
- The summary gives the suite's size and speed (1,400 tests in under 15 minutes on every pull request), the two numbers that tell a reader whether an automated suite is actually useful.
- Flakiness is addressed directly, with the rate before and after and the two techniques that fixed it, because unstable tests are a common reason a team stops trusting its automation.
- Framework design choices are named (page objects, fixtures, API-based data setup, sharding), showing that Diego builds test code as software and does not just record scripts.
- The move from Selenium with Java to Playwright with TypeScript shows adaptability across two toolsets that appear frequently in adverts.
- The Allure reports and the training of six developers show the suite being used by the whole team, and the open-source library gives a reader real test code to look at.
What employers look for in this role
- Design, build and maintain automated test frameworks for UI and API testing
- Decide which tests to automate and at which level
- Integrate test suites into CI pipelines and keep them fast
- Investigate failures and fix or quarantine flaky tests
- Manage test data and test environments
- Report results in a form developers can act on
- Coach developers and manual testers in writing automated tests
Skills to consider
List only the skills you can back up with an example. These are the ones that come up most for this kind of role.
- Tools and languages
- Playwright, Cypress or Selenium WebDriver, Appium for mobile, REST Assured, Postman or Karate, TypeScript, Java, Python or C#, Cucumber or another BDD tool, SQL
- Framework design
- Page object or screenplay pattern, Fixtures and test data management, Parallel and cross-browser execution, Contract testing, Mocking and service virtualisation, Visual regression testing
- CI and maintenance
- GitHub Actions, Jenkins or GitLab CI, Docker, Test reporting (Allure, HTML reports), Flaky test analysis, Git and code review, Performance scripting with k6 or JMeter
More bullet points to adapt
Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.
- Moved 60% of UI checks down to API level, cutting total suite time from 50 minutes to 18 while keeping the same coverage of business rules
- Added a nightly cross-browser run on WebKit and Firefox that found 11 layout and date-handling defects missed on Chrome
- Wrote a quarantine process that tags a flaky test, opens a ticket and removes it from the merge gate until it is fixed
- Built a tagging scheme so each pull request runs only the tests for the modules it changes, with the full suite nightly
- Automated accessibility checks with axe on 40 key pages as part of the pull request pipeline
- Migrated 500 Selenium tests to Playwright over 5 months, deleting 120 that duplicated unit or API coverage
Words that recur in adverts
These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.
Which sections to include
An automation tester is hired to write code, so the resume should read closer to a developer's than a manual tester's. Put tools and language in the summary, then use the experience section to show the framework you built, how it runs in CI and how reliable it is. In skills, list automation tools, programming languages, framework design and CI separately. A projects section or a link to a code profile is valuable here, because a reader can look at real test code. Education follows; testing certifications are optional and carry less weight than a suite you can describe in detail.
Mistakes to avoid
- Quoting "automated 500 test cases" or "90% automation coverage" alone, with nothing about how long the suite takes, how often it runs or how often it fails for the wrong reasons.
- Naming Selenium or Playwright without the programming language and design pattern used with it, which hides whether you wrote the framework or only added cases to someone else's.
- Leaving CI out, although a suite that runs only on a tester's laptop gives a team very little; say where the tests run and what they gate.
- Claiming time saved on regression without the maintenance cost; a credible bullet mentions keeping the suite stable as well as building it.
- Listing every tool in the ecosystem (Selenium, Cypress, Playwright, Appium, Katalon, UFT) when you have real depth in one or two.
Questions and answers
How is an automation tester resume different from a QA engineer resume?
The emphasis moves from test strategy and manual investigation to code: framework architecture, languages, CI integration and suite reliability. Both roles need testing judgement, but here the reader expects to see what you built. For the strategy-led version, compare the QA engineer example.
I only have Selenium experience. Should I still apply for Playwright or Cypress roles?
Usually yes. The underlying skills (locators, waiting strategies, test data, design patterns, CI) transfer, and many employers know this. State your Selenium depth honestly, and if you have tried the newer tool on a small project, add it as a project and say what you built.
Should I include manual testing experience?
Yes, briefly. It shows you understand what is worth automating and what is better explored by hand. Keep it to a bullet or an earlier role, so the balance of the document still says automation.
What numbers matter most for automation work?
Suite size, run time, how often it runs, the failure rate from flakiness and defects caught before release. Regression time saved is useful when paired with one of these. Percentage coverage figures need a definition (of requirements, of regression cases, of code) or they mean little.