Test design from a user story
Write boundary, negative and edge cases for a checkout story.
The program
A structured 30-day career transformation.
Not a video course. A daily rhythm of workplace problems, weekly checkpoints and interview practice for one chosen role.
The arc
Four weeks, four proofs, then two interviews.
Thirty steps, one a day. The red ones are the weekly checkpoints you defend; the one at the top is the interview.
W1
Days 1–7
Foundations
The core concepts and tools of the role, and how AI is changing them.
W2
Days 8–14
Practical execution
Doing the actual work, end to end, on realistic scenarios.
W3
Days 15–21
Real-world problem solving
Messy, ambiguous problems with trade-offs and stakeholders.
W4
Days 22–28
Portfolio and interview readiness
Finish your project and prepare to present it.
MI
Days 29–30
Interview prep
The most-asked technical, scenario and behavioural questions, answered in writing.
What you get
One track. Thirty days. Nothing vague.
A structured career program with a clear daily rhythm, not a library of videos.
- Selected career trackEverything you do is specific to the role you want.
- Practical daily challengesOne real workplace problem a day.
- Weekly assessmentsAfter Days 7, 14, 21 and 28, with feedback.
- Role-specific projectEvidence you can show an interviewer.
- Interview preparationRole-specific questions and answer frameworks.
- Interview-prep daysDays 29 and 30: the most-asked questions.
Day by day
Explore all 30 days.
Week 1The new test stack
Day 1 Day 2 Writing a defect report that gets fixed
Turn a vague bug complaint into a reproducible report.
Day 3 Prompting for test cases
Use AI to draft test cases and correct what it gets wrong.
Day 4 First Playwright test
Automate a login flow with stable locators.
Day 5 API testing basics
Validate status codes, schemas and error responses for a REST API.
Day 6 What should an agent own?
Mark which tests in a suite should be automated, agent-generated or kept manual.
Day 7 · Checkpoint Suite audit
Audit a real regression suite and mark what an agent should own, with reasoning.
Week 2Directing test agents
Day 8 Acceptance criteria as contracts
Rewrite ambiguous criteria so an agent can generate tests from them.
Day 9 Generating a suite from a ticket
Generate Playwright tests from a raw ticket and fix the failures.
Day 10 Reviewing AI-written tests
Find flaky locators, missing assertions and false passes.
Day 11 Test data on demand
Generate realistic test data sets for edge cases.
Day 12 API contract tests
Automate contract checks for a payments API.
Day 13 Flaky test triage
Diagnose three flaky tests and fix the root cause.
Day 14 · Checkpoint Ticket to suite
Generate a test suite from a raw ticket and defend its coverage.
Week 3Testing AI systems
Day 15 Why AI features break normal tests
Identify what cannot be asserted with exact matches.
Day 16 Building an eval set
Create 30 test prompts with expected behaviour for a chatbot.
Day 17 Prompt injection checks
Try to break a support bot's instructions and document findings.
Day 18 Scoring with rubrics
Score model outputs consistently using a rubric.
Day 19 Regression on model changes
Compare two model versions and report what changed.
Day 20 Reporting AI quality to stakeholders
Summarise eval results for a product manager.
Day 21 · Checkpoint AI feature eval
Build an eval set for a non-deterministic feature and report pass/fail criteria.
Week 4Pipelines, gates and portfolio
Day 22 Tests in CI
Run your suite on every pull request with GitHub Actions.
Day 23 Quality gates
Define what blocks a release and why.
Day 24 Test strategy document
Write a one-page test strategy for a new feature.
Day 25 Portfolio: architecture
Document your agentic test architecture.
Day 26 Portfolio: walkthrough
Record a 5-minute walkthrough of your project.
Day 27 Interview drill: test design
Answer live test-design questions under time pressure.
Day 28 · Checkpoint Panel review
Present your agentic test architecture to a review panel.