SDET vs QA Engineer
Skills Gap: Where to Focus
Skills Gap: Where to Focus
Moving from QA to SDET isn't about learning everything at once — it's about closing a specific, identifiable gap. This lesson maps that gap so the rest of this path has a clear target.
What a Manual/Automation QA Already Has
- Deep knowledge of the application under test and its failure modes
- Comfort writing test cases and using automation tools (Selenium, Playwright, Cypress)
- An eye for edge cases developers often miss
What "Type A" SDET Adds on Top
| Area | QA / Automation Engineer | SDET |
|---|---|---|
| Code structure | Scripts, sometimes with helper functions | OOP design, applied design patterns, layered architecture |
| Framework | Uses an existing framework | Designs and builds framework infrastructure |
| CI/CD | Runs tests in an existing pipeline | Designs and maintains the pipeline itself |
| Code review | Reviews test code | Reviews production code for testability, gives engineering-level feedback |
| System thinking | Tests one feature/service at a time | Reasons about a system's architecture end to end |
The gap is not "knowing more test tools" — it's the software engineering layer underneath: object-oriented design, patterns, and the judgment to structure a codebase that other engineers can extend.
A Self-Assessment
Rate yourself 1–5 on each, honestly:
[ ] I can explain the difference between an interface and an abstract class, and when to use each
[ ] I have designed a class hierarchy from scratch (not just extended one)
[ ] I can name a design pattern and explain the problem it solves, not just its structure
[ ] I have built framework infrastructure (not just written tests against one)
[ ] I am comfortable reading and reviewing another engineer's production code
[ ] I understand how my test framework's config, logging, and CI pieces fit together
Anything below a 3 is where this path will spend the most time — the modules ahead go roughly in that order: OOP fundamentals → design patterns → framework architecture → engineering skills (review, Git, system design).
A Realistic Timeline
Closing this gap seriously — to the point of passing a Type A SDET interview — typically takes 3–6 months of deliberate practice alongside a full-time QA role, not a weekend. The modules in this path are sequenced so each one gives you something concrete to apply to your current job immediately, rather than saving everything for a future project.
Setting a Concrete Target
Before continuing, write down one thing:
By the end of this path, I will be able to: ___________________
Example: "Design and build a Selenium/Playwright framework from scratch
using the Factory, Builder, and Singleton patterns, with config profiles
and CI integration — as a portfolio project I can discuss in interviews."
Having a concrete target changes how you engage with the OOP and pattern lessons that follow — you're not learning Factory Pattern in the abstract, you're learning it to use in the specific project you just described.
💬 Discussion
Which item on the self-assessment checklist is your biggest gap right now? What is the smallest possible task that would move it from a 2 to a 3?