// Interview Prep/Role-based prep/Manual QA
📝 Manual QA interview prep
Test design, exploratory testing, and defect reporting — the craft behind every quality release.
// WHO THIS IS FOR
For engineers interviewing for roles focused on structured and exploratory testing, requirements analysis, and defect lifecycle management. Covers junior-to-mid scopes where the interviewer is assessing your testing instincts, communication with developers, and ability to write test cases that find real bugs.
// SKILLS INTERVIEWERS EXPECT
Green = most frequently tested
// TYPICAL INTERVIEW ROUNDS
Fundamentals screen
30–45 min with a QA lead or hiring manager. Expect questions on the testing pyramid, types of testing (smoke, regression, sanity, exploratory), the defect lifecycle, and SDLC models. Interviewers assess whether you use precise vocabulary and understand why each test type exists — not just that you know the words.
Test case design exercise
Given a feature description or a set of requirements (login form, search field, date picker), write test cases covering happy paths, edge cases, negative paths, and boundary values. You may be asked to justify your coverage choices and estimate risk. Interviewers look for completeness, structured thinking, and the ability to spot ambiguity in requirements before writing a single test.
Exploratory and bug-reporting task
Test a live staging environment, a web app, or a provided APK for 20–30 minutes without a script. You are expected to charter your session, log findings as structured bug reports (title, severity, priority, steps to reproduce, expected vs actual), and debrief on your approach. Interviewers grade the quality of your bug reports and whether you explored beyond the obvious paths.
Behavioural
Situational questions — a developer disputes your bug, a deadline cuts regression scope, a feature ships without sign-off. Also covers how you communicate test progress to stakeholders, how you decide what not to test, and how you've advocated for quality without a seat at the planning table.
// TOPICS TO STUDY
- Equivalence partitioning and boundary-value analysis — applied to real form fields
- Decision tables and state-transition testing for business rules
- Exploratory testing: session-based charters, time-boxing, and heuristics (SFDIPOT)
- Defect lifecycle: new → assigned → fixed → verified → closed, plus reopen flows
- Bug report anatomy: clear title, severity vs priority, minimal steps to reproduce
- Risk-based test prioritisation: impact × likelihood matrices
- Regression vs smoke vs sanity: when to run each and how to scope them
- JIRA: defect workflow states, JQL filtering, Zephyr test cycles
- SQL basics: SELECT, WHERE, JOIN, GROUP BY for test data validation
// READINESS SELF-CHECK
How ready are you for a Manual QA interview? Score yourself 1–5 per competency. Be honest — it is a map of where to focus, not a test. Nothing is saved; print or copy it to track over time.
| Competency | 1–2 — weak signals | 4–5 — strong signals | You |
|---|---|---|---|
| Test case design | Covers the happy path only; misses boundary values, negative cases, and edge conditions. | Applies EP, BVA, and decision tables; spots requirement ambiguity before writing the first test. | __/5 |
| Exploratory testing | Clicks around without a session charter or structured heuristic; findings are inconsistent. | Uses SFDIPOT or similar heuristic, time-boxes sessions, and adapts coverage from findings in real time. | __/5 |
| Bug reporting | Vague title, missing reproduction steps, no justified severity or priority. | Reproducible minimal steps, clear expected vs actual, severity justified with user-impact reasoning. | __/5 |
| Requirements analysis | Accepts specs at face value and starts writing tests without questioning ambiguities. | Flags untestable requirements, asks clarifying questions, and identifies missing acceptance criteria. | __/5 |
| Risk-based prioritisation | Tests everything in specification order regardless of risk or time pressure. | Scores by impact x likelihood, scopes regression from a risk map, and justifies what to defer. | __/5 |
Reading your score — max 25
Your lowest two competencies are your study list — see Topics to study above and the Manual QA prep plan.
🗓️ Structured prep plan available
A day-by-day plan with study, practice exercises, and deliverables to get interview-ready.
More for this role coming soon
Hands-on test-case-design exercises and exploratory testing drills with rubrics are coming soon.