Three years ago, I was writing Go microservices at a Series B fintech. I was good at it. I was also slowly going crazy.
Not because engineering is bad — it's not. But I kept finding myself in meetings thinking *"we're building the wrong thing"* and not having the platform to say it out loud. So I decided to do something about it.
What I Thought the Transition Would Be Like
I assumed my engineering background would be my superpower. I figured I'd waltz into PM interviews, impress everyone with my technical depth, and get offers left and right.
I was wrong on almost every count.
What Actually Happened
My engineering skills mattered less than I thought. Yes, being technical helped me read PRDs critically, push back on engineering estimates, and earn credibility with the team fast. But no PM interview asked me to debug code or architect a system. They asked me about users.
Ambiguity was a genuine shock. In engineering, done means done. Tests pass, code ships. In PM, "done" is a negotiation. There's always more signal to gather, more stakeholders to align, and more reasons to revisit a decision. I had to rebuild my relationship with uncertainty from scratch.
The soft skills gap was real. I could write a great spec but struggled to *sell* it. Persuading a skeptical VP, rallying a design team around a direction, navigating the politics of a roadmap review — none of that was in my engineering toolkit.
The One Skill I Wish I Had Built Earlier
Storytelling. Not in a manipulative way — in the *clarity* sense. The ability to take a messy problem space and tell a crisp, compelling story about why this matters, who it affects, and what we should do about it.
Engineers communicate in systems. PMs communicate in stories. The faster you learn to translate between the two, the smoother your transition will be.
What I'd Tell Anyone Making This Move
- Start building your user empathy muscle now. Talk to customers in your current role even if it's not your job.
- Document the decisions you influence, not just the ones you make. That's your PM portfolio.
- Find a PM who will let you shadow them. Two weeks of observation is worth months of reading.
The transition is absolutely worth it. But go in with clear eyes.
3 Comments
This breakdown is exactly what I needed heading into my Google loop next week. The CIRCLES method always felt a bit mechanical to me — your framing around trade-offs makes it feel much more natural.
The part about not jumping to solutions before defining the problem — I messed this up in my first Meta screen. Wish I'd read this before. Saving for my next prep cycle.
Great writeup. One thing I'd add: interviewers at top companies often care as much about how you react to pushback as the answer itself. Would love a follow-up post on handling live objections.
Share your thoughts on this article…
Sign in or register to comment