Why this role resists assessment
Every other engineering hire produces an artefact. Code, a design, a pipeline, an incident review. You can look at it and form a judgement that is mostly about the work rather than about the person describing it.
A manager's artefact is a team that shipped, or did not, and grew, or did not — visible in quarters, not in an interview. What you get instead is a narrative about that team, delivered by someone with an interest in the narrative. Manager interviews therefore over-select for people who tell a clean story.
You cannot close that gap entirely. You can narrow it by asking for specifics that a good storyteller who did not do the work will not have.
People development — ask for the hard conversation
The reliable probe is not "how do you develop people". It is: tell me about someone on your team who was not performing, and what you did. Everyone has one. What they say next sorts them quickly.
| Weak | Strong |
|---|---|
| Avoids the question, or reframes it as a hiring mistake someone else made. | Names the specific gap, when they first noticed it, and how long they waited before saying something. |
| Talks about throughput and reassignment. The person is a resource being routed. | Talks about the conversation itself — what was said, how it landed, what changed afterwards. |
| The story ends with the person leaving, framed as inevitable. | The story includes what they would do earlier next time. Often the answer is "start six weeks sooner". |
The second-best probe is the inverse: someone who grew unusually fast under them, and what they actually did to cause it. Vague answers here are common and forgivable. Vague answers to both questions are a pattern.
Delivery — look for the trade-off, not the hit rate
Candidates who say they always hit deadlines are describing either a very unusual team or an unexamined memory. The useful question is what they did when a date was going to slip.
- Weak: hoped, then pushed the team to recover the schedule. Burnout is described as commitment.
- Strong: noticed early from something measurable, then took a named trade-off to a stakeholder — scope, date, or quality — and made the choice explicit rather than absorbing it quietly.
Ask which of the three they gave up and who they told. A manager who has never had that conversation has either never had a slip or has been hiding them.
Technical partnership, between two failure modes
Managers who came from engineering fail in two opposite directions, and both are visible in an interview if you ask about a disagreement with a senior engineer.
One keeps making the technical calls, which is why the staff engineer eventually leaves. The other abdicates entirely and cannot tell whether a technical plan is realistic, which is how a team spends two quarters on a rewrite nobody sanctioned. The answer you want questions the technical assumption through the lens of team capacity, without overruling it.
What no assessment will tell you
This is the role where a written assessment is weakest, and it would be convenient not to say so on a site that sells assessments.
- Whether people want to work for them. Reference conversations with former reports are worth more than any exercise, and they are the one input we cannot generate.
- How they behave when the company is going badly. Nobody screens for this well.
- Whether they will suit your specific team. A manager who was excellent with four seniors may struggle with four juniors, and the reverse.
Use an assessment for the first cut, not the decision
A structured screen is good at surfacing who has genuinely done the work, so your interview time goes to the right three people. For this role it should not do more than that.
On what a first cut should actually contain, what candidate assessment is and how to choose a method covers which instrument suits which role — including the cases, like this one, where every available method is weak.