Structured tracks from manual testing to AI-assisted automation.
From QA foundations to a portfolio-ready Playwright framework, in one mentor-guided track. Homework is reviewed at every gate.
A complete manual testing course in 11 modules: the SDLC, team roles, Scrum and Kanban, learning a product, test documentation, Jira/Confluence/TestRail, the test pyramid, test design techniques, terminology, professional growth and, to finish, ISTQB and the principles of testing. Every example and exercise runs on one end-to-end product, MediBook.
TypeScript from scratch for a tester who has never written code: the environment and tsconfig, the type system, functions and pure computation, scope and modules, collections, asynchrony, classes, generics, utility types and Result<T, E>. 8 modules, 32 lessons, 40 hours, the end-to-end medibook-tools project and two milestones on the MediBook product.
Code that other people read and change: clean names and functions, SOLID on a test framework, the Page Object / Builder / Factory / Strategy patterns, a catalogue of test automation anti-patterns, framework architecture with ADRs, Git from its model to team review, and working with an AI assistant. 8 modules, 32 lessons, 40 hours, an end-to-end refactoring of the medibook/qa-automation repository and a gate milestone — the medibook-report CLI tool.
The complete automation QA path on one repository, medibook/qa-automation: the web under the hood and REST APIs, Postman and OpenAPI, authorisation and tokens, API tests in TypeScript, Playwright from the config to Page Objects and fixtures, network interception, visual and a11y checks, stability and parallelism, reporting and failure investigation, checks in PostgreSQL, CI/CD on Docker and GitHub Actions, performance and security, AI in testing and a Capstone framework defence. 18 modules, 77 lessons, 307 hours, 4 gates.
Python from scratch for a tester who has never written code: the environment and venv, types, numbers and strings, branching, loops and pure functions, collections and comprehensions, modules, files and exceptions, OOP with dataclass, requests and pytest. 8 modules, 32 lessons, 40 hours, the end-to-end medibook-scripts project and two milestones on the MediBook product.
Mobile testing for a tester who has only tested the web so far: platforms and fragmentation, app types and deep links, gestures and screen states, the network, interruptions and permissions, emulators, adb and proxies, logs and crashes, a device matrix and test design, a store release with a staged rollout. 8 modules, 32 lessons, 45 hours, the end-to-end feature MB-2107 “rescheduling fee” in the MediBook 2.4 mobile release, and two milestones.
Mobile automation for an automation engineer who already knows Playwright. First the MediBook mobile web in Playwright: device descriptors, touch gestures, geolocation and permissions, offline and a slow network, the time zone, breakpoints, horizontal scroll and visual snapshots at mobile widths. Then native Android and iOS apps through Appium and WebdriverIO in TypeScript: the architecture and the first test, locators and Screen Objects, permissions, the network, interruptions, deep links, updating over an old version, an emulator in GitHub Actions, device farms and stability — with the honest price of every decision. 6 modules, 24 lessons, 40 hours, two gates: a mobile web suite and a native suite in CI.
SQL for a tester on a live MediBook database in PostgreSQL 16 that you bring up yourself in Docker: the relational model and the schema, SELECT and NULL, JOIN and the row duplication trap, aggregation and the clinic report, subqueries, CTEs and window functions, changing data, transactions and the race for a slot, indexes and EXPLAIN, an overview of NoSQL and database checks in automated tests. 8 modules, 34 lessons, 40 hours, a gate — a timed SQL exam — and an investigation of the incident “the patient did not get their refund”.
An ATS-ready master resume by a recruiter's method: format and header, achievements by XYZ / CAR / PAR, a Summary in 150 and 50 words, Skills, education and extra sections, tailoring to a vacancy with an AI assistant, the resume through a recruiter's eyes, a four-paragraph cover letter and an honest story of your path. 4 modules, 16 lessons, 20 hours, the “Resume package” milestone.
Finding a first job as a process with numbers, not a lottery: the application funnel and diagnosing by it, vacancy selection criteria and red flags, three baskets of vacancies, salary expectations and test tasks; a 5–8-sentence cover letter and first messages in three formats — the Djinni field, email, LinkedIn; an application tracker, follow-ups, asking for feedback and a gap register, a weekly search rhythm without burnout; networking without connections, informational conversations and referrals. 4 modules, 16 lessons, 16 hours, the “Two weeks of searching, with numbers” milestone.
The first call with a recruiter from the greeting to the next steps: what a screening really checks and what it does not, technical preparation for a video call, the 60–90-second rule, a bank of 25 typical questions in the “claim — specifics — result — link” structure and STAR on training experience, a screening in English with a self-introduction, 12 answers and rescue phrases, the money conversation in three strategies, terms and employment formats, red flags on both sides and 20 questions for the company. Complete dialogues with a breakdown and the recruiter's notes after the call. 4 modules, 16 lessons, 16 hours, the “Mock screening recording” milestone.
The Junior QA technical interview as a skill of its own — explaining out loud what you can do with your hands: the 60–90-minute conversation format, thinking aloud, clarifying questions and three “I don't know” formulas; question banks with answer skeletons and branches for QA theory (40) and Playwright automation (30), 15 SQL tasks on the MediBook schema, 12 TypeScript live coding tasks and “what does this code return” snippets, a 10-minute defence of your own framework and a mock interview script with a 20-criterion form. 6 modules, 24 lessons, 30 hours, the “Full mock interview” milestone.
The final hiring stage, where the people talking to you are not engineers: a Product Owner, a Delivery Manager, a head of department, a client or a founder. Who checks what, the four measures of business — money, time, risk, reputation — the answer to “what value does testing bring” in 30, 60 and 90 seconds, a 40-row dictionary from engineer-speak to business language, how to say “no” so that it is heard, a bank of 25 case and conflict situations with a breakdown, 25 questions for the company and an offer evaluation checklist. All on the MediBook business context, with complete dialogues. 4 modules, 16 lessons, 14 hours, the “Mock stakeholder conversation” milestone.
The three to seven days between the words “we are ready to make you an offer” and the first working day: how to read an offer (compensation, employment formats, gross and net, the probation period, termination terms, red flags), how to size up your leverage honestly and ask for more once — five complete scripts, the company's lines and what they really mean, what to ask for instead of money and when not to negotiate — and how to decide: an offer comparison matrix, acceptance and decline letters, a plan for the first 90 days and preparing for a compensation review. No salary figures and no legal advice — just the questions you need to ask. 3 modules, 12 lessons, 10 hours, the “Offer breakdown and negotiation prep” milestone.
How a tester works with AI assistants so the result can be trusted: set the task as a specification and verify the answer. Eight modules on one storyline — a six-week “AI in QA” pilot in the MediBook team: how a language model works and where it goes wrong; the prompt as a test specification and the team's prompt library; data, privacy and the AI usage policy; requirements analysis and test design with every boundary checked; bug reports, test data, logs, SQL and reports; automation — from a draft test to an agent in the repository; testing the product's AI features — an eval set, a judge, injection defence; measurements, cost and a decision for each task type. Every technique is shown in full: the prompt, a sample answer, the check, the errors found and the cost in minutes. 8 modules, 32 lessons, 40 hours, two milestones. The first two lessons are free.
The engineering foundation for the Forward Deployed Engineer role — the person who takes code to the customer and is responsible for it working there, not just on a laptop. Git without the fear of mistakes: the working tree, the index and the commit, a commit made on main by mistake, the reflog. The command line: environment variables and subshells. Docker: images without secrets in their layers, compose with healthy services, and why an application in the cloud gets its permissions through a role rather than someone else's keys. Python and SQL come from the prerequisites.