Career path
Product Manager
A product manager owns the why and what of a product — deciding what to build and in what order so the team solves real user problems and the business grows. They sit at the intersection of users, engineering, design, and the business, with lots of responsibility and very little direct authority.
What the job actually is
PMs make decisions under uncertainty and get a team aligned behind them. That means talking to users, defining problems clearly, prioritising ruthlessly, writing crisp specs, and saying no to good ideas so the team can ship the great one. The craft is judgement: you rarely have enough data, and the job is to make a sensible call anyway and learn fast.
Skills that matter
- Communication and influence — you lead without authority.
- Prioritisation — deciding what not to do is the core skill.
- User empathy and product sense — knowing what good looks like.
- Comfort with data — enough to frame and read the numbers.
- Just-enough technical fluency to work credibly with engineers.
How to switch in
There's no single path, which is why engineers, designers, marketers, analysts, and support leads all become PMs. The most reliable route is to start acting like one in your current role: own a problem end-to-end, talk to users, and drive a small project to launch. Internal moves into PM are common and often easier than switching companies cold.
Frequently asked questions
Do I need to be technical to be a product manager?
You need enough technical fluency to work well with engineers and reason about trade-offs, but you don't usually need to code. Strong PMs come from design, marketing, analytics, and support as well as engineering.