BeginnerGetting into QA
How to get into QA in 2026
A practical, no-bootcamp path into software quality engineering — what to learn, in what order, and how to get your first role.
14 min readRead the guide →
A real path, not a reading list.
Most QA advice is scattered across threads and outdated posts. The Guidebook is the opposite: ordered, opinionated, and built from production experience — so you always know what to learn next. Pick the track that matches where you are.
// new to qa
★ The game · 30 daysThe First 30 Days — onboarding gamePlay through your first month as a junior QA engineer, guided by a mentor.Start from zero
No prior testing experience needed. These are interactive lessons — learn by doing, with instant feedback at every step.
Lesson 1 · Interactive · 5 minThink like a testerThe core skill of QA isn't a tool — it's a way of looking at software and asking 'what did they forget?' Let's build that instinct.Lesson 2 · Interactive · 5 minWhat a QA engineer doesThe job title says 'tester,' but testing is only part of it. Let's walk through what the work actually looks like — and why the best testers get involved early.Lesson 3 · Interactive · 4 minUnderstand the business firstYou can't judge how serious a bug is without knowing what matters to the business. This is the skill that turns a tester into a trusted one.Lesson 4 · Interactive · 5 minManual testing still mattersAutomation didn't kill manual testing. The two do different jobs — and the human, exploratory kind finds bugs no script ever will.Lesson 5 · Interactive · 5 minBug reports that get fixedFinding a bug is half the job. Reporting it so a developer can act immediately is the other half — and it's the skill that gets juniors kept.
Prefer to read? Long-form guides cover the same ground in depth:
BeginnerGetting into QA
What a QA engineer actually does all day
Beyond the job title: the real week-to-week work of a quality engineer, from refinement to release — and how it shifts as you get more senior.
10 min readRead the guide →
// growing in qa
★ The QA Lab · 6 toolsThe QA Lab — hands-on tool trainerWorking simulators of an API console, SQL terminal, network tab, logs, locators, and a terminal — with missions.Get genuinely good
You know the basics — now build real depth in API testing, automation, CI/CD, and test strategy that survives contact with production.
Lesson 1 · Interactive · 6 minTest the API, not just the UIMost of what an app does happens below the buttons. Learning to test at the API layer makes you faster, sharper, and much harder to fool.Lesson 2 · Interactive · 5 minWhat to automate (and what not to)Automation is a bet: you spend time now to save time forever. Good testers know which checks pay that bet back — and which quietly lose it.Lesson 3 · Interactive · 5 minFlaky tests, and how to kill themA test that fails sometimes is worse than no test at all — it teaches the whole team to ignore red. Here's how flakiness starts, and how to end it.Lesson 4 · Interactive · 5 minTesting in the CI pipelineYour tests are only as good as when they run. CI runs them on every change, minutes after it's made — here's how to make that feedback loop actually work.Lesson 5 · Interactive · 5 minTest strategy: think in riskYou will never have time to test everything. Strategy is deciding what to test first, what to test lightly, and what to consciously skip — by risk.
Prefer to read? Long-form guides cover the same ground in depth:
IntermediateAPI testing
The API testing roadmap
A structured path from 'what is an API' to confident contract and integration testing — the skills, the order, and where tools fit in.
16 min readRead the guide →
// advanced quality
Modern quality engineering
The current, harder edge: evals, AI-assisted testing, and designing quality strategy for a whole organization.
Lesson 1 · Interactive · 5 minWhen software rolls diceYour whole toolkit assumes the same input gives the same output. AI features break that assumption on purpose. Before you can test them, you need to understand exactly what died — and what survived.Lesson 2 · Interactive · 6 minBuild your first evalAn eval is a dataset plus a grader plus a bar. That's it — and each of the three is a place where testers' instincts matter more than ML knowledge. Let's build one properly.Lesson 3 · Interactive · 6 minThe judge is also on trialFor subjective quality — tone, helpfulness, faithfulness — you'll end up using an LLM to grade an LLM. It works, it scales… and it has documented biases. Trusting a judge you never tested is the eval version of shipping untested code.Lesson 4 · Interactive · 6 minRed-team your own AI featureEvery AI feature ships with a new attack surface: the input is natural language, and natural language can lie, trick, and smuggle instructions. Testing your own feature adversarially — before strangers do — is classic tester work with new ammunition.Lesson 5 · Interactive · 6 minEvals in the pipelineAn eval you run by hand is a demo with paperwork. The finale of this pathway is wiring quality measurement into the machinery: every prompt change gated, every model upgrade regression-tested, production watched for drift.
Dedicated guides are in progress. The thinking already lives in these essays:
- Evals Are the New Unit TestsWhy every team shipping AI features ends up rebuilding a test framework from scratch — and what the good ones look like.
- Why Quality Is the Real Bottleneck in AI EngineeringGenerating code with an LLM is the easy part. Knowing whether the generated code is right is the whole job — and it's harder than it sounds.
- How AI is Changing the QA Engineer RoleA deep look at how AI tools are reshaping quality engineering — and why the skill of breaking systems is more valuable than ever.
Not sure where you fit?
If you're new to quality engineering, start at the beginning — the first guide assumes nothing.