It’s 10:15 AM. A senior developer is stuck on a database bottleneck. A Product Manager wants one more feature in Friday’s release. A junior engineer has just asked for five minutes to talk about their career.
All three requests land on the desk of an Engineering Manager.
The title sounds contradictory: how do you manage engineers, and do you still engineer? An EM sits at the intersection of people, product, and technology. A traditional manager focuses on schedules, and a Tech Lead focuses on architecture. The EM’s job is to keep the team’s priorities clear, its work unblocked, and its people growing. They don’t need to be the best coder in the room.
If you are an engineer wondering whether this is your next step, this guide covers what the job involves, how it differs from the Tech Lead path, what research says makes managers effective, and how to test the move before you commit to it.
From Maker to Multiplier
Most EMs started as engineers, where success meant merged pull requests, fixed bugs, and shipped features. As an individual contributor (IC), your impact grows in proportion to your output. As an EM, your impact comes from what the team achieves. You stop solving the hard problem yourself and instead make sure the people who do have clear priorities, context, and time.
That changes how you rank your own work. Gergely Orosz, who wrote about his own move into management in The Pragmatic Engineer, describes the new order of priorities as the company first, then the team, then the individual people on it, and only then yourself. For an engineer who has spent years putting their own technical output first, that reversal is the hardest part of the transition.
The Four Pillars of the EM Role
Every company draws the job slightly differently, but the work usually falls into four areas.
1. People Leadership and Growth
This is the core of the job, and the part most new managers underestimate.
- Meaningful 1-on-1s. These are not status updates, because the tracker already has those. Use the time to gauge morale, spot burnout early, and learn what motivates each person.
- Career coaching. Help a mid-level engineer understand what Senior looks like at your company, or help someone choose between the architecture and management tracks.
- Feedback. Give it early, specific, and in private when it is critical. Waiting for the review cycle means the person hears about a problem months after it could have been fixed.
- Psychological safety. Engineers should be able to say “I don’t know,” “I broke production,” or “I disagree” without fear of blame.
2. Delivery and Execution
- Unblocking. Get the API credentials, clarify vague requirements, and absorb organizational friction on the team’s behalf.
- Protecting the pace. Push back on unrealistic deadlines, and don’t let tech debt pile up just to hit short-term targets.
- Process tuning. Cut pointless meetings and improve code review and workflows. Change one thing at a time and ask the team whether it helped.
- Predictability. Stakeholders rarely need the fastest team. They need a team that says what it will deliver and then does it, or says early when plans change.
3. Technical Strategy and Credibility
EMs write little code, and an EM who is the bottleneck on a release is often a sign the team is short on people or ownership. They still need enough technical depth to:
- Ask the right questions: “How does this scale?”, “What if this dependency goes down?”, “Are we over-engineering?”
- Balance tech debt against features by working with Tech Leads on refactoring, security, and infrastructure health.
- Judge risk. You do not need to write the migration, but you do need to know when a plan is too fragile to commit to a date.
4. Cross-Functional Alignment
- Translate in both directions. Explain why a business goal matters to engineers, and turn technical constraints into clear trade-offs for stakeholders.
- Manage in three directions. David Loftesness, in a First Round Review piece on new engineering managers, describes managing up to your boss, across to peers, and down to your team. New EMs often focus only on the last one.
- Hire and build the team. Identify skill gaps, interview candidates, and shape the team’s culture.
EM vs. Tech Lead
| Tech Lead | Engineering Manager | |
|---|---|---|
| Focus | Architecture, code quality, technical execution | People growth, team health, delivery predictability, alignment |
| Key question | Are we building it the right way? | Are we building the right things, and is the team thriving? |
| Career track | IC (Staff / Principal Engineer) | Management (often leading to Director / VP of Engineering) |
| Typical day | Coding, PR reviews, system design | 1-on-1s, roadmap planning, hiring, stakeholder syncs |
In small startups, one person often does both jobs, which is why the role can feel so intense.
If you love design discussions and want to keep building, the Tech Lead and Staff Engineer path may suit you better. If you find that the parts of your week you enjoy most are mentoring, clarifying goals, and removing obstacles for others, management is worth a serious look.
What Makes a Good Engineering Manager
Google ran an internal study called Project Oxygen to find out what its best managers did differently. The list started with eight behaviors and grew to ten in 2018. As summarized by Parabol, a great manager:
- Is a good coach
- Empowers the team and does not micromanage
- Creates an inclusive team environment, showing concern for success and well-being
- Is productive and results-oriented
- Is a good communicator who listens and shares information
- Supports career development and discusses performance
- Has a clear vision and strategy for the team
- Has key technical skills to help advise the team
- Collaborates across the company
- Is a strong decision maker
Look at where technical skill lands: eighth. Coaching comes first. This does not mean technical depth is irrelevant, since it is still on the list. It means that if you are choosing between investing in another framework and investing in how you give feedback, the research points to feedback.
Skills to Build Before You Become an EM
You do not need the title to start practicing. These habits build the muscles the job relies on:
- Mentor someone. Pair with a junior engineer, review their work kindly, and notice how you explain things.
- Lead a project end to end. Write the plan, track the risks, communicate status, and handle the moment when scope changes.
- Practice written communication. Design docs, project updates, and clear PR descriptions are the same skills you will use to align a team.
- Run a meeting well. Set an agenda, make sure quieter people are heard, and end with owners and dates.
- Ask for feedback on your feedback. Ask a peer how your code review comments land. It is a safe way to learn how you come across.
- Learn how your company makes decisions. Who sets priorities, how are budgets decided, and how does your team get headcount? New managers are often surprised by how much of the job is navigating this.
Mistakes First-Time Managers Make
- Keeping one foot in the code. Charity Majors, writing about the engineer/manager pendulum, argues that engineering and management need opposite mindsets: one needs long uninterrupted focus, the other needs constant availability. Trying to do both tends to short-change your team and your own work.
- Treating management as a promotion. She warns that the biggest risk is seeing it as a step up instead of a different job. Engineers who move for status or pay alone can end up resenting the work.
- Skipping your own goals. Orosz notes he nearly forgot to set personal development goals, because he was focused on his team’s. Ask your manager for a mentor and for regular, candid feedback.
- Letting the calendar fill by default. Managers get far more meetings than ICs. Block time for 1-on-1s, for thinking, and for protecting your team from interruptions.
- Expecting to feel productive. Majors says to expect being exhausted without much visible output at first. The work is real, but it does not show up as a merged PR.
A 90-Day Plan for Your First Quarter
Loftesness suggests splitting your first three months into phases:
- Days 1-30: own your education. Study management, find mentors, and block time to read and learn. Meet every person on the team and listen more than you fix.
- Days 31-60: find your rhythm. Build a sustainable calendar, set up your 1-on-1s, and establish how and when you communicate with the team and stakeholders.
- Days 61-90: assess. Check whether you can describe each person’s strengths and goals, whether the team is delivering, and whether you are still interested in the job.
Decide Before You Commit
Majors makes the case that moving between engineering and management is a legitimate career pattern, not a failure. Loftesness’s advice is similar: if the role does not work for you after your first quarter, stepping back to IC is acceptable. Before you say yes:
- Ask whether you can try the role with a clear path back, such as a trial period or a team-lead stint.
- Ask your own manager what they would expect from you in the first six months.
- Talk to two or three EMs at your company about what a bad week looks like, not only a good one.
- Be honest about your reason. If it is only salary or title, consider whether a Staff Engineer path gets you there without the day-to-day work of managing people.
Which Hat Do You Wear Most?
Look at last week’s calendar. If you aren’t an EM yet, picture the calendar you’d expect to have. Where does most of the time go?
- Coach: mentoring, feedback, career conversations
- Firefighter: outages, escalations, urgent blockers
- Strategist: roadmaps, hiring, cross-team alignment
- Builder: code reviews and architecture
There’s no ideal ratio, because it shifts with your team’s stage. What matters is noticing which hat dominates and whether that’s the one the team needs right now.
Why the Role Matters More in the AI Era
AI tools can now generate boilerplate in seconds, so typing code is a smaller share of the effort. Deciding what to build, keeping people aligned, reviewing generated code with good judgment, and keeping a team motivated still take people, and that is the EM’s work.
FAQ
Do Engineering Managers still code? Rarely. They may review designs or PRs, but their main output is team effectiveness.
How do you become an Engineering Manager? Many EMs move up from senior engineer or Tech Lead roles, though paths vary by company. Common steps are mentoring others, leading projects, and working well across teams.
Can I go back to being an engineer? Yes. Many people move between the two tracks, and the experience of each makes you better at the other.
Sources
- Things I’ve learned transitioning from engineer to engineering manager, The Pragmatic Engineer
- This 90-day plan turns engineers into remarkable managers, First Round Review
- The engineer/manager pendulum, Charity Majors
- Google Project Oxygen: the behaviors of great managers, Parabol