Thinking
Do PMs need to be technical
The real answer is more fluid than “learn to code” versus “just strategy.”
Some people say learn to code or get left behind. Others say your job is strategy, not writing code.
The reality depends on the product, the team, and the problems you want to work on.
If you are highly technical
- Infrastructure and platforms where systems design is the product.
- Personalization and recommendation where models and evaluation matter.
- Payments and fraud where tradeoffs show up in reliability and risk.
If you are less technical but still strong
- Customer psychology and UX where behavior is the main lever.
- Growth and retention where loops and incentives matter.
- Marketplaces where balancing supply and demand is the system.
Why technical fluency helps
- You can understand tradeoffs earlier and avoid false simplicity.
- You can read design docs and ask better questions.
- You can debug patterns in data and logs without waiting for a walkthrough.
You do not need to be technical to be a strong PM. But technical fluency expands the surface area of problems you can own, and it often accelerates your ability to earn trust with engineering.