QA / Test Automation Engineer
You find out what breaks before a user does, and turn that into a test that runs forever.
No degree needed Approachable entry, with genuine depth once you automate.
Can I actually do this?
One of the more open routes into software without a degree, partly because manual QA roles still exist and convert into automation from the inside. Being able to write a failing test that proves a bug is the skill that moves you up.
Who it suits. People who instinctively try the weird input, and who enjoy being the one who found it.
Runway. Months. One of the shorter runways into software, and manual QA is a real door in.
Coming from support? You already spend your day reproducing other people's problems, which is most of this job. Help Desk / IT Support
Also advertised as
The route
Four stations, in order. Each one is a thing you finish before the next matters.
-
Station one
Learn it free
Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.
Playwright — getting started
Free to learn · no certificate
Browser test automation from Microsoft, free and open source. Currently the most-asked-for tool in this space alongside Cypress.
Verified 2026-07-27
MDN — Learn web development
Free to learn · no certificate
You cannot test what you do not understand. Enough HTML, CSS and JavaScript to read the thing you are testing is the floor.
Verified 2026-07-27
GitHub Actions — quickstart
Free to learn · no certificate
A test nobody runs is decoration. This is how you make them run on every change. Free minutes on public repositories; private repos consume a quota.
Verified 2026-07-27
-
Station two
Attest strategically
Nothing here is worth buying. This field has certification schemes, but hiring runs on whether you can write a test that catches a real bug — which is demonstrable in an interview and in a repository. Save the money.
Nothing here is worth paying for
No credential needed
Nothing here is worth buying. This field has certification schemes, but hiring runs on whether you can write a test that catches a real bug — which is demonstrable in an interview and in a repository. Save the money.
Checked 2026-07-27
-
Station three
Prove it
A certificate says you passed a test. These say you can do the job.
A failing test that proves a real bug
Find a bug in an open-source project, write the test that demonstrates it, and submit it. This single artifact is the most convincing thing in this field.
A suite that runs on every push
Wire your tests into CI so they gate a merge, and show one being blocked.
A flaky test you fixed
Document a test that passed and failed at random and what you did about it. Everyone has them; few can explain them.
-
Station four
Get hired
Search these exact titles
Who hires for this. Product companies, agencies, and any regulated industry where shipping a defect is expensive.
A submitted failing test on a real project is checkable by anyone, which makes it rare evidence. That is our reasoning about what is inspectable, not a hiring statistic we have verified.
On salaryWe don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.
Where this route continues
- DevOps Engineer — the pipeline is the natural next step
- Backend Developer — many move into development
- Frontend Developer — sideways move
- Backend Developer — sideways move
This page last verified 2026-07-27 · How we verify
Playwright, MDN and GitHub Actions docs fetched and READ 2026-07-27.