SDET Courses & Learning Paths | sdet.qa - Join the Waitlist

Learn to become a software development engineer in test. Structured SDET learning paths, hands-on test automation courses, and a membership for working SDETs. Join the waitlist.

If you want to break into test automation engineering, or you are already an SDET and want to level up, this is where the training lives. We are building structured SDET learning paths and hands-on test automation courses that teach the way the job actually works: real repos, real CI pipelines, real flaky tests you have to fix. No slide decks that stop at “hello world.”

Courses and the membership are launching soon. The fastest way in is the waitlist below, which also locks in founding-member pricing at launch.

Four learning paths

We are organizing everything into four paths so you always know what to learn next.

1. Aspiring SDET

For manual testers, developers, and career switchers who want their first SDET job. This path starts with programming fundamentals (Python or JavaScript), then moves through your first UI and API tests, version control, and a portfolio project you can put in front of a hiring manager. By the end you can write, structure, and debug automated tests with confidence. If you are early on this journey, start with our guide on how to become an SDET.

2. Test Automation Framework Engineering

For engineers who can write tests but need to design the systems that hold hundreds of them. This path covers the Page Object Model, fixtures and factories, data-driven testing, custom reporters, parallelization, and how to keep a suite fast and non-flaky as it grows. This is the difference between someone who uses a framework and someone who builds one. It maps directly to the skills in our SDET roadmap for 2026.

3. CI Test Infrastructure

For SDETs who want to own the pipeline. This path is about running tests where they matter: CI/CD test infrastructure, GitHub Actions and GitLab CI, containerized test environments, parallel sharding, artifact and report handling, quarantine strategies for flaky tests, and gating merges on quality signals engineers actually trust. This is the work that turns a test suite into a safety net.

4. AI-Augmented Testing

For SDETs who want to stay ahead of where the field is going. This path covers AI-augmented testing: using LLMs to generate and maintain test cases, self-healing locators, evaluating and testing AI features themselves, and knowing where AI genuinely speeds you up versus where it quietly manufactures false confidence. This is the fastest-growing specialization in the discipline right now.

What the membership will include

Beyond individual courses, we are building a subscription membership for working SDETs who want to keep sharpening. The plan is for it to include:

  • A full course library across all four paths, updated as tools and practices change, so one subscription keeps pace with the field.
  • Production-grade code repositories for every course - complete frameworks, CI configs, and example suites you can clone, run, and adapt into your own work.
  • Live office hours where you can bring your real flaky tests, architecture questions, and interview prep to people who do this daily.
  • A community of SDETs to trade patterns with, review each other’s frameworks, and share job leads.

We would rather ship this properly than rush it, so we are opening a waitlist first and building alongside the founding members who join early.

Join the waitlist

Courses and the membership are launching soon, and waitlist members get in first with founding-member pricing at launch.

To join, head to our contact page and mention “course waitlist” in your message. That is it - we will reach out with early access, path recommendations based on where you are today, and founding-member details before anything goes public.

While you wait, two good places to start: our step-by-step guide on how to become an SDET and the SDET salary guide for 2026 so you know what the work is worth. If you learn best by building in the open, our open-source work is a good place to read real test code and contribute.

Whether you are aiming for your first test automation engineer role or moving up the seniority ladder, the waitlist is the front of the line. We will see you there.