“I moved from engineering to product because I realized I loved figuring out what to build more than how to build it. Start by doing PM work before you ask for the title: write specs, run customer interviews, and own a metric your team is judged by.”
“I moved from engineering to product by building side projects, doing AI research, and documenting everything publicly until the CEOs I interviewed with already knew my name. The PMs who matter now are not the ones writing perfect PRDs; they are product thinkers who can translate a long-term intuition into strategy, roadmap, and a story people actually believe.”
“I studied engineering but never really coded, so my edge was never technical depth. It was learning to defend product calls by understanding the why behind the architecture, not the code itself. Start building small product artifacts, take the interviews even when you are not ready, and let each rejection teach you what the role actually asks.”
“I moved from engineering into PM at Samsung's Bixby AI team, and the shift only stuck once I stopped framing specs as handoffs and started writing one-pagers that engineers actually wanted to read. Your edge is that you already speak their language; use it to build trust before authority.”
“I moved from engineering to PM through Yahoo's new products team, then Yelp's experimentation group, because I wanted to own outcomes, not just output. The shift is less about learning frameworks and more about getting comfortable with ambiguity and owning the why before anyone asks.”
“I made the move from frontend engineer to product, and the thing that actually got me the title was already doing the job before I had it: talking to sales, shadowing customer calls, and shipping small things that mattered. Start there, because no one promotes you for wanting the role, only for performing it.”
“I came into product management from quantity surveying, not engineering, but the same trap waits for both of us: you already know how to ship, so people will keep asking you to ship what they already decided. I trained with Treford, then forced myself to live in the discovery phase, asking why until stakeholders got uncomfortable, because that is where the role actually starts.”
“I spent ten years as a front-end developer before moving to product in 2018, and the hardest part was letting go of the reflex to optimize solutions before I had truly validated the problem. My advice: start doing PM work before you have the title, volunteer to own discovery for a feature, run user interviews, and get comfortable saying I don't know yet.”
“I made the jump from mechanical engineering at Shenzhen Nanshan Circuit into product management, and the biggest shift was learning that being right about the tech matters less than being clear about the problem and the trade-offs. Start doing PM work before you have the title: write the spec, run the user interview, own the decision on your own team.”