An engineering manager (EM) is the person responsible for a team of engineers: hiring them, growing them, keeping the team healthy and making sure it delivers what it promised. EMs stay technically credible, but most of their week goes to people and planning rather than writing code. In most companies it is a separate career track from senior and staff engineering, so moving into it is a change of job, not a promotion.
This guide covers what the job looks like day to day, how it compares to tech lead and staff roles, how engineers usually make the switch, what the interview loop contains, and what the pay data says. Every number links to its source.
What an engineering manager does
GitLab publishes one of the clearest public descriptions of the role. Its Engineering Manager job family page says EMs "see their team as their product". They know the details of what engineers work on, but their time goes to the team's health, to hiring and to putting people in a position to succeed. They also own the delivery of product commitments.
The responsibilities GitLab lists for the role (accessed 2026-11-13) are concrete:
- manage a team of engineers and help them grow their skills
- hold regular 1:1s with every team member and give clear feedback on performance
- write project plans and run the team's agile process
- hire, run managerial interviews, and train the team to do technical interviews
- foster technical decision making on the team, and make the final call when needed
- draft quarterly OKRs and engineering KPIs
- improve quality, security and performance
- take part in the incident on-call rotation
Count the items: most of the list is people and coordination. The technical part is still there, but it shows up as coaching, code review and architecture guidance rather than shipping features yourself. GitLab even suggests EMs keep empathy for the team by doing code reviews or working on non-critical bugs, which tells you how much hands-on coding the role normally leaves room for.
Published career ladders tell the same story. The ladders from Kickstarter and Rent the Runway, collected in swyx's list of public engineering ladders, put architecture, hiring, organisation and leadership skills into the management track. Dropbox publishes level pages with detailed expectations for each management level in its career framework.
IC track vs manager track
Many companies run two parallel ladders after senior engineer. One is technical leadership as an individual contributor (IC): staff, principal and above. The other is management: engineering manager, senior manager, director. StaffEng describes the split this way: staff-plus engineers typically have no people management duties, while their EM and director counterparts spend a large share of their time on people.
Dropbox makes the parallel structure explicit. Its framework runs the IC track from IC1 to IC7 and the management track from M3 (Engineering Manager) to M7 (Senior Engineering Director), side by side (Dropbox career framework overview).
Two things follow from that:
- Management is not the only way up. A staff engineer can have the same seniority as a manager without any direct reports.
- The skills that got you promoted as an IC are not the skills you will be judged on as an EM. Dropbox's promotion principles say promotion needs "demonstrated, sustained impact at the next level". For an EM, that impact is measured through the team.
A common way to decide is to look at what gives you energy. If deep architecture work is what you look forward to, the staff track is probably a better fit. If running 1:1s, hiring and untangling team problems is the part you enjoy, management is worth trying. That is a rule of thumb, not research, but it is a useful first question.
Engineering manager vs tech lead
People mix these two up, partly because one person sometimes does both jobs.
A tech lead guides the technical approach and execution of a team, or a cluster of teams. They coordinate the work, remove blockers and keep relationships with other teams going. Will Larson describes tech lead as the most common of the four staff engineer archetypes (tech lead, architect, solver, right hand). In other words, tech lead is usually a role an IC plays, not a management position.
An engineering manager owns the people side: hiring, performance, 1:1s, growth and team health, plus accountability for delivery.
| Tech lead | Engineering manager | |
|---|---|---|
| Main focus | Technical direction and execution | People, team health, delivery |
| Direct reports | Usually none | Yes |
| Track | IC (often a staff archetype) | Management |
| Typical outputs | Design decisions, technical plans, unblocked work | Hires, feedback, growth plans, project plans, OKRs |
| Writes code | Regularly | Occasionally, off the critical path |
Some companies also have a tech lead manager (TLM) role that mixes both. If your company has it, it is a practical way to test management before you commit.
How to move from senior engineer or tech lead to EM
GitLab's job family shows the usual entry point: the level listed right before Engineering Manager is senior frontend, backend or fullstack engineer. Its requirements include "demonstrated progressive experience in a leadership role with current technical experience" and excellent written and verbal communication (GitLab).
So the move is about collecting leadership evidence while you are still an IC. Things you can start doing now:
- Mentor people on purpose. Pair with juniors, explain your code review comments, help someone get promoted.
- Join the hiring loop. Interview candidates and write structured feedback.
- Own delivery for one project. Write the plan, track it, report status to stakeholders and deal with the slips.
- Write planning documents. Design docs and project plans show you can think at team level.
- Step into conflict. When people disagree about scope or approach, get them to a decision.
Then tell your manager you want to try management. Ask whether a TLM role, or covering for a manager on leave, is possible. My view: an internal move is the easier first step, because your current company has already watched you lead and does not have to take your word for it.
Expect the feedback loop to get slower. As an IC you see a merged PR the same day. As an EM your output is the team's output, and it shows up over weeks.
What engineering manager interviews look like
EM loops vary by company, but GitLab publishes its process for the role. Candidates go through (GitLab):
- a 30 minute screening call with a recruiter
- a 60 minute interview with the hiring manager
- a 60 minute peer interview with another engineering manager
- possibly a 60 minute interview with a product manager
- possibly a 60 minute interview with a senior leader in the department
Notice who is in the room: managers, a product manager, leadership. Engineering loops at big tech look different. They usually include coding, fundamentals, system design and a behavioural round, and behavioural weight grows with seniority and drives leveling (GreatFrontEnd). For EM candidates the behavioural and people part becomes the core of the loop, though many companies still check technical judgment.
A practical way to prepare: take each responsibility from the job description and have one real story for it. Based on GitLab's list, that means stories about:
- a hire you made or helped make, and how you assessed the candidate
- a 1:1 that changed something for a team member
- giving hard feedback about performance
- a project plan that slipped and what you did about it
- a technical decision where the team disagreed and you had to decide
- a process you improved and how you knew it worked
Keep each story short: the situation, what you did, what happened, what you would change now. If a story has no people in it, it is probably an IC story.
Engineering manager salary
Pay data needs care, because sources measure different things.
United States. Levels.fyi shows a median total compensation of $360,000 for software engineering managers in the US, based on 3,081 salaries (page data accessed 2026-11-13). Total compensation means base salary plus stock plus bonus. For comparison, the median for all software engineers on Levels.fyi is $200,000 from 46,471 salaries.
Ukraine. The DOU summer 2026 salary survey (May to June 2026, 4,541 respondents) does not give a separate figure for engineering managers. The closest data point is the Lead+ level, with a median of $5,500 per month net of taxes. Team lead pay went down by $140 over six months, according to the dev.ua summary of the same survey. For context, the median senior developer in that survey earned $4,500.
Do not compare the two directly. DOU numbers are monthly and net of taxes. Levels.fyi numbers are yearly gross total compensation.
Is engineering management right for you?
Try a short honest check. Over the last few months, which days felt good? If they were the days you solved a hard technical problem, look at the staff track first. If they were the days a junior you helped shipped something, or a team conflict got resolved, management may suit you.
Both tracks go up a long way. They just fill your calendar with different things.
FAQ
Do engineering managers write code?
Some do, but it is not the main job. GitLab suggests its EMs stay close to the work through code reviews and non-critical bugs and features, while most of their time goes to the team's health, hiring and delivery.
Is an engineering manager higher than a senior engineer?
In ladders like GitLab's, engineering manager is the next step on the management track after senior engineer. Many companies also offer an IC path (staff, principal) that reaches the same seniority without managing people, as in Dropbox's parallel IC and M tracks.
What is the difference between a tech lead and an engineering manager?
A tech lead leads the technical work and usually has no direct reports. An engineering manager is responsible for people: hiring, feedback, growth and team health, plus delivery.
How long does it take to become an engineering manager?
There is no fixed number of years. Dropbox says promotion requires sustained impact at the next level rather than time served. In practice, most EMs come from senior or tech lead roles where they already showed leadership.
What questions are asked in engineering manager interviews?
Expect questions about hiring, 1:1s, giving feedback, handling underperformance, planning and missed deadlines, and decisions the team disagreed with. Some companies add a technical or system design conversation.
Keep your technical base strong
Managers who stay technically credible earn trust faster. ShortLesson has short, practical lessons that help you keep fundamentals fresh or prepare for interviews: start with TypeScript Essentials or React: the basics, or browse all courses.