Role Pack · Mid to Senior
QA / SDET Interview Pack
Test design, automation frameworks, CI integration and shifting quality left.
Test strategy, automation patterns, flakiness, and quality across the pipeline.
- Questions
- 360
- Topics
- 20
- Pages
- 250pages
- 360 questions, every one with a model answer
- Test-design cheat sheet
- Automation framework patterns
- CI & flake handling
Get the QA / SDET Interview Pack — $9
One-off. Delivered as a PDF by email the moment payment clears.
Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
- Test strategy, risk and coverage
- The test portfolio and where each test belongs
- Test case design techniques that survive contact
- State machines, workflows and use case coverage
- Designing unit tests that survive refactoring
- Test doubles, seams and dependency injection
- Integration testing, contracts and service boundaries
- API testing, schema validation and contract checks
- Browser end to end automation with Playwright
- Designing end to end tests that do not rot
- Test data, fixtures and environment control
- Component and frontend testing with Testing Library
- Diagnosing and eliminating flaky tests
- Parallelism, sharding and suite runtime
- CI pipelines, quality gates and pull requests
- Shift left, static analysis and defect prevention
- Performance, load and resilience testing
- Accessibility and security testing in the quality process
- Defect management, triage and quality metrics
- Automation strategy, return on investment and rollout
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
- Coverage is a conversation about risk, not a percentage to maximise.
- Cheap tests that fail for the right reason beat comprehensive slow ones.
- Equivalence classes shrink an input space you cannot enumerate.
- Draw the state machine before writing tests, because the gaps become obvious.
- Name the test after the behaviour or rule, not after the method under test.
- A stub answers a question, a mock asserts on a call, a fake replaces behaviour.
Questions this pack covers
- How do you decide what not to test?
- What would you actually write in a test strategy for a brand new product?
- How do you decide whether a test belongs at unit level?
- What belongs in a smoke suite for a web application?
- How do you pick the boundaries worth testing around a date field?
- When is pairwise testing enough for a configuration matrix?
- How do you model a checkout workflow as a state machine?
- Which illegal transitions actually deserve an explicit negative test?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
- How many questions?
- 360, spread across 20 topics, written out in full across 250 pages.
- Do the answers just list keywords?
- No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
- How do I get it?
- Pay once and the PDF arrives by email immediately, with a signed download link.
- Can I get it refunded?
- Yes, if it is not what you expected. See the refund policy.
