About this tool
Job titles in testing mean different things at different companies, but the skills behind them are fairly consistent. This checklist breaks the work of a QA engineer, SDET or test architect into 28 concrete skills across testing fundamentals, programming, UI automation, API testing, CI/CD, non-functional testing, strategy and leadership, and AI in testing. For each target role it shows a typical expected level, from Aware to Expert. You rate yourself, and the tool ranks your gaps by size, shows a readiness percentage calculated from a stated formula, and groups the gaps by learning path so you know where to start. The expectations are realistic defaults for product companies, not a formal standard, so read them as a conversation starter for your next one-to-one.
How to use it
- Choose the role you are aiming for, not the one you have now.
- Rate each skill from 0 to 3 using the definitions above the list. Be strict: “Working” means you do it alone on real projects.
- Read the biggest gaps and the suggested learning paths on the right.
- Copy the plan to share with your manager or mentor. Ratings are saved in this browser.
QA & SDET Skills Gap Checklist FAQ
How is readiness calculated?
For each skill the role expects, your rating is capped at the expected level, then the total is divided by the sum of expected levels. Being an expert in something the role only needs awareness of does not make up for a gap elsewhere.
What is the difference between SDET 1 and SDET 2 here?
An SDET 1 writes good test code inside an existing framework and pipeline. An SDET 2 is expected to own parts of the framework, the CI integration and the test strategy for a team, which shows up as higher expectations for framework design, flaky test diagnosis, CI and contract testing.
Are these levels an industry standard?
No. There is no single standard for QA career levels. These are typical expectations at product companies; your employer’s career framework, if it has one, takes precedence.