What Does an Engineering Manager Actually Do? Plain Definition
The most common myth in our industry: an Engineering Manager is a senior developer who got admin rights in GitHub and the authority to approve pull requests on Fridays. Two reasons that's wrong. First, the median EM on the 100+ B2B teams we measure writes code for roughly 18 minutes per day, and that's the healthy number. Second, the highest-leverage thing an EM does has nothing to do with the IDE. It's the conversation that prevents a senior from quitting. The spec rewrite that saves a quarter. The hiring loop that finds an engineer one level above what the team thought it could afford. Will Larson, who built engineering at Stripe, Calm, and Carta, puts it bluntly in An Elegant Puzzle: an EM's job is to make the team output more than the sum of its parts. You cannot do that with your hands on a keyboard.
This is a plain-language definition. Who an EM is, what they do during a week, how the role differs from Tech Lead, the path from senior engineer, and how to measure whether one is doing the job well.