Engineering Manager Job Description Template (With Screening Tips)

Engineering managers read job posts looking for answers to questions most posts never address: how many reports, do I still write code, who decides what the team works on, and am I being hired to build something or to absorb blame for a team in trouble. Vague management posts attract vague candidates. Specific ones attract people who have done the job.

The template

Engineering Manager at [Company]

Location: [City / Remote — [region] / Hybrid] Compensation: [$X – $Y] base, plus [equity / bonus] Reports to: [Title]

About the role

[Company] builds [product] for [users]. Engineering is [n] people across [n] teams.

We're hiring an engineering manager for [the team], which owns [the specific domain]. The team is [n] engineers today — [breakdown: n senior, n mid, n junior] — and [is growing to n / is stable / is being formed].

The honest context: [State the actual situation. "The team has been without a manager for four months." "This is a new team we're forming from two existing ones." "The team is delivering well and needs someone to help it scale."] Experienced managers will find this out in week one regardless; saying it up front earns credibility and filters for people who want that specific challenge.

What you'll do

• Lead and grow a team of [n] engineers — one-to-ones, feedback, career development, performance.
• Own delivery for [the domain]: planning, prioritisation, and being accountable for what ships.
• Partner with [product / design / other teams] on what to build and in what order.
• Hire: define roles, run loops, and close candidates. [Expected hires this year: n.]
• Improve how the team works — process, quality, on-call, and technical direction with your senior engineers.
• Represent the team's work and constraints upward and outward.

How much you'll code

[Be specific. "We expect roughly 20% hands-on — code review, prototypes, occasional fixes — but you are not on the critical path for delivery." Or "This is a fully non-coding role." Or "This is a player-coach role at roughly 50/50, and here's why."] Managers self-select hard on this line, and getting it wrong is a top cause of early departures.

What we're looking for

• [n]+ years managing engineers, including performance conversations and at least one full hiring cycle.
• A background as a practising engineer — enough to earn technical credibility and judge trade-offs.
• Evidence you've grown people: promotions, scope increases, engineers who improved under you.
• Ability to work with product and design as a genuine partner.
• Clear written communication, especially about difficult things.

Nice to have

• Experience with [your domain] or systems at [your scale].
• Having built a team from a small base, or having turned one around.
• Experience managing distributed or remote teams.

Your authority

[This section is unusual and worth including.] You'll own [hiring decisions for your team / performance ratings / technical direction with your seniors / roadmap input]. Decisions made above this role: [budget, headcount, company-level priorities]. [Be honest — managers with no authority and full accountability leave quickly.]

Interview process

1. [30 min] Intro call.
2. [60 min] Management experience: a team you grew, a performance problem you handled, a delivery failure.
3. [60 min] Technical conversation — enough depth to confirm credibility, not a coding test.
4. [60 min] Meet the team you'd manage. Their feedback carries real weight.
5. [45 min] Cross-functional partners.

Benefits and how to apply

[Benefits.] [Application link.]

[Company] is an equal opportunity employer.

Hiring managers: what's different

The three numbers candidates want

Most management posts omit all three:

• Team size and composition. Managing three juniors and managing twelve mixed-seniority engineers are different jobs.
• The coding expectation, as a percentage and a description.
• Expected hiring, because a manager hiring six people this year is doing a substantially different job from one holding steady.

Say whether this is a rescue

There's no shame in hiring a manager for a struggling team — plenty of strong candidates specifically enjoy that work. But hiding it is costly. A manager who accepts a "healthy growing team" role and arrives to attrition, a burned-out staff engineer, and a stalled roadmap will feel misled, and they'll be right.

Frame it as the challenge it is: "The team has had three managers in two years and morale is low. We want someone who can stabilise it. Here's the support you'd have."

Let the team interview them

Have candidates meet the engineers they'd manage, and take that feedback seriously. It's the closest simulation available of the actual job, and engineers detect condescension, vagueness, and empty process talk faster than any panel.

Screen for judgment, not vocabulary

Management interviews are unusually easy to perform in. Everyone can describe a growth mindset. Push for specifics:

• "Tell me about an underperformer you managed. What happened?" Listen for early, direct intervention and a real outcome — including the case where it ended in an exit, handled decently.
• "Describe someone you promoted. What did you do to get them there?" Concrete answers only.
• "Tell me about a delivery commitment you missed." How they communicated it upward matters more than the miss.
• "When did you disagree with your own leadership? What did you do?" Tests whether they'll represent the team or just relay decisions.
• "How do you decide what the team works on?" Reveals whether they're a partner in prioritisation or a ticket conduit.
• "What's your view on managers writing code?" No right answer, but a considered one signals someone who has thought about the role.

Expect to sell the scope

Strong managers are evaluating the size and importance of the problem, the quality of the team, and whether they'll have the authority to fix what's broken. Compensation matters, but scope and autonomy usually decide it.

What to delete

• "Player-coach" with no percentage attached. It's the vaguest phrase in management hiring.
• "Servant leader" and similar without any concrete behaviour behind it.
• A post that lists only delivery responsibilities. It reads as project manager, not engineering manager, and the best candidates will read it that way.
• No mention of team size. The first question every candidate asks.

The takeaway

Management posts win or lose on three specifics: team size, coding expectation, and real authority. State all three, be honest about whether the team is healthy or needs rescuing, let the team meet the candidates, and interview for concrete stories about performance, promotion, and disagreement. Managers who've done the job well recognise a serious post immediately — and so do the ones who haven't.

Hiring an engineering manager? Post your role on JobsList.dev.