We use cookies for site analytics. Accept to help us understand how the site is used. See our Privacy Policy for details.
A curriculum for Software Development Engineer in Test and QA-engineer loops, which blend a real (if lighter) coding bar with deep testing judgment. Strengthens the coding floor, builds the systems and API knowledge test engineers are expected to reason about, develops object-oriented and framework design sense for test automation, and finishes with the quality-ownership behavioral themes that define the role.
SDET loops include a coding round - usually string and collection manipulation rather than hard algorithms. Get the fundamentals solid.
Test engineers reason about the system under test - HTTP semantics, status codes, database state, and where things break. Build the breadth that lets you design good test cases.
Automation is software. SDETs are graded on whether they can design a maintainable test framework - page objects, fixtures, fakes - so object-oriented design matters. Then reason about testing a real system with rate limits and retries.
QA and SDET loops screen hard for the engineer who owns quality and raises the bar without being adversarial. Bring stories about catching the bug others missed and pushing back on a risky ship.
SDET work is full of 'prove the data is right' questions. These cover the joins and aggregation you need to write assertions against a real database, plus the anti-join pattern for finding orphaned records.
Complexity for reasoning about test-suite cost, and the concurrency sheet for the flaky-test questions that come up in every SDET loop.
21 role-targeted paths are live, from new-grad and backend through SRE, security, data and engineering management. If you have a role you want covered, let us know.
View all paths →