Hiring Intake Meeting Template for Engineering Roles

Where engineering hires actually fail

When a senior engineering hire blows up — wrong person, wrong level, declined offer, fast attrition — the root cause is almost never the final debrief. It is the 30-minute conversation that should have happened at intake and didn't.

The recruiter and hiring manager agreed on roughly what the role was. They never agreed on what "good" looked like. So the recruiter sourced candidates the manager would later reject, the panel calibrated against different bars, and the offer stage surfaced comp expectations no one had checked. Every dollar spent on the funnel was spent against unclear targets.

The intake meeting fixes that. Here is the template we use, the questions every recruiter should walk in with, and the outputs that should land in the ATS before the first candidate is sourced.

What an intake meeting is (and isn't)

It is a structured working session between the recruiter and the hiring manager — held before a job opens publicly — to agree on the role, the loop, and the bar.

It is not:

• A kickoff slide deck.
• A job-description writing meeting.
• A status update.

If you walk out with a JD and nothing else, you ran the wrong meeting. The JD is a byproduct of the artifacts below.

The 30-minute agenda

Thirty minutes is enough for a single individual-contributor role. Block 45 if it's a brand-new function or a director+ search.

The order matters. Skipping straight to the loop without nailing down outcomes is how you end up testing for a skill the role does not need.

0–5: Outcomes for the first 90 days

Start here, before titles or required years. The question: "Imagine it's three months in and this hire is a clear win. What have they delivered?"

Acceptable answers are concrete: shipped the migration off the legacy queue, brought oncall paging volume below 2/week, hired and onboarded two reports. Unacceptable answers are titles ("they're being a senior engineer"). If the hiring manager can't give you concrete 90-day outcomes, the role is not ready to open.

5–10: Must-haves vs. nice-to-haves

Force a two-column split. Most managers pile everything into must-have because it feels safer. Push back: "If we found a candidate with everything in column A but nothing in column B, would you interview them?" The answer reveals which column each item actually belongs in.

Apply the same pressure to years of experience. "Why eight years and not five?" usually has no answer — and dropping the floor opens the funnel meaningfully.

10–15: Calibration on one real resume

The single most useful step in the intake. Bring one anonymized resume from a past candidate the team has interviewed before — ideally one the manager was on the fence about. Walk through it together. Where did they pass? Where did they fail? What would tip them either way?

This is how you find out the manager's actual bar is two levels above what their JD implies. Better to discover that now than after sourcing 40 candidates against the wrong target.

15–20: Loop design

Sketch the loop end-to-end:

1. Initial screen — recruiter conversation or async assessment?
2. Technical signal — live coding, take-home, or async-then-sync?
3. Manager and cross-functional interviews
4. Debrief and offer

For each stage, name the dimension you are testing and the interviewer who owns it. If two stages test the same dimension, collapse them. If a dimension from your scorecard has no owning stage, add one.

20–25: Scorecard and rubric

Lock in the rubric in the meeting, not after. Use a structured scorecard template with 4–6 axes — any more and the panel won't actually use them. Anchor each axis with what a 1, 3, and 5 look like; vague rubrics are how you get interviewer drift.

25–30: Logistics

Three items, no more:

• Comp band. If the manager can't quote a range, no offer can move forward — surface that gap now.
• Timeline. "When does this need to be filled?" anchors urgency and sets a time-to-hire target.
• Sourcing channels. Inbound only? Outbound? Referrals? Agency? Each implies a different funnel volume.

12 questions the recruiter must walk in with

Print these on a card. Half are about the role, half about the manager's bar.

About the role:

1. What does success in the first 90 days look like?
2. What is the one problem this hire owns end-to-end?
3. What team is on the other end of their work?
4. Why is this role open — backfill, growth, new function?
5. What did the last person who tried this role do well? What did they miss?

About the bar:

6. Walk me through this resume — would you interview them?
7. What is a "must-have" you would actually waive for the right candidate?
8. What is a "nice-to-have" you would actually reject for?
9. Where do you usually disagree with the rest of the panel?
10. Who else needs to interview, and what dimension does each test?
11. What does a strong-no look like from you?
12. What does "this person is better than half my current team" look like?

The last two flush out the bar in a way "describe your ideal candidate" never does.

Outputs to walk away with

By the end of the meeting, these artifacts should exist:

• A 3-bullet 90-day outcomes statement
• A must-have / nice-to-have list, both shorter than 5 items
• An anchored scorecard rubric with 4–6 axes
• A loop diagram with named owners per stage
• A comp range, target time-to-hire, and primary sourcing channel

Drop them onto the role record in your ATS so every interviewer on the loop sees the same target.

The four mistakes that kill intake meetings

• Letting the manager dictate the loop without the rubric. Without anchors, every interviewer brings their own bar — that is calibration drift baked in from day one.
• Accepting "we'll figure it out as we go" on comp. Every senior offer that falls apart at the comp stage was avoidable here.
• Skipping the resume walk-through. It feels like a luxury. It is the only step that reveals the manager's actual bar in five minutes.
• Treating the JD as the deliverable. The JD is downstream of the rubric, not upstream. Write it after the meeting, not during it.

What to do next

Block 30 minutes with your next hiring manager before the role opens. Bring this template and the 12 questions. Walk out with the five artifacts above and drop them into your hiring scorecard. The next 40 hours of sourcing will be aimed at the right target.

The funnel does not start at "applied." It starts at "we agreed on what we wanted."