From Software Engineer to Product Manager: My Transition
I studied Software Engineering at university. I could build full-stack applications, design databases, and write clean code. But I kept finding myself more interested in why we were building things than how. That curiosity eventually led me to product management, and my technical background became my biggest advantage.
Why I Made the Switch
During my internship at Pandai Education, I was involved in both building features and making product decisions. I noticed that the decisions about what to build had more impact than the code itself. A well-chosen feature built with average code outperformed a poorly-chosen feature built with excellent code every time.
I realized I wanted to be the person making those decisions, informed by technical understanding but focused on user and business outcomes.
What Technical PMs Do Differently
Speak the Engineers' Language
When I discuss trade-offs with engineering, I don't need them translated. I understand when someone says "this requires a database migration" or "this endpoint will have N+1 query issues." This builds trust and speeds up decision-making because engineers don't have to simplify their concerns for me.
Better Feasibility Intuition
Before proposing a feature, I have a reasonable sense of its technical complexity. This doesn't mean I estimate effort (that's engineering's job), but I can avoid proposing solutions that are architecturally impractical. It also means I can suggest simpler technical approaches when the complex solution isn't necessary.
Stronger API and Integration Thinking
At Paydee, understanding API design helped me write better technical specs for our payment gateway integration. I could think about edge cases, error handling, and data flow in ways that made the PRD more useful for the engineering team.
Automation and Tooling
My technical skills let me build internal tools that improved team productivity. At BrioHR, I built automation tools that streamlined processes across product and engineering teams, something a non-technical PM would need to request from engineering.
The best thing about being a technical PM isn't writing code. It's having the credibility and context to make better product decisions alongside your engineering team.
What I Had to Learn
Technical skills got me in the door, but product management required an entirely new skill set:
- User empathy: Engineers solve technical problems. PMs solve human problems. Learning to deeply understand user motivations, not just their feature requests, was a mindset shift.
- Prioritization: As an engineer, I could work on one thing at a time. As a PM, I had to choose which things not to do. Saying "no" is the hardest and most important PM skill.
- Communication: Engineering communication is precise and technical. PM communication needs to adapt to the audience: business stakeholders, designers, engineers, and customers all need different framing.
- Letting go of implementation: The hardest part was learning to define the problem and desired outcome, then trusting the engineering team to find the best solution. My instinct to jump to technical solutions sometimes got in the way.
Advice for Engineers Considering PM
- Start by asking "why" more. In your current role, start questioning the product decisions behind the features you're building. This builds PM muscle.
- Get close to users. Sit in on customer calls. Read support tickets. Watch session recordings. Understanding users is the foundation of everything in PM.
- Learn the business side. Understand your company's revenue model, unit economics, and competitive landscape. Technical PMs who also understand business have a rare and valuable combination.
- Don't abandon your technical identity. Your engineering background is a superpower, not something to leave behind. The best technical PMs stay close to the technology while focusing their energy on product strategy.
The transition from engineer to PM isn't about choosing between technical and non-technical work. It's about expanding your impact from building solutions to choosing which problems are worth solving. For engineers who are curious about the bigger picture, it's one of the most rewarding career moves you can make.