- When you find a bug, what do you enjoy most — finding it, explaining it, or making sure it never comes back?
- Do you prefer judging quality or breaking things on purpose?
- Would you rather write less code or learn a bit more?
Your answers point to a route below. Finding plus breaking → red-teaming. Explaining plus judging → AI evaluation. Never-again plus a bit more code → AI test automation.
Testers are still in demand: "software tester jobs" is typed into search about 4,400 times a month from India alone (OpenSEO, Oct 2026). Testing hasn't disappeared. But AI products need testers who can judge answers, not just buttons, and that's where your skills travel.
Bug Report Glow-Up
Paste an old bug report (or use our sample: "login not working pls fix"). Press "Glow up" and it transforms, with a small sparkle animation, into a clean report: title, steps, expected, actual, environment, severity. Then a second button, "Make it an AI bug", rewrites the same structure for a chatbot: prompt, expected behaviour, actual answer, why it matters. It shows how little changes. Everything runs in your browser; nothing is sent anywhere.
Bug report glow-up
Which route? Follow the arrows
- Do you need some income within 30 days? → Yes: start crowdtesting on a listed platform as bridge income, then continue. → No: go to the next question.
- Do you enjoy reading and judging answers carefully? → Yes: AI evaluator.
- Do you enjoy finding the ways things can be misused? → Yes: AI red-teamer.
- Are you willing to learn a low-code or AI-assisted automation tool? → Yes: AI test automation.
- Would you like to sell testing as a fixed package to small businesses? → Yes: productised QA.
Sort these tasks
Decide your answer first, then tap a card to check.
Each card\'s back shows where most testers placed it.
What you already have
| Your manual-testing habit | Where it helps |
|---|---|
| Reading requirements closely | Writing and applying rating guidelines |
| Exploratory testing | Red-teaming and edge cases |
| Clear bug reports | Evaluation notes and red-team findings |
| Regression checklists | Automated suites |
| Patience with repetition | Large rating batches |
Bridge income, honestly
Crowdtesting can bring in some money while you build a main route. uTest and Testlio are the two we list for manual QA work. The AI-training platforms and our verdict on each are on the AI evaluator route page.
One name you may see in ads, DataAnnotation, is not for India: it doesn't take applicants based here, and a VPN won't change that safely.
Work volume is never guaranteed. Apply only on official domains and never pay a fee.
Free things to learn with (checked 23 Oct 2026)
- OWASP Top 10 for LLM (large language model) Applications (2025) — free reading on AI risks.
- ISTQB Certified Tester AI Testing (CT-AI) v2.0 — a recognised syllabus. Exam fees vary by national board; check your board.
- Katalon Free Studio — record-and-playback authoring and local runs at no cost.
Which route fits your years in testing
0–3 years: AI evaluator or productised QA. 3–8 years: AI test automation or red-teaming. 8+ years: lead evaluation or red-team programmes; your judgement on what "good" means is the asset.
Testing work in India and globally
India: IT services firms are adding GenAI testing to client work; product start-ups need AI QA; crowdtesting reaches Indian testers but volume varies. Global: AI evaluation and red-teaming roles at product companies and labs; remote contract work with mixed terms. Tax and visa questions are outside our scope.
Your realistic 90 days
You wrote test cases in Excel or TestRail, logged bugs in Jira, and did regression the night before every release. Manual-only QA roles have thinned out, but your eye for what breaks is exactly what AI products need. This plan tests four routes using the test cases you already wrote.
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.
What AI changed in your old tasks
| You used to… | Now you… |
|---|---|
| Executed test cases step by step | Judge AI answers against a rubric (AI evaluator) |
| Hunted edge cases nobody specified | Try to make AI systems misbehave, safely (red-teaming) |
| Ran the same regression every sprint | Automate it with Playwright or an AI-assisted tool |
| Tested for one employer | Offer a fixed QA package to small product teams |
Your first 7 days
| Day | Task | Done when |
|---|---|---|
| 1 | Open your old test cases (or rewrite 20 from memory, no company data) | 20 cases in a Sheet |
| 2 | Evaluator try-out: score 10 AI chatbot answers on accuracy and tone | 10 scored rows |
| 3 | Red-team try-out: write 10 tricky prompts against a public chatbot and log what failed | 10 logged attempts |
| 4 | Automation try-out: record one login test with Playwright's codegen | Test runs |
| 5 | Productised QA try-out: write a one-page 'release check' offer for a small app | Draft offer |
| 6 | Score all four; pick one | Choice written |
| 7 | Save 10 postings for it | 10 links |
Days 1–30: Your test cases, reused
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Turn your 20 rewritten test cases into a proof you can show a QA lead | about 10 hours over 3 weeks | a shareable Sheet or repo with results | 10 cases. | Save or commit what works now and stop adding. A finished small version beats an unfinished big one. |
| Message 5 ex-teammates (devs and QA) with the proof | about 2 hours | 5 messages sent, replies noted in your tracker | Message 2 ex-teammates (devs and QA) with the proof. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 30: A QA lead or ex-colleague responds to your proof.
Days 31–60: A bug report pack
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Test a public web app you didn't build and file a bug report pack | about 10 hours | 5 bugs written up and linked next to your first proof | Two well-written bugs from that app. | 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. |
| Apply to 10 roles where your manual tester years count | 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 or a platform test passed.
Days 61–90: Interviews
| Step | Time | Done when | Smaller version | If you need to pause |
|---|---|---|---|---|
| Prepare 3 bug stories: what you found, how, and the impact | about 2 hours | 3 stories | Your single strongest bug story. | Optional. Skip it if the week is full; nothing later depends on it. |
| Follow up every application from your tracker | about 2 hours | each row has a follow-up date | Only the 3 roles you want most. | Optional. If reaching out feels like too much this week, skip it and put the time into your proof. |
Signal by day 90: A QA lead asks you back for a second round, or a crowdtesting platform pays for your first accepted bug.
Job-hunt moves that matter for this route
- Search 'AI QA', 'AI evaluator', 'Playwright', 'red team' on LinkedIn and Naukri.
- Check each crowdtesting or AI platform's India eligibility before signing up.
- Never pay to join a testing platform.
Where the openings are, and what to type
Also worth a weekly look: Instahyre, Cutshort, Wellfound, and iimjobs or hirist for senior roles. Upwork and Contra if you want freelance work.
IT services firms, testing vendors and product companies. Naukri lists many QA roles; LinkedIn adds 'AI evaluator' and AI QA posts.
- LinkedIn search string:
("manual tester" OR "QA analyst") AND (AI OR LLM OR evaluation OR automation) - Naukri / foundit keywords: manual testing, QA analyst, AI evaluator, test analyst
Worries people bring to this route
- Manual tester at 40+, is it over? Careful judgement is exactly what AI evaluation needs.
- A gap. A dated eval sheet on a public chatbot closes it.
- Only BSc or BCA. Very common in testing teams.
- English. Bug and eval reports follow templates.
- Family says testing has no future. Testing AI is a growing kind of testing.
- Runway. Regular QA roles still hire; apply alongside.
Your 30/60/90 quests
XP: learning 20 · proof 60 · outreach 40. Ranks: Wayfinder → Builder → Pathmaker. Progress stays in your browser only.
Pay for testers moving into AI
We haven't verified pay data for these routes, and we don't quote platform rates on this site.
Task scams aimed at testers
India's I4C and the US FTC both warn about "task" job scams on Telegram and WhatsApp: small payouts first, then deposits. Never pay to get paid. Never share OTPs or UPI PINs. Official domains only. Report: cybercrime.gov.in / 1930 (India), ReportFraud.ftc.gov (US).
Manual testing questions
Is manual testing dead? No. Searches for tester jobs remain steady, and AI products need human judgement. The work is shifting, not vanishing. Do I need to code? Not for evaluation or productised QA. A little helps for automation.
Take the quiz · Related: Automation tester · AI training jobs
Newer step-by-step plan: Manual Tester → Accessibility Specialist, each with one proof project and a 90-day schedule.
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 between 21 Oct 2026 and 23 Oct 2026. We opened every link below ourselves. Search volumes on this site come from OpenSEO keyword research (Oct 2026).
| What we checked | Where |
|---|---|
| ISTQB CT-AI v2.0 | istqb.org |
| OWASP Top 10 for LLM 2025 | genai.owasp.org |
| Platform verdicts (uTest, Testlio, Outlier, Alignerr, Turing, Test IO, DataAnnotation) | AINewPath platform checks (Oct 2026) |
| Katalon Free Studio | katalon.com |