How to run a hiring manager screen

The 45-minute structure

1. 0–5 — The role, the team, how the loop works.
2. 5–15 — Current scope: what they own, who they work with, what decisions are theirs.
3. 15–30 — One piece of work in depth, with follow-ups.
4. 30–35 — What they want next and why this role.
5. 35–45 — Their questions, then next steps with a date.

Scope is how you calibrate level

Titles are unreliable across companies; scope is not. Ask what they own rather than what they do: which decisions are theirs to make without asking, what happens when they disagree with a product manager, who reviews their work and who they review. Two candidates with the same title routinely describe entirely different jobs, and this is the quickest way to find out which one is in front of you.

Go deep on one thing, not shallow on five

A hiring manager screen is not a tour of the CV. Pick the single most relevant item and spend fifteen minutes on it, with the standard follow-up sequence: what did you specifically do, what else did you consider, what happened afterwards. You are looking for whether they reach a real decision with a trade-off they can name. One topic explored properly tells you more about level than five summarised.

Test motivation honestly

• “What are you looking for that you are not getting now?” More useful than “why do you want to work here”, which invites flattery.
• Then check it against reality. If they want more architectural ownership and this role is mostly delivery, say so now. A mismatch found in week three of employment is far more expensive than one found here.
• Ask what would make them turn this down. Candidates answer this more honestly than expected, and it tells you what to address at offer stage.

Sell, but only after you have assessed

Hiring managers routinely spend the first twenty minutes selling. This wastes the part of the conversation where the candidate is most honest, and it sells before you know whether you want to. Assess first, then sell in the last ten minutes, tailored to what they actually told you they wanted. A specific pitch built on their stated motivation beats a generic one every time.

The output is a note for the loop

The main deliverable is not a yes or no; it is two sentences telling the rest of the loop what to probe. “Strong on delivery, no evidence yet of designing anything from scratch — design round should push on that” turns four generic interviews into four targeted ones. Without it, your loop assesses whatever each interviewer thinks of. See how to design an interview loop.

Where it sits in the loop

• After a recruiter screen for high-volume roles, so you are not doing logistics.
• First, for senior and leadership roles, where level and motivation are the main filters and a recruiter cannot judge them.
• Never last. A hiring manager who meets the candidate only at the end cannot steer the loop, which is most of the value of this conversation.

Questions that calibrate level quickly

• “What decisions can you make without asking anyone?” The sharpest level question available. Answers range from “which library to use” to “what the team works on next quarter”.
• “Who reviews your work, and whose work do you review?” Locates them in the team rather than in the org chart.
• “What happens when you disagree with your product manager?” Tells you whether they have standing, and how they use it.
• “What would break if you left tomorrow?” Uncomfortable and extremely informative about real ownership.
• “What is the largest thing you have been trusted with?” Lets the candidate choose the evidence, which is itself a signal.

Red flags specific to this conversation

Two patterns are worth noticing here rather than later. The first is a candidate who cannot describe any decision as theirs — everything was assigned, reviewed and approved by someone else. That may be accurate and simply means a more junior level than the title suggests. The second is a candidate whose account of why they are leaving is entirely about other people's failings. One difficult manager is unremarkable; a pattern where nothing was ever within their influence is worth probing gently in the loop.

Write the decision before you discuss it

Hiring managers anchor the loop more than anyone, so this is where independent scoring matters most. Write your assessment immediately, against the rubric, and keep it to yourself until the debrief. See how to run an interview debrief and interviewing vs screening.

Where Interviewer Mode fits

Disclosure: we make CoPilot Interview, which includes Interviewer Mode for the hiring side and a real-time assistant used by candidates. We have an interest in you using the first, and our view of the second is that interviews should be designed to measure something an assistant cannot fake. Weigh the advice below accordingly.

Frequently asked questions

What is a hiring manager screen?

A 45-minute conversation with the person the candidate would report to, covering current scope, one piece of work in depth, and motivation. Its purpose is to calibrate level, check that what the candidate wants exists in this role, and decide what the rest of the loop should probe.

What should a hiring manager ask in a first call?

What they currently own and which decisions are theirs, one piece of relevant work explored in depth with follow-ups, and what they are looking for that they are not getting now. Scope questions calibrate level far better than titles do.

Should the hiring manager screen come first or last?

First for senior and leadership roles, and after a recruiter screen for high-volume ones. Never last — a hiring manager who meets the candidate at the end cannot use what they learn to steer the loop.

How much should a hiring manager sell in a screen?

Only in the last ten minutes, after assessing. Selling early wastes the most honest part of the conversation and means pitching before you know whether you want the candidate. A pitch built on their stated motivation works better than a generic one.