Free tool for product managers
Technical PM skills assessment
Fifteen questions, about five minutes. Twelve check how well you understand the technology behind your product; three ask what you have already built. You get your level from 0 to 4, your strong and weak areas, and exactly which guides to read next. Answers stay in your browser.
The five levels
| Level |
Name |
What it looks like |
| 0 |
Non-technical PM |
Engineering discussions are hard to follow; terms like API, migration or deploy feel vague. |
| 1 |
Tech-aware PM |
You know the common terms but can’t yet reason confidently about how systems fit together or what a trade-off costs. |
| 2 |
Technical PM |
You can discuss APIs, data, authentication, architecture and trade-offs with engineers and write requirements that cover failure cases. |
| 3 |
AI product builder |
You also use Git and AI coding agents to prototype and build working software yourself. |
| 4 |
AI-native technical PM |
You can take an idea from requirements to a deployed product with AI agents — and review, secure and debug what they build. |
The levels are a practical guide, not an industry standard. Most product managers who work closely with engineers sit at level 1 or 2 — and the jump from 2 to 3 is mostly practice, not theory.
How the score works
- Twelve knowledge questions cover how the web works, APIs, data, authentication, Git, architecture, security and AI agents. “I’m not sure” is always an option — guessing only makes the result less useful.
- Three experience questions ask whether you have used Git, built something with an AI coding agent and shipped it.
- Knowledge decides whether you are at level 0, 1 or 2; hands-on experience on top of solid knowledge moves you to 3 or 4.
After you submit, every question shows the correct answer and a short explanation, so the assessment is also a quick lesson.
What to do with your result
Retake the assessment after a few weeks of practice to see how far you have moved.