There's no single degree that makes you a PM. When I evaluate education requirements—for myself or a hire—I separate credentials from capability.
What usually matters more than the diploma
- Evidence you can discover problems and ship outcomes
- Communication that survives exec and eng scrutiny
- Comfort with data enough to make decisions (not become an analyst)
- Domain context when the product is specialized
When formal education helps
| Situation | Education can help by… |
|---|---|
| Career switch with thin proof | Signaling seriousness + structured learning |
| Highly regulated / technical domains | Shared vocabulary with experts |
| Some companies' HR filters | Clearing a checklist (frustrating but real) |
A CS or MBA background can help—neither is universal. I've seen great PMs from support, design, sales eng, and ops.
What I'd do instead of collecting degrees forever
- Ship a portfolio case (problem → options → decision → result)
- Close specific gaps (SQL basics, discovery interviews, roadmapping)
- Get feedback from practitioners, not only courses
If you want structured craft without pretending a certificate replaces proof, look at a PM Certification. Keep learning via the newsletter.