“I moved from engineering into product by sitting in the middle layer between our CEO, who led product early on, and our CTO, who built the technical stack. I spent 80% of my time executing across roles like engineer, designer, and user researcher, and 20% learning from my team, newsletters, and friends in product.”
“The hardest part of moving from engineering to product is realizing your job is no longer to be right about the solution, but to be right about the problem the team should solve.”
“I moved from engineering into product and for the first three months I genuinely thought I sucked. I wanted to go back to engineering every day, because the puzzle-solving high is real, but product gives you breadth and impact you can't get writing code alone.”
“I moved from engineering into product at Amazon on the Kindle team, and the shift was less about losing technical depth and more about owning the why before the how. My engineering background became leverage only once I stopped needing to be the smartest person in the room on implementation and started being the person who could translate customer pain into a decision the team could rally behind.”
“I moved from CS at IIT Kanpur into PM by taking the Bixby AI role at Samsung Korea, where my engineering background helped me ship features but I had to stop optimizing code and start optimizing decisions. The shift is less about losing technical depth and more about trading does it work for should we build it.”
“The hardest part is learning to live with decisions you can't prove are right. Engineering trained me to optimize for correctness; product management forced me to optimize for judgment under uncertainty, with sales, support, and engineering all pulling in different directions.”
“I moved from engineering to product at Juno because I loved figuring out what to build more than how to build it, and that early role had no PM so I did product, design, biz dev, and code all at once. Engineering gave me fluency in tradeoffs and team empathy, but I now believe design, marketing, and analytics are equally valid paths into product.”
“I was an engineer for 10 years before jumping to product, and the biggest cost was losing the clarity of did the code work or not. Product gives you none of that clean signal, just ambiguity and tradeoffs you help others navigate, which is either thrilling or miserable depending on why you're switching.”
“I came into product from frontend engineering, and the trap I fell into early at SurveySparrow was trying to prove I still had the technical know-how to engineers, which only made them trust me less. What actually moved me forward was when my manager told me to stop winging it and start performing the PM role before I expected the title: talk to sales, sit with customers, ship the smallest test.”