Interview scorecard for engineering managers, with anchors for each competency
On this page
- Which competencies should an engineering manager scorecard cover?
- The scorecard: weights and anchors for 1, 3 and 5
- The copy-ready scorecard
- Anchors for 2 and 4, and how to test each competency
- Two work samples to use in the interview
- A filled example
- How should the scorecard change by level and team?
- What mistakes are specific to scoring engineering managers?
- Where does this scorecard fit in the hiring process?
- Questions people ask
An interview scorecard for engineering managers should score six things: developing and coaching engineers, managing performance, delivery and prioritization with product, technical judgment, operational ownership of on-call and incidents, and hiring. Score each from 1 to 5 against anchors written for engineering teams, weight the people competencies at least as heavily as the technical ones, and do not let a strong system-design conversation stand in for evidence that the candidate has grown people and handled a performance problem. Get one reference from a former direct report before the offer.
The five points mean what they mean in the 1–5 interview rating scale. The loop that produces the evidence, with a quarter-planning exercise and a postmortem review, is in the interview guide for engineering managers; this page is the scoring sheet, with every point anchored and two people-side work samples the guide does not include. The individual-contributor version is the interview scorecard for software engineers.
Which competencies should an engineering manager scorecard cover?
- Developing and coaching engineers. Has the candidate grown specific people, through feedback they can quote and plans they can describe?
- Managing performance. Do they address underperformance early, separate the person from the project or tooling, and reach a decision?
- Delivery and prioritization. Do they plan against real capacity and negotiate scope with product instead of overcommitting the team?
- Technical judgment. Would engineers trust their trade-offs, and do they know when to decide and when to let the team decide?
- Operational ownership. Do they run incidents, blameless reviews and on-call load as part of the job?
- Hiring and team building. Do they define the role before interviewing, train interviewers and decide from evidence?
There is no license to check. Record the scope the candidate has managed (number of reports, managers or engineers, on-call or not) next to their name, because it frames every score, and confirm logistics such as the on-call expectation by stating it and asking whether they can meet it.
The scorecard: weights and anchors for 1, 3 and 5
Example weights for a first-line manager of five to ten engineers on a product team. Set yours at intake.
| Competency | Weight | 1 looks like | 3 looks like | 5 looks like |
|---|---|---|---|---|
| Developing and coaching engineers | 20% | One-to-ones are status updates; no example of someone they grew. | A named engineer they developed: the gap, the plan, feedback in their own words, and the result. | Several engineers grown into larger roles, including a possible successor, with the style adapted to each person. |
| Managing performance | 15% | Waited for the review cycle, passed it to HR, or moved the person to another team. | Raised it early with a clear expectation and a date, offered support, documented it, and made a decision either way. | Does the 3, first ruled out a project, tooling or clarity cause, and says what they now catch earlier. |
| Delivery and prioritization | 20% | Commits the team to everything; scope gets cut by missed dates. | Plans for leave, on-call and meetings; proposes what moves out with product; flags trade-offs early. | Re-planned mid-quarter on new information, got stakeholders to agree, and the work that mattered most shipped. |
| Technical judgment | 15% | Defers every call to the team, or overrides it with personal preference; vague on their own system. | Explains a decision on their team: the options, the trade-off, who decided, and how they would know it was wrong. | Argued for a technical investment against delivery pressure with a business reason, and can show it paid off. |
| Operational ownership | 15% | Incidents are the on-call engineer's problem; no review practice. | Coordinated an incident, ran a blameless review, and action items had owners and dates. | Cut on-call load through team-wide changes (alert cleanup, runbooks, rotation) and kept it down. |
| Hiring and team building | 15% | "I can tell a good engineer when I see one"; hiring left to recruiters. | Criteria agreed before interviews, a realistic work sample, trained interviewers, and one hire they got wrong and what changed. | Built or rebuilt a loop that others now use, widened where candidates came from, and kept the bar through growth. |
On a 1–4 scale, keep the 1 and 3 anchors and merge 4 and 5. The free scorecard builder has a people-manager preset that starts with this role and uses 1–4.
The copy-ready scorecard
Candidate: [name] Role: [EM / senior EM / manager of managers]
Scope managed: [reports, levels, on-call yes/no, years]
Interviewer: [name] Stage: [hiring manager / technical / product / team / work sample]
Competency Weight Score (1-5) Evidence (what they did, in their words)
Developing and coaching engineers 20% [ ] [ ]
Managing performance 15% [ ] [ ]
Delivery and prioritization 20% [ ] [ ]
Technical judgment 15% [ ] [ ]
Operational ownership 15% [ ] [ ]
Hiring and team building 15% [ ] [ ]
Weighted total: sum of (weight x score) = [ ]
Not assessed (and why): [ ]
Reference from a former direct report: [requested / done]
Recommendation: [Strong yes / Yes / No / Strong no]
Anchors for 2 and 4, and how to test each competency
Developing and coaching engineers
Tested by: the one-to-one role-play below and "Who is the engineer you are proudest of developing?" 2: a mentoring story where the candidate mostly gave answers rather than feedback. 4: quotes the hard feedback they gave and what the engineer did with it. More probes are in interview questions for coaching ability.
Managing performance
Tested by: "Tell me about an engineer whose performance you had to address, start to finish." 2: addressed it, but late, or with no written expectation. 4: early and documented, and they checked the environment first. The full question set is in interview questions for managing underperformance.
Delivery and prioritization
Tested by: the guide's quarter-planning exercise, scored by the product manager. 2: adjusts capacity but leaves the cut to product. 4: proposes the cut, explains the cost of each option, and keeps paging-reduction work in the plan.
Technical judgment
Tested by: a senior or staff engineer: "Draw the main system your team owns. Where does it break?" 2: accurate at a high level, but cannot say what they decided. 4: names a decision they let the team own and one they stepped into, and why each.
Operational ownership
Tested by: the guide's postmortem review and "How did you know on-call was too heavy?" 2: runs reviews, but action items drift. 4: measured paging load and protected time to fix the noisiest alerts.
Hiring and team building
Tested by: the debrief exercise below and "Walk me through your last hire, from writing the role to the decision." 2: structured loop, but cannot say what the criteria were. 4: can show the scorecard they used and how they handled a split debrief.
Two work samples to use in the interview
The quiet senior engineer (one-to-one role-play, 15 minutes). The interviewer plays a senior engineer who was a top performer, has gone quiet in meetings for a month and, a few minutes in, says they were turned down for promotion without a clear reason and are "looking around." The candidate runs the one-to-one.
What to listen for: asking before advising; owning that the promotion criteria were not made clear; a concrete next step (the written criteria, a project that shows the missing evidence, a date to revisit); no promise they cannot keep; and no pressure or threat about the job search.
The split debrief (15 minutes). Give four invented interviewer scorecards for an engineer candidate: two "yes" with specific evidence, one "no" on system design with a quoted gap, and one "strong no" that says only "not a culture fit." Ask: "You are the hiring manager. How do you run this debrief, and what do you decide?"
What to listen for: asking the "strong no" interviewer for evidence against the criteria and setting the comment aside if there is none (see how to assess values without culture-fit bias); weighing the system design gap against the level; and a decision rule stated before discussing, as in the interview debrief template.
A filled example
A made-up candidate who manages seven engineers on a payments team, scored across the loop:
Developing and coaching engineers — 4. In the role-play, asked two questions before saying anything about the promotion, admitted the criteria "lived in my head," and offered to write them down that week with a review date. Earlier described telling a mid-level engineer, "Your designs are right, but nobody can review them," and the design docs that followed.
Managing performance — 3. Addressed missed commitments within two sprints with a written expectation; the engineer moved to a role that fit better. Did not first check whether the commitments were realistic.
Delivery and prioritization — 3. In quarter planning, adjusted for the leave and on-call, and proposed moving one roadmap item; left the customer-promise question to the product manager.
Technical judgment — 4. Explained why the team kept a monolith for ledger writes and split out notifications, and the incident that would make them revisit it.
Operational ownership — 3. Ran blameless reviews with owners and dates; had not measured paging load.
Hiring and team building — 2. In the split debrief, sided with the majority without asking the "culture fit" interviewer for evidence.
Weighted total (example arithmetic): 0.20×4 + 0.15×3 + 0.20×3 + 0.15×4 + 0.15×3 + 0.15×2 = 3.20. Recommendation: Yes, if the reference from a former report confirms the coaching, with hiring judgment as the first thing to work on.
A sample decision rule, to adapt: no score below 3 on coaching or performance management for an experienced manager (2 allowed for a first-time manager with a 4 in the role-play), no 1 on technical judgment, and a weighted total of 3.0 or higher.
How should the scorecard change by level and team?
| Situation | What to change |
|---|---|
| Tech lead moving into management | Accept evidence from mentoring, leading projects and running a rotation; mark formal performance management "not assessed" if they have never had the authority. The people manager loop adds a one-to-one stage. |
| Manager of managers | Replace hiring with "developing managers," anchored on a manager they coached through a team problem; raise delivery to an organization-level planning case. |
| Platform or infrastructure team | Raise operational ownership to 25%; the delivery exercise uses internal customers instead of a product manager. |
| Small company where the manager still codes | Add a hands-on line at 10% and take it from delivery; score it with the software engineer anchors. |
What mistakes are specific to scoring engineering managers?
| Mistake | Why it fails | Fix |
|---|---|---|
| Scoring the candidate's coding | Rewards the strongest engineer, the trap the 30-60-90 day plan for engineering managers warns about | Score technical judgment, not output |
| Crediting the employer's brand | A well-known company's delivery record is not this manager's | Score only what the candidate decided and did |
| Confidence read as judgment | A fluent plan with no trade-offs scores like a 4 when it is a 2 | Ask what they would give up, and score the answer |
| Asking about family to test on-call | It reaches family status, not the job | State the on-call expectation and ask whether they can meet it |
| Age proxies such as "years since they last coded" or "energy" | Neither is a competency, and both can stand in for age | Score the six rows only |
| No reference from a report | Peers and bosses see delivery; reports see management | Ask for one former direct report and score coaching only after it |
Where does this scorecard fit in the hiring process?
Split the rows across the loop so each interviewer owns two or three: the hiring manager takes performance and hiring, a staff engineer takes technical judgment, the product manager takes delivery, and an engineer from the team runs the one-to-one role-play. Everyone submits before the debrief, and the people management questions fill any row a stage left thin. If you run these interviews in Interview Signal (we make it), you can enter the six competencies as scorecard areas on the kit screen, each with a weight of 1, 2 or 3; it scores each area from 1 to 10 against three rubric lines, attaches the candidate's own quotes checked against the transcript, and caps an area with no quote at 5, marked "Probe further."
Questions people ask
What should an engineering manager interview scorecard measure?
Six competencies: developing and coaching engineers, managing performance, delivery and prioritization with product, technical judgment, operational ownership of on-call and incidents, and hiring. Score each from 1 to 5 against anchors written for engineering teams, weight the people competencies at least as heavily as the technical ones, and collect one reference from a former direct report before deciding.
Should an engineering manager candidate pass a coding interview?
Usually not the team's full coding loop. Score technical judgment instead: whether the candidate can explain the trade-offs in a system their team owns, knows when to let engineers decide and when to step in, and can justify time spent on technical debt. Add a light hands-on exercise only if the role really includes regular coding, and score it as its own line.
How do I score a first-time engineering manager against experienced managers?
Use the same anchors and accept evidence from leading projects, mentoring and running on-call rotations as a tech lead. A first-time manager can reach a 3 on coaching by describing an engineer they mentored through a promotion case; mark competencies they have had no chance to show, such as handling a formal performance plan, as not assessed rather than scoring them 1.
Who should score which part of an engineering manager scorecard?
Split it so each interviewer owns two or three rows: the hiring manager scores performance management and hiring, a senior or staff engineer scores technical judgment, a product manager scores delivery and prioritization, and an engineer from the team scores coaching from their own questions. Everyone submits before the debrief.