Developers Who Became PMs: Their Stories

I Got Offered the PM Track

My team lead asked during our 1:1: "Have you thought about transitioning to PM?" Caught me off guard. I'm a developer because I enjoy writing code. Why would I go into product management? But part of me was curious. What's it actually like for people who made the switch?

So I bought coffee for three developer-turned-PMs I knew and asked them.

"My Coding Hours Turned Into Meetings"

First person, Minsu (not his real name). Four years as a frontend developer, then switched to PM. He's been at it for a year and a half. First thing he said: "There are so many meetings." An average of 4.7 meetings per day. (He actually counted.) As a developer, he had 1-2 meetings a day. As a PM, his calendar has no empty slots.

But he said the number of meetings isn't what bothers him. The problem is that so many of those meetings require him to make decisions. As a developer, he only made technical decisions. As a PM, he makes business decisions, priority decisions, resource allocation decisions. "Decision fatigue is real," he said.

"Dev Experience Helps But Isn't Enough"

Second person, Jieun. Three years as a backend developer before switching to PM. She assumed her technical background would give her an edge in technical judgment. Reality was different. Knowing too much technical detail as a PM actually leads to micromanaging.

Saying things like "Why aren't you using Redis caching here?" in meetings makes developers feel like they're being critiqued by a senior dev, not guided by a PM. It took Jieun 6 months to break that habit. (I was honestly scared I'd make the same mistake.)

What actually matters for a PM isn't technical knowledge but the ability to articulate "why we need to build this feature." That's a skill developers almost never practice.

"Pay Went Up But the Satisfaction Is Different"

Third person, Hyunwoo. Five years full-stack, then PM. His salary jumped 15% on transition. PMs tend to have wider salary bands. But the type of satisfaction is completely different.

As a developer, writing code, deploying, seeing users interact with it, that was satisfying. As a PM, satisfaction comes from hitting quarterly OKRs, which doesn't have the same immediate rush as a deployment. He called it "delayed gratification." Three months of waiting before seeing results.

The hardest part for Hyunwoo was feeling like "I didn't make anything today." PMs attend meetings, write documents, coordinate. At the end of the day, it's easy to think "what did I even do?" Developers at least have commit logs. (That one hit home.)

But I Decided Not to Switch

After hearing all three, my conclusion was that PM isn't for me. The reason is simple. I love the flow state of coding. Three hours of nothing but code, completely in the zone. PMs rarely get that opportunity. There's a meeting every 30 minutes, Slack pings constantly, decisions need to be made.

This isn't a knock on PM as a role. Minsu said "PM is my calling." Different things suit different people. But the assumed progression of "developer then PM" being treated as the default path is problematic. Senior developer, staff engineer, architect, these technical tracks are equally valid career paths.

I told my team lead, "I'll pass on PM, but I'm interested in the staff engineer track." The response was positive.