Think Twice About Management

A former Apple manager published a personal account saying she preferred being an individual contributor and burned out after becoming a manager, ultimately taking a career break at 30 with no regrets. The piece frames management not as the natural next step but as a role change that trades coding for people-ops, alignment work and emotional labor. That anecdory is a useful counterpoint for engineers considering promotion without testing the role first. (businessinsider.com)

A former Apple manager wrote that she hit 30, left the job, and took a career break after learning the promotion she chased had turned her from a builder into a full-time people coordinator. She said she had “no regrets” about stepping away after burning out in management. (businessinsider.com) That story lands because tech still treats management like the default prize after senior engineer, even though the job changes almost completely once you cross that line. You stop being measured mainly on code you ship and start being measured on hiring, feedback, planning, conflict, and keeping teams aligned. (leaddev.com, staffeng.com) A lot of engineers do not discover that difference until after the promotion, because titles make the move sound like “more senior engineer” instead of “different profession.” LeadDev describes the jump from individual contributor to engineering manager as one of the biggest transitions in a tech career, not a routine level-up. (leaddev.com) The work itself also shifts from concrete output to invisible maintenance. A manager can spend a day in one-on-ones, performance reviews, hiring loops, roadmap meetings, and cross-team negotiations and still have nothing tangible to point to except a calmer team and fewer blocked decisions. (leaddev.com, hbr.org) That invisible load is one reason managers burn out so often. Harvard Business Review reported in 2023 that more than 50% of managers said they felt burned out, and Gallup reported this year that 97% of managers had taken on individual-contributor work outside their leadership role. (hbr.org, africa.businessinsider.com) The squeeze is structural, not just personal. Middle managers have to translate strategy from executives above them while coaching employees below them, and Harvard Business Review has described that constant switching between high-power and low-power situations as cognitively and emotionally exhausting. (hbr.org, hbr.org) Tech companies also do have another ladder, even if it is explained less clearly. Individual contributors can keep advancing through staff engineer, principal engineer, or distinguished engineer roles without taking on direct reports. (staffeng.com, leaddev.com) That matters because the old assumption was simple: if you want more scope, more pay, or more influence, you become a manager. In many companies now, senior technical roles can carry company-wide influence over architecture and strategy without requiring the daily emotional labor of people management. (leaddev.com, staffeng.com) There is also a third option that shows up again and again in engineering careers: try management, then go back. LeadDev calls this moving between manager and individual contributor roles, and Charity Majors has described it as an “engineer/manager pendulum” rather than a one-way promotion track. (leaddev.com, leaddev.com) So the Apple anecdote is not really about one person quitting at 30. It is a reminder that “manager” is not the next rung on the same ladder for engineers; it is a job swap, and a lot of people would make a different choice if companies described it that way from the start. (businessinsider.com, leaddev.com)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.