The MBA who went back to engineering

A composite story drawn from several user journeys. Names and details have been changed.

Priya was in a hotel bar in Houston, drinking a flat Diet Coke at 11pm on a Wednesday, listening to a partner explain to the client why the model they'd built needed to be redone. She was 31, four years into a consulting career at a top firm, two years past a $190,000 MBA at a top-10 school, and she was thinking about her first job — a software engineer at a mid-size e-commerce company — for the first time in years.

She'd been thinking about it a lot, lately.

The setup

Priya's career looked perfect on LinkedIn. CS undergrad, three years as a software engineer, MBA at a brand-name school, two years at a tier-one consulting firm. She was on track to make senior manager within 18 months, partner by 36. Her base was $175,000, bonus took her to $235,000, and her profile was the kind that got recruiter inmail several times a week.

She also hadn't opened a code editor in three years. Her work was 80% PowerPoint, 15% Excel, and 5% actual thinking. The consulting work wasn't bad work — it was, technically, fine work. It just wasn't interesting to her.

The bigger problem was quieter. She didn't like who she was becoming. She'd noticed herself talking the way partners talked in meetings: hedging, reframing, repositioning. She'd gotten good at it. That was part of what scared her.

The turning point

The turning point was a conversation with her younger brother, who was an engineer at a startup.

He was describing a bug he'd fixed — something with a cache invalidation race condition — and she realized, listening to him, that she was jealous. She didn't want his job exactly. She wanted the texture of his day. She wanted to make something that either worked or didn't work, and to know which one it was by the end of the week.

She went home that weekend and opened her old GitHub. She hadn't pushed code in 41 months.

What she did

Month 1 (Apr 2025): She gave herself a test. Could she still code? She spent four weekends rebuilding a side project she'd abandoned in 2022 — a small app that tracked the books she read. She got it working. It took her twice as long as it would have three years ago, but she got it working.

She was pleasantly surprised at how much came back. She was unpleasantly surprised at how much had changed in the tooling.

Month 2 (May 2025): She told her husband she was considering going back to engineering. She did not tell anyone at work. She spent two weekends reading engineering blog posts from companies she admired and making a list of the kinds of problems that still excited her: infrastructure, data systems, developer tools.

Month 3 (Jun 2025): She started a small refresher plan. Two hours a night, four nights a week. She worked through a distributed systems course she'd abandoned in grad school. She built a toy rate limiter. She built a toy key-value store. She reread Designing Data-Intensive Applications.

Month 4 (Jul 2025): She did her first technical interview — not for a job, just to see. A friend at a FAANG-tier company offered to run her through a mock loop. She did badly. Her system design was rusty and her LeetCode reflexes were gone. She wrote down every question she missed and made a list.

Month 5 (Aug 2025): She kept grinding. She told herself she'd apply in September if she could pass two more mocks.

She passed them in late August. She started applying September 3.

Month 6 (Sep 2025): Here the math got scary. She started getting interviews — her CS degree, despite being old, still screened her through. But the salary bands were jarring. Senior engineer roles she was qualified for were paying $180,000–$220,000 base in her market. Staff-level roles, which she wasn't quite qualified for yet, paid more.

She was looking at a real pay cut. Between her consulting bonus and her likely signing loss, something like $50,000 year one.

Month 7 (Oct 2025): She had three offers. She picked a senior engineer role at a mid-size company building developer infrastructure. Base of $195,000, equity, and — importantly — a manager who agreed in writing that she'd be evaluated for staff promotion at the one-year mark.

She gave notice at the consulting firm the first week of November. Her partner mentor told her, with real regret, that she was making a mistake.

What worked

Testing herself privately before telling anyone worked. She spent four months confirming it wasn't a mood before she acted on it.

Being honest about the skill gap worked. She didn't try to interview for staff roles she wasn't ready for. She took a senior role and bet on herself to promote up.

Having the MBA and the consulting experience on her CV actually helped. Hiring managers liked the mix. Several told her they wanted engineers who could talk to customers, and she walked in with the ability to do that already proven.

What didn't

Leetcode grinding in isolation didn't work for her. After two weeks of daily grinding, her scores weren't improving. What worked was alternating hard problems with actual project work — she needed the reward of something running on her screen.

She almost took one offer that would have paid $30,000 more because she was afraid of the pay cut. In the final round of conversations, she noticed the manager never asked her a single question about what she wanted to build. She turned it down. It was the right call.

Telling her consulting peers too early would have been a mistake. She told one person "in confidence" in month three; it was back to her staffing manager within a week. The staffing manager was gracious about it, but she was off the most interesting project the next cycle.

Where she is now

Priya is 10 months into the engineering role. She was promoted to staff engineer last month, two months early. Her total comp is now roughly equivalent to what she made consulting, though it took a year to claw back.

She works on distributed storage systems. She is, in her own words, happier at work than she's been in five years.

She still uses her MBA and her consulting skills constantly. She runs her team's planning processes. She's the person who writes the strategy docs. Her engineering director has told her she's the best communicator on the team. None of that came from the MBA directly — but none of it would have developed without those four years.

The takeaway

Going "backward" is a frame, not a fact.

Priya's path, measured in titles, looks like a step down. Measured in salary year one, it was. Measured in the rest of her life — her work, her health, the thing she thinks about when she's in the shower — it was a clear step forward.

If you're in a career that everyone calls prestigious and you're not sure you want it anymore, the hardest part isn't doing the thing. It's being willing to look like the person who walked away. That part takes practice. Priya said it took her about six months to stop flinching when old classmates asked what she was up to.

The right question isn't "am I throwing away the last five years." It's "am I throwing away the next fifteen."