Developer Career Pivot Stories I've Collected

Why I'm Suddenly Writing About This

A friend of mine switched to PM last month. He was a 4-year backend developer who one day said "I just don't enjoy writing code anymore." Hearing that made me look around, and I realized quite a few developers in my circle had changed careers in the past two years. I gathered six stories.

Case 1: Minsu, Backend to PM

The friend I just mentioned. Two months into the switch. His salary dropped by about $3,500 annually. He'd heard "PMs with dev experience have an edge," but reality was back-to-back meetings. Six meetings a day. A kind of fatigue he never felt while coding. (But when I asked "do you want to go back?" he said no.)

Instead of code reviews, he now reviews planning docs. Since he can make technical judgments, the engineers trust him as a PM. That part is definitely a strength, he said.

Case 2: Yejin, Frontend to Designer

This one's unusual. She was a 3-year frontend developer who was always more interested in UI/UX. She quit and spent six months self-studying Figma. Built a portfolio and joined a startup as a junior designer.

Her salary dropped by about $8,500. Basically started over as a newcomer. "Do you regret it?" I asked. "Not every day, but a little on payday." (Points for honesty.)

But having frontend experience means she can immediately judge design feasibility when building design systems. That turned out to be a bigger competitive advantage than expected.

Case 3: Taeho, Developer to Dev YouTuber

23,000 subscribers. Monthly revenue from ads plus courses is "less than my old salary" -- he wouldn't give me exact numbers. Eight months since quitting, and he loves the freedom but the income instability stresses him out.

He posts two videos a week, handling planning, filming, and editing alone. Twelve-hour days aren't unusual. "If you think it's cushier than a job, you're dead wrong," he emphasized.

Case 4: Junghoon, Fullstack to DevOps

Switched within the same company. No salary change. He'd been self-studying Kubernetes and ended up leading an internal infrastructure migration project, which became his springboard.

"I found designing systems more fun than writing code," was his reason. But then on-call happened. Getting alerts at 3 AM still hasn't grown on him. Averages 2.7 times a month, he says. (Not sure what the 0.7 means, but that's what he told me.)

Case 5: Subin, Startup CTO Back to Regular Developer

This one stuck with me the most. Became a startup CTO at year seven, then after two years concluded "I'm an engineer, not a manager" and took a senior developer role at a large corporation. Salary actually went up.

"The CTO title looks glamorous, but I was coding less than 3 hours a week," she said. The rest was hiring, meetings, schedule management. That just wasn't the career she wanted.

Case 6: Me, Still Figuring It Out

Truth is, I had a reason for writing this. I think about it too. Five years in, wondering if I should keep coding indefinitely. PM sounds interesting. Technical writing sounds interesting. But actually making the jump is scary.

Listening to all six stories, one common thread emerged: anyone can make the switch, but you'll have to give something up along the way -- salary, stability, something. Whether you can stomach that tradeoff is really the core question.

"The perfect timing" didn't exist. Four out of six said "I just went for it."