If you Google “how to become an SDET” or “how to start a QA career,” you’ll get a firehose of information.
Blog posts. YouTube playlists. Medium articles. Reddit threads. Courses. PDFs. Opinions.
Most of it isn’t wrong. It’s just scattered. And it doesn’t tell you what to do first.
That’s where people get stuck. Not because they’re incapable. Because no one hands them a map.
So this isn’t another “top 50 links” post.
This is a curated roundup of SDET, TE or QA resources that are actually respected in the industry, plus guidance on when and why you’d use them if you’re preparing for SDET interviews or planning a QA career transition.
Think of this as internet archaeology, already organized.
Throughout this post, I’m using Software Development Engineer in Test (SDET), Quality Assurance (QA), and Test Engineer (TE) somewhat interchangeably. Different companies use different titles, but the interview expectations overlap far more than people expect.
Start With Foundations (Before You Touch Automation)
If you’re trying to break into an SDET, TE, or QA role, this is where most interview prep should actually start.
A common mistake is jumping straight into tools and frameworks without understanding how testers think.
Before worrying about Selenium, Playwright, or language-specific syntax, you need a mental model for:
- What testing is actually trying to achieve
- How to reason about risk
- How to talk about quality in a structured way
Foundational resources help you answer questions like:
- “How would you test X?”
- “What would you prioritize and why?”
- “What does good coverage actually mean?”
If you skip this step, interviews become a memorization exercise instead of a reasoning exercise.
Resources I’d actually point people to:
- Lessons Learned in Software Testing (Cem Kaner, James Bach, Bret Pettichord)This is still one of the best ways to learn how testers reason about risk and coverage.
- James Bach’s blog and talksNot everything will resonate, and that’s fine. What matters is learning how to think in heuristics instead of checklists.
Automation & Coding Practice (With Intent)
Strong automation skills are table stakes for most SDET roles, but how you practice matters more than how many problems you solve.
Especially in interviews, interviewers care less about the tool and more about how you reason through tradeoffs.
Not all automation practice is created equal.
Some resources are great if you’re brand new and just need reps. Others are better if you already automate at work but struggle to explain your decisions in interviews.
When evaluating automation resources, ask yourself:
- Is this teaching syntax, or teaching problem solving?
- Does it mirror the way interviewers actually assess code?
- Am I learning how to design tests, or just write them?
The goal here isn’t to collect tools. It’s to build confidence under pressure.
Resources I’d actually point people to:
- LeetCode (used selectively).Not to become a DSA god, but to practice communicating logic clearly while coding.
- Playwright or Cypress docs and examples.Pick one. Learn it deeply enough to explain why you’d choose it and where it breaks down.
Interview-Specific Prep (Where Most Resources Fall Short)
This is where SDET interview prep usually breaks down, even for experienced engineers.
Here’s the uncomfortable truth: most SDET, TE, QA resources teach skills, not interviews.
Interviews are their own game. And most people underestimate how different that game actually is.
They care about:
- How you structure your thinking
- How you communicate tradeoffs
- How you scope problems in real time
This is why people can be strong engineers and still feel blindsided in loops.
The most useful interview prep resources do three things:
- Simulate real interview scenarios
- Provide repeatable frameworks
- Teach you how to talk about your work, not just do it
Resources I’d actually point people to:
• High-quality mock interview walkthroughs on YouTube where candidates explain their thinking out loud, not just the final answer.(Example search: SDET mock interview)
• Structured testing frameworks that help you answer “How would you test X?” without rambling.
Community & Ongoing Learning
Building a long-term SDET, TE, or QA career means learning beyond interview prep alone.
Communities can be incredibly valuable, or incredibly noisy, depending on how you use them.
Some are great for:
- Seeing real interview questions
- Learning how other engineers think
- Staying current as the field evolves
Others are better treated as background signal.
You don’t need to engage everywhere. Lurking counts. Being selective is a skill.
Communities worth sampling (with discernment):
- LinkedIn groups focused on SDET, TE, and QA roles.Signal varies, but patterns emerge over time.
One example is the The SDET Playbook LinkedIn group, which we built specifically to keep discussions interview- and career-focused rather than tool-of-the-week noise.
- Reddit and Discord communities.Read more than you post. Pay attention to what experienced engineers consistently emphasize.
We also run r/TheSDETPlaybook for longer-form discussions around interview strategy, frameworks, and real-world loops.
The Pattern You’ll Eventually Notice
After stitching together enough of these resources, a pattern becomes obvious.
The information isn’t the problem.
The lack of structure is.
Most resources answer individual questions, but very few show how everything connects across the actual hiring process.
Recruiter screen. Technical screen. Final loop.
Different stages test different things, yet most prep treats them the same.
Why We Built The SDET Playbook
After years of pulling from all of the resources above, we kept seeing the same gap.
People didn’t need more links.
They needed sequencing.
We built The SDET Playbook to act as a one-stop, structured guide for SDET, QA, and TE interview preparation that mirrors how real interview loops actually work.
Not just what to study, but:
- When to focus on what
- How interviewers evaluate your answers
- How to move through each stage with a plan
The internet gives you ingredients.
We built the recipe.
If you’re tired of juggling tabs and want a clear, end-to-end path for your SDET or QA career, that’s exactly what this book is for.
If you want to see how the playbook is structured, what it covers, and who it’s designed for, start here.
Stop guessing. Start navigating.
