Manual tester to automation engineer: pay jump and skills

01The pay jump

We compared the 1,379 manual QA tester postings with the 1,023 QA automation engineer postings in our snapshot. Only postings with an employer-published US dollar annual range have pay: 84 manual, 59 automation.

At mid level, where most postings sit, automation posts $125k against $108k: 16% more. At senior level the gap is $35k (23%). The pay premium is real in this sample, but each row has 17 to 47 ranges.

02Manual is already half automated

The usual picture is a switch: one day a person tests by hand, the next they write code. The postings show a slope from junior to senior.

Of 1,379 manual postings, 577 (42%) name at least one of Selenium, Playwright, Cypress, Appium, Cucumber, Robot Framework, Katalon, REST Assured, WebdriverIO, TestCafe, Espresso or XCUITest. At senior level it is 54%. Employers who file a role under 'manual' often want someone who can read and maintain a suite, or who will move into one.

This is good news for a manual tester planning the move: the first step does not need a change of job. Add a framework to your current work and the next posting you read will fit.

03What changes in the stack

What changes in the tool list when the role changes. Positive points are what you add. Negative points are what you stop being asked for.

You add a framework, a language and CI: Selenium (30% to 61%), Playwright (18% to 57%), Cypress (12% to 42%), Python (14% to 22%). You lose the weight of Jira (54% to 14%) and TestRail (19% to 3%). Keep them on the CV, but they are no longer the headline.

04What to learn first

Take the 664 mid-level automation postings, the level most people move into. Here is how often each tool is named.

1. Start from what you already use. Postman is named by 40% of manual postings and still by 20% of automation ones. Scripting the API checks you run by hand is a small first step.
2. Pick one browser framework. Selenium is named in 61% and Playwright in 57% of automation postings; Cypress in 42%. Employers rarely ask for one only: 50% of automation postings name two or more of the three.
3. Add the language it needs. Python is named in 22% of automation postings in our tool list. Java, C# and TypeScript are not tracked here, so check the posting for the stack you target.
4. Learn to run it in CI. Jenkins (10%), GitHub Actions (4%) and Docker (7%) separate a suite on your laptop from a suite a team trusts.

The order is ours; the percentages are what the postings show. One browser framework plus a language covers most of what is asked at mid level.

05Where the roles are

The mix differs a lot by country: automation is 57% of the two groups in United Kingdom and 16% in Canada. Check your country on the jobs pages before you plan the move around one city.

06Quick answers

Which is better, manual testing or automation?

Automation pays more in our sample and appears in 54% of all QA postings. Manual roles are still the larger group (1,379 against 1,023), and they carry judgement that a script does not. The best-placed tester does both.

Will manual testing be replaced by AI?

Postings cannot answer that. What they do show is that employers file the work under manual and ask for tools: 42% name a framework. That is a signal to add skills, not a prediction.

Who can become an automation engineer?

Anyone who can read a test case and a stack trace and who will write code every week for six months. The QA career roadmap lays out the stages.

07A six-month plan

A plan in four steps. The order is ours; the weights come from the percentages above.

1. Weeks 1 to 4: pick up Postman collections for the product you test today. Write assertions, not just calls.
2. Weeks 5 to 12: take one framework (Playwright or Selenium) and automate the smoke tests you run by hand every release. Keep it in a repository you can show.
3. Weeks 13 to 20: learn the language to read other people's suites, wire the run into CI, and handle flaky tests.
4. Weeks 21 to 26: apply to hybrid roles first: manual postings that name a framework, then mid-level automation roles. Check pay for your market on the pay report.

If you want a recruiter who knows which of these roles pay better in your country, get a personal QA recruiter and say what you already automate.

08Method and limits

Sample: 3,863 public postings harvested 20 Oct 2026 from employer career pages and public job feeds. Listings are postings, not people or confirmed openings: one role open in several cities counts several times (2,417 distinct titles across 3,863 postings). PassRidge talent-pipeline roles (149) are excluded from every statistic.

Manual means the role 'Manual QA Tester', automation means 'QA Automation Engineer' in our role classifier. A framework is any of 12 test frameworks in our tool list, not only web ones.

Tool shares come from the stack field, which only knows about 30 tools. Programming languages other than Python are not tracked.

Pay figures use only ranges the employer published (605 postings). Ranges in other currencies are converted at the indicative rates in our rate table dated 2026-10-01; hourly ranges are annualised at 2,080 hours. Employers that publish a range are not a random sample of employers, and most of them are US companies.

The method for roles, tools and pay is documented on our salary methodology page. Spot an error? Write to [email protected].