Auto Apply to hundreds of jobs in a few hours

Español

日本語

Engineering manager skills: what to learn first, and what can wait

Your technical skills got you considered. They won't carry the job, because the work now is people, plans and the system your team runs inside. Learn the weekly mechanics of managing first, and leave org design and budget fights for later.

4,064 open jobs

Step one

Gets you the interview

One-on-ones that surface real problemsKeep a shared running doc per report in Notion or Google Docs, let them set the agenda, and save a slot for career talk. Screeners ask how you run them. An answer about status updates tells them you've never actually done it.

Structured hiring loopsWrite the role's scorecard before the first interview, give each interviewer one signal to probe, and run a debrief where people submit feedback in Greenhouse or Lever before they talk. Managers who hire well get hired, and this is the easiest part of the job to prove.

Enough technical depth to judge a designYou don't write the code, but you have to spot when a plan skips the data migration or ignores the on-call cost. Most loops include a system design round for managers, and people who've gone soft on architecture fail it.

Sprint and quarterly planning with productTurn a product manager's roadmap into a plan that fits your team's actual capacity, with room for on-call, bugs and debt. Bring a real example of cutting scope before the quarter started, not halfway through.

Step two

Gets you the offer

Handling an underperformerName the gap early and in writing, agree on what good looks like, check in weekly, and loop in HR before it becomes a formal performance improvement plan. Final rounds nearly always include this scenario, and hesitation is what they're listening for.

Writing reviews and surviving calibrationTie each rating to the career ladder and to specific work, like the design doc or the incident someone ran. In calibration you'll defend those ratings against other managers, so vague praise won't hold up.

Reading delivery metrics without gaming themKnow the DORA metrics, cycle time and deploy frequency, and pull them from tools like LinearB, Jellyfish or your own Jira dashboards. Interviewers want someone who uses numbers to find a blocked review queue, not to rank engineers.

Owning the on-call rotation's healthWatch pager load in PagerDuty or Opsgenie, make sure postmortem follow-ups actually get scheduled, and move people off a rotation that's burning them. A tech lead runs the incident. You make sure the same one doesn't keep waking the same person.

Step three

Gets you promoted

Headcount and budget planningMake the case for a new hire in terms of the roadmap it unblocks, and know the cost of contractors versus full-time staff. Directors spend much of the year on this, so doing it well at manager level is the clearest signal you're ready.

Team topology and reorgsDecide where team boundaries sit so each group owns services it can change without waiting on others. Team Topologies is the book most people reach for. Managing a split or merge without losing people is a promotion story on its own.

Growing a manager under youHand a senior engineer a small team, coach them through their first tough review, and let them own their own hiring. You can't run a larger group until someone else can run part of it.

Writing for executivesA one-page update with the decision you need, the risk and the options, written so a VP can answer it between meetings. Managers who write this way get pulled into bigger conversations.

Certificates worth your time

Certificate	Best for	Effort	Worth it?
Professional Scrum Master I (PSM I)	Managers of teams that run Scrum without a dedicated scrum master	a week or two of reading the Scrum Guide and taking practice tests	Cheap and fast, and it shows you know the ceremonies. Nobody hires a manager because of it, so treat it as a small extra.
Project Management Professional (PMP)	Managers in large enterprises or government work where delivery follows formal project controls	a couple of months of evening study, plus logged project experience before you can sit the exam	Skip it for most software teams. It only earns its cost where postings list it by name.

Eligibility rules, exam fees and renewal requirements change, so check the details on the provider's own certification page before you pay.

Put it on your résumé like this

Weak

Managed a team of software engineers and handled hiring, performance reviews and project delivery.

Strong

Managed 9 engineers across 2 teams, hired 5 through a rebuilt scorecard loop with 0 regretted leavers in 18 months, and cut median cycle time from 6 days to 2 by splitting a shared deploy pipeline.

Questions people ask

Which engineering manager skill should I learn first?

One-on-ones. You'll run them every week from your first week, they're where most problems show up first, and you can practise them now by mentoring someone on your current team. Everything else builds on knowing what your people actually think.

How much do I need to keep coding as an engineering manager?

Enough to read a pull request and judge a design, not enough to own features. If your team waits on your code, you've become a bottleneck. Some managers keep a small internal tool or fix bugs on quiet weeks to stay sharp.

Can I learn management skills before I have the title?

Most of them, yes. Sit on hiring loops, run a retro, mentor a new hire, and ask your manager to let you draft a quarterly plan. Performance reviews and compensation are the parts you'll only learn on the job.

What do engineering manager interviews test that tech lead interviews don't?

People scenarios. Expect questions on firing, low performers, conflict between senior engineers and pushing back on your own boss. Tech lead loops lean on design and code, while manager loops give those a smaller share.

Got step one? Start applying. HeroApply matches you to roles that fit.

Start your trial