Automation Engineer is one of the most ambiguous titles in technology hiring, and the ambiguity creates a specific CV problem: if you don't signal immediately which type of automation you do, your application will be screened against the wrong role. The title covers three genuinely distinct disciplines — test automation (Selenium, Playwright, Cypress), infrastructure automation (Terraform, Ansible, Puppet), and robotic process automation (UiPath, Automation Anywhere, Blue Prism) — each with its own toolchain, hiring market, and performance metrics. A CV that opens with "experienced automation engineer with skills in CI/CD, scripting, and testing" without specifying the domain will be filtered out by recruiters who need one specific type. The second problem is the absence of ROI evidence: automation work is uniquely quantifiable — every automation replaces a manual process, and that process has a time cost that can be calculated. Automation engineers who express their output in hours saved, error rate reductions, and cycle time improvements are positioned as commercially aware rather than purely technical, which changes who reads their CV and at what seniority level.

What Automation Engineer Job Descriptions Require in 2026

Automation engineer JDs split sharply by domain. Identify which track your experience sits in and lead with it:

Test Automation Engineer: Builds and maintains automated testing frameworks. Primary tools: Selenium (mature, Java/Python), Playwright (modern, TypeScript/Python, growing fast), Cypress (JavaScript, frontend-focused), Appium (mobile). Language proficiency in Python, Java, or JavaScript/TypeScript is required — writing tests is programming. CI/CD integration (tests running in GitHub Actions, Jenkins, or GitLab CI on every build) is standard. Framework architecture is the senior differentiator: designing the page object model, test data management, reporting layer, and retry logic — not just writing individual tests.

Infrastructure Automation Engineer / DevOps Automation: Automates infrastructure provisioning, configuration management, and deployment pipelines. Primary tools: Terraform (IaC, dominant), Ansible (configuration management), Pulumi (developer-centric IaC), Helm and ArgoCD (Kubernetes GitOps). Language: Python and Bash for tooling; Go for custom infrastructure tooling. Cloud platform (AWS, Azure, GCP) is the deployment target. GitOps workflows and drift detection are the senior differentiators.

RPA Developer / Automation Engineer: Automates repetitive business processes using enterprise RPA platforms. Primary tools: UiPath (market leader), Automation Anywhere, Blue Prism, or Microsoft Power Automate. Does not require traditional software engineering skills but does require structured process analysis, exception handling design, and UiPath/AA certification. The commercial language for this track is different: ROI, FTE equivalent, processing time, error rate.

Requirements common across all automation engineering tracks:

  • Process analysis before automation — identifying which processes are worth automating (stable, rule-based, high-volume) vs. which are not (highly variable, judgement-intensive). This analytical skill separates productive automation engineers from those who automate the wrong things.
  • Error handling and reliability — automated processes fail in ways manual processes don't. Retry logic, alerting, and graceful failure handling are engineering requirements, not optional extras.
  • Documentation — automated processes that only the person who built them can maintain are a liability. Runbooks, architecture diagrams, and inline code comments are part of the deliverable.
  • Metrics — time saved, error rate before and after, process volume, and reliability rate. Automation work is uniquely measurable and the numbers belong on the CV.

Automation engineer salaries in 2026: £40K–£70K UK (test/RPA); £55K–£90K (infrastructure/DevOps automation). US: $75K–$120K; senior/lead $110K–$160K.

ATS Keywords for an Automation Engineer Resume

Automation engineering ATS filtering is domain-specific. The keyword clusters for test automation, infrastructure automation, and RPA have minimal overlap — use the cluster that matches your track.

Essential ATS terms for an automation engineer resume:

  • Title variants: Automation Engineer, Test Automation Engineer, Infrastructure Automation Engineer, DevOps Automation Engineer, RPA Developer, RPA Automation Analyst, SDET
  • Test automation: Selenium, Playwright, Cypress, Appium, WebDriver, TestNG, pytest, JUnit, BDD, Cucumber, Gherkin, page object model, CI test integration
  • Infrastructure automation: Terraform, Ansible, Pulumi, CloudFormation, Puppet, Chef, GitOps, ArgoCD, Helm, Kubernetes, configuration management, Infrastructure as Code, IaC
  • RPA: UiPath, Automation Anywhere, Blue Prism, Power Automate, RPA, robotic process automation, workflow automation, process mining, bot development
  • CI/CD: GitHub Actions, Jenkins, GitLab CI, CircleCI, pipeline automation, deployment automation
  • Languages: Python, Java, JavaScript, TypeScript, Bash, Go, PowerShell
  • Metrics language: hours saved, FTE equivalent, error rate reduction, cycle time, processing time, automation ROI
  • Long-tail phrases: automation engineer resume examples, how to write an automation engineer resume, test automation engineer cv, RPA developer resume, Terraform automation engineer resume

Placement: Your automation domain and primary tool in the headline — "Automation Engineer | Playwright · TypeScript · GitHub Actions · Python" or "Automation Engineer | Terraform · Ansible · AWS · GitOps" or "RPA Developer | UiPath · Automation Anywhere · Power Automate." Language (Python, TypeScript) visible in Skills alongside the primary tool.

Automation Engineer CV Structure and Bullets That Show ROI

Section order:

  1. Headline — domain + primary tool + language: "Test Automation Engineer | Playwright · Python · GitHub Actions"
  2. Certifications — UiPath Certified Professional (RPA), AWS DevOps Engineer (infra), ISTQB Advanced Test Automation (test); near the top
  3. Skills — Primary Domain Tools / Languages / CI/CD / Cloud / Monitoring
  4. Experience — 4–5 bullets per role; processes automated, scale, hours saved, error rate impact
  5. Education — CS, engineering, or IT degree; bottom

One to two pages. For infrastructure automation, GitHub link to public Terraform modules or Ansible playbooks — actual runnable code proves the skill directly. For RPA, UiPath certification number and Academy completions are useful supporting evidence.

Three elements make an automation engineer bullet convincing: what process was automated (type, volume, complexity), the tool and scale of the automation, and the measured outcome (hours saved, error rate, cycle time). Three examples:

  • Built a Playwright/TypeScript test automation suite of 520 end-to-end tests for a multi-tenant SaaS platform — integrated into GitHub Actions pipeline; reduced regression cycle from 3 days to 45 minutes; defect escape rate to production fell from 8% to 1.2% over the following 6 months
  • Designed a Terraform and GitHub Actions CI/CD pipeline automating provisioning of 40 cloud environments on AWS — environment spin-up time reduced from 4 hours to 8 minutes; eliminated configuration drift errors responsible for 6 production incidents in the prior year
  • Developed 28 UiPath RPA automations for a finance operations team — processes covered invoice matching, vendor reconciliation, and payment approval; eliminated 1,800 annual hours of manual processing and reduced transaction error rate from 3.2% to 0.1%

Automation engineering interviews test design thinking ("how would you automate this process?"), code quality (show me a test/script you've written and walk me through the design decisions), and reliability thinking ("what happens when this automation fails at 2am?"). Your bullet specificity — particularly hours saved and error rates — signals which scale of automation you've operated at.

Three Automation Engineer CV Mistakes That Fail the Domain Filter

No domain signal in headline or first bullet. An automation engineer CV that opens with "experienced in automation testing, scripting, and CI/CD tools" without naming the specific framework is invisible to the recruiters searching for "Playwright automation" or "Terraform engineer." The headline must commit to the domain: test automation or infrastructure automation or RPA. A recruiter hiring a test automation engineer is not looking for someone who "has experience with various automation tools" — they are looking for Playwright or Selenium with Python or TypeScript in GitHub Actions. Be that person in your headline.

Scale and ROI absent from automation bullets. "Automated manual processes to improve efficiency" is the weakest possible automation bullet. It names the activity (automation), implies a direction (improvement), and proves nothing. The reason to automate anything is that the before state is measurable and the after state is better. Always state the before: "what was the manual process, how long did it take, how error-prone was it?" Then state the after: "how long does the automated version take, what is the error rate now, how many hours does it save annually?" These numbers exist — they are available from your team's data or from a simple calculation. If an automation saves 2 hours weekly, that is 100 hours annually or roughly 2.5 FTE weeks. Put it on the CV.

Tool listed, framework architecture not mentioned. "Used Selenium for test automation" and "used Terraform for infrastructure" describe tool familiarity, not engineering depth. The senior signal in automation engineering is framework architecture: designing the structure, the modularity, the reusability, the error handling, and the CI integration — not just running the tool. For test automation, this means: did you design the page object model, the test data management strategy, the reporting layer? For infrastructure automation: did you write reusable Terraform modules with input validation, or did you write monolithic scripts? Naming the architectural decisions you made, even briefly, is what distinguishes an automation engineer from an automation user.

If you are applying to automation engineer or test automation roles and want your CV rebuilt around the specific Playwright, Terraform, or UiPath requirements in a target job description, Resumegpt generates your automation engineer CV from your work history in under 60 seconds — domain signalled, ROI metrics surfaced, ATS-optimised, and exported as a PDF ready to submit.