The Engineer/Manager Pendulum — Charity Majors

Summary

Charity Majors rejects the idea that engineers must choose a permanent “lane” (IC or management) and argues the best technical leaders oscillate between the two. The core mental models:

1. The Pendulum Model. The best frontline engineering managers are never more than 2-3 years removed from hands-on technical work. The best individual contributors have done time in management. The best technical leaders swing back and forth — building the stack, then building the team, then managing the team, then leaving to start over. The restlessness isn’t a bug; it’s a signal that you’ve stopped learning.

2. Management is a career change, not a promotion. This reframe is critical. Moving to management is not “leveling up” — it’s switching professions entirely. You will be bad at it for a long time. The skills that made you a great engineer (deep focus, blocking interruptions, solving hard technical problems) are the opposite of what management requires (being interruptible, handing off the challenging work, developing others).

3. The “I know what I’m doing” alarm. Feeling comfortable and competent is a telltale sign something is wrong. It means you’ve stopped growing. The pendulum swings when the discomfort of staying exceeds the discomfort of switching.

4. Hand off the hard problems. As a manager, your job is to give away the most challenging assignments so your engineers can grow. This is the opposite of what made you successful as an IC. The identity shift is brutal: you go from “the person who solves the hardest problems” to “the person who ensures others can solve them.”

Relevance

• 01-projects/phdata/career-transition — This is the most directly relevant framework. The career transition question isn’t “IC or manager?” — it’s “where am I on the pendulum, and when does it need to swing?” If you’ve been deep in IC work, the next growth edge might be management (or vice versa). The discomfort of the switch IS the value.
• SOUL.md — The AI COO is an attempt to have management-layer execution without swinging the pendulum. Ray stays in the Entrepreneur/IC zone while the agent handles Manager-layer coordination. But Majors would say: you still need to understand management deeply to delegate it effectively. The pendulum insight says the delegation only works if Ray has done enough management reps to know what good looks like.
• 06-reference/2026-04-03-the-e-myth-revisited — Gerber’s Technician trap is what happens when someone refuses to swing the pendulum. They stay in the IC role forever because that’s where they’re comfortable, and the business suffers. Majors’s version: the org suffers because the manager never goes back to being an IC and loses touch with the work.
• 06-reference/2026-04-03-company-of-one — In a company of one, you ARE the pendulum. You swing between building and managing every day, sometimes every hour. The question is whether you do it consciously (Majors) or unconsciously (Gerber’s Technician).
• 06-reference/2026-04-03-part-time-creator-manifesto — The day job might be one side of the pendulum (e.g., IC engineering), while the side hustle is the other (manager/operator of your own thing). The part-time creator is living the pendulum in parallel rather than serial.
• 06-reference/2026-04-03-ladders-of-wealth-creation — Moving from Ladder 2 (freelancing) to Ladder 3 (productized services) requires a pendulum swing from “doing the work” to “managing the system that does the work.”

Open Questions

• Where is Ray currently on the pendulum? Has it been too long on one side?
• The “I know what I’m doing” alarm: which current activities feel too comfortable? Where has the learning curve flattened?
• Is the AI COO setup creating a false sense of management coverage? Does Ray still need direct management reps to grow as a leader?
• How does the pendulum model apply to the team-of-one scenario? Can you get the benefits of the management swing through managing projects/systems rather than people?