What carries over
| What you did as a WordPress maintenance developer | Where it shows up now |
|---|---|
| Checked forms after updates | Write repeatable form tests |
| Tested checkout by hand | Script a checkout test |
| Spotted layout breaks | Run visual checks across screens |
| Told clients what broke | Write clear bug reports |
What is new
- Writing simple automated browser tests.
- Defining a fixed test scope per site or app.
- Reporting bugs with steps, expected and actual results.
Try it: Test After Update
A plugin update just went live. Decide which four checks to run first and which can wait.
Test After Update
Your first proof in 30 days
Write five automated tests for one real site and run them before and after an update on staging. Share the test repo and a one-page result report.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Worries, answered
I have never written tests. Browser test tools have clear starter guides; five tests is a real start.
Is QA a step down? No. Testing is how a team catches a bad update before customers do.
Pay, honestly
We haven't verified pay data for this move. Productised QA can be salaried or a fixed-price service, so compare offers by what the fixed scope includes.
Your realistic 90 days
You worked as a WordPress maintenance developer. This plan moves you toward QA work in 90 days, using what you already do.
Assumes 2–3 hours a day alongside job applications, a laptop and a phone, and free plans only. Every step has a smaller version and a way to pause. Use them. It runs in three blocks of 30 days, each ending with a signal that you're on track. A signal is not a promise of a job or income.
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Pick one site you can test on staging | Site picked |
| 2 | List its five most important actions | 5 actions |
| 3 | Read the Playwright getting-started page | Notes |
| 4 | Write one test for the contact form | 1 test |
| 5 | Add a second test for login or checkout | 2 tests |
| 6 | Write a bug report template | Template |
| 7 | Save 10 postings | 10 links |
Days 1–30: Five-test pack
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Publish five automated tests and a before-and-after update report | about 8 hours over 3 weeks | repo + report | Two tests. | Stop at the end of the step you're on and write two lines about where you stopped. Pick it up from those notes later. |
| Show your proof to 5 people who hire for this role | about 1 hour | 5 messages | Show it to 2 people who hire for this role. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: Your five tests run clean before an update and catch at least one change after; one of the 5 people you showed them to replies.
Days 31–60: Applications
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Turn your proof into a one-page case and CV line | about 8 hours | case + CV | CV line only. | Put it on hold while interviews take up your time, then come back to it. |
| Apply to 10 QA roles | about 5 hours | 10 logged | Apply to 5 roles. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 60: A screening call.
Days 61–90: Interviews for QA roles
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Practise a 2-minute story of why you are moving | about 2 hours | 2 practice runs | 1 run. | Optional. Skip it if the week is full; nothing later depends on it. |
| Ask 3 former colleagues for referrals | about 2 hours | 3 asks | Just one instead of 3. | Stop sending for now. Keep a list of who you've contacted so you can follow up later without doubling up. |
Signal by day 90: A second round or a paid trial.
Other worries
Age, a career gap, no degree, English, family pressure and savings are covered on the route page and the role page.
One search that fits your background
The full set of search strings for this move is on the route page. These strings work on LinkedIn, Naukri and foundit; Instahyre and Cutshort are worth a weekly look too. Add your old job title to any of them with AND, so your searches surface roles that want both skills.
Job-hunt moves that matter for this route
- Show your test pack and result report.
- Tell one story of a bug you caught before the client did.
- Look at agencies, hosts and SaaS firms that sell or run QA.
Fake-job traps
Watch for 'developer internships' or 'live project training' that charge a registration, laptop or certificate fee, 'test tasks' that ask you to build a full product for free, and anyone asking for an OTP, UPI PIN, a deposit or remote access to your bank before you start. Real employers never charge you to hire you. Use official domains only. Report in India at cybercrime.gov.in or call 1930; in the US, ReportFraud.ftc.gov.
Back to WordPress Maintenance Developer · About the Productised QA route · Development hub
Quick quiz: does this path fit?
Answer each, then press Check. Every answer explains itself.
Make your Path Card
A shareable reminder of where you're heading. The day count starts the first time you open this page; quest XP comes from your log above.
Scam check before you apply anywhere
- Real job and gig platforms are free to join. Never pay a "joining" or "training" fee.
- Never share an OTP or UPI PIN — no genuine employer needs them.
- Use official domains only; type the address yourself.
- India: report at cybercrime.gov.in or call 1930.
- US: report at ReportFraud.ftc.gov.
Small steps, every day.
Each quest has a smaller version for hard weeks, and a pause button. Nothing is lost.
Keep exploring
Sources
Checked 27 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
| What we checked | Where |
|---|---|
| WordPress Site Health screen | wordpress.org |
| Playwright docs: getting started | playwright.dev |