How to Hire as a Manager: Writing a Req, Interviewing, and Deciding

Sep 10, 2026 | Blog, Leading Others

Hiring looks simple from the outside: open a req, meet a few people, pick the one you like. Then you inherit someone who cannot own the work you actually needed, and the next six months become a recovery project.

Most bad hires start as fuzzy reqs. If the team cannot describe the first six months of problems the hire must solve, interviewers will optimize for chemistry and pedigree. Write the role as a set of decisions and deliverables, then interview for evidence of having made similar decisions.

This guide is for first-time and mid-level hiring managers who own the role definition and the interview loop, and for directors who want cleaner hiring quality on their teams. It is practical process, not employment-law advice. Follow your company’s recruiting policy, HR guidance, and counsel. Rules vary by place and employer.

For what happens after the offer lands, pair this with the employee onboarding checklist and first 90 days as a new manager if you are still building your own operating system.

Write the role as outcomes, not a unicorn wish list

A job description that lists every tool, every soft skill, and ten years of experience in three different domains is not a hiring strategy. It is a filter that scares away strong people and still fails to tell interviewers what “good” looks like.

Start with a short job outcomes worksheet before you touch the public posting:

Mission of the seat (1-2 sentences): Why does this role exist for the team and the business?
First 6 months of problems: The three to five concrete problems this person must make progress on.
Decisions they will own: What can they decide alone vs escalate?
Deliverables and artifacts: What will exist if they succeed (roadmaps, launches, process, customer outcomes, reports)?
Stakeholders: Who depends on them, and who can block them?
Constraints: Team size, budget, legacy systems, compliance, remote vs onsite, travel.
Manager support: What coaching and air cover you will provide so the role is doable.

If you cannot fill that worksheet, you are not ready to open the req. You are still clarifying the job.

Must-have vs nice-to-have (be ruthless)

Must-haves are skills or experiences without which the person cannot do the job in a reasonable ramp. Keep the list short. Examples: “has owned a multi-quarter project with cross-team dependencies,” not “expert in five frameworks.”

Nice-to-haves are accelerators. Industry familiarity, a specific tool, a preferred domain. Put them in a separate section so screening does not treat them as hard gates.

A useful test: if removing a requirement would not change the first six months of problems, it is not a must-have. Pedigree proxies (brand-name employers, elite schools) are weak must-haves unless your work truly requires a credential. Prefer evidence of judgment and ownership.

Also write what the role is not. “This is not a people-manager seat in year one” or “This is not a pure IC craft role; stakeholder management is half the job.” Clarity here prevents bait-and-switch later.

Partner with recruiting without abdicating ownership

Recruiting owns process mechanics: sourcing channels, scheduling, candidate experience, offer paperwork, and often market context. You own the definition of success, interview quality, and the hire decision (within company rules).

A healthy partnership looks like this:

Topic	Hiring manager owns	Recruiting owns	Shared
Role definition	Outcomes, must-haves, level	Market feedback on title/level language	Align before posting
Sourcing	Referral outreach, team sell	Pipeline strategy, outreach, agencies if used	Weekly pipeline review
Interviews	Question design, scorecards, interviewer briefing	Loop logistics, reminders, candidate updates	Interviewer training norms
Decision	Evidence-based recommendation	Process fairness, calibration support	Debrief facilitation
Offer	Comp philosophy input, close plan	Offer letter, approvals routing, negotiation coaching	Candidate close

Do not disappear after the req is posted. Recruiters cannot invent a crisp bar you never wrote down. Do not micromanage every email either. Agree on a weekly 20-minute sync: pipeline health, stuck stages, feedback quality, and whether the bar or the market is the real problem.

When HR or recruiting flags a process or compliance concern, treat it as a stop sign, not a suggestion. See HR for humans for how People partners typically divide work.

Build a structured interview loop

Unstructured “chat and vibe” interviews reward confidence and similarity. Structured loops improve signal and fairness when they are actually used.

A typical loop (customize to level and company):

Recruiter screen: logistics, interest, basic fit, compensation range alignment where your process allows.
Hiring manager screen: role outcomes, motivation, high-level evidence of similar work, sell the role honestly.
Core competency interviews (2-4): deep dives tied to must-haves.
Work sample or case (when relevant): a scoped exercise that mirrors real work, with clear evaluation criteria.
Cross-functional or stakeholder interview: collaboration under ambiguity.
Values / working-norms interview (optional): how they handle conflict, feedback, and tradeoffs, still tied to job-relevant behavior.
Debrief and decision.
References (when your process uses them) before final offer.

Interview loop RACI (illustrative)

Step	Hiring manager	Interviewers	Recruiter	Skip-level / director
Scorecard design	Accountable	Consulted	Consulted	Informed (for senior roles)
Running interviews	Responsible (own slot)	Responsible	Informed	Optional slot
Notes and scores	Responsible	Responsible	Informed	–
Debrief	Accountable	Consulted	Facilitates / process	Approves for senior roles if required
Offer recommendation	Accountable	Informed	Responsible for packaging	Approves per policy

Keep loops as short as the risk allows. Extra interviews that ask the same questions twice create candidate fatigue and do not add signal.

Tie questions to competencies, not improvisation

For each must-have, write two to four questions that ask for past behavior or a realistic work sample. Prefer “Tell me about a time…” and “Walk me through how you would…” over abstract “What is your leadership style?”

Illustrative question bank by competency

Ownership under ambiguity
– Tell me about a project where the goal moved midstream. What did you decide, what did you escalate, and what was the result?
– Describe a time you shipped something imperfect on purpose. How did you choose the cut line?

Cross-team influence
– Walk me through a time a partner team blocked your work. What did you try, and what changed?

Technical or craft depth (adapt to role)
– Pick a hard problem you solved recently. What options did you reject and why?

Prioritization
– Tell me about a week with more urgent asks than capacity. How did you decide what slipped?
– How do you communicate tradeoffs to your manager when everything is labeled P0?

Brief every interviewer on which competency they own. Overlap on purpose is fine for critical bars. Accidental overlap that crowds out other bars is not.

Notes, scorecards, and consistent scoring

Chemistry fades. Notes do not. Ask every interviewer to capture:

The question asked
What the candidate said (paraphrase is fine; avoid mind-reading)
Evidence for and against the competency
A score on a shared scale (for example 1-4 with written definitions)
A hire / lean hire / lean no / no recommendation for their competency only

Sample scorecard row

Competency	Definition of “strong”	Evidence (quotes / examples)	Score (1-4)	Confidence (low/med/high)
Ownership under ambiguity	Makes decisions with incomplete info, documents tradeoffs, escalates risks early

Score before the debrief, independently. Do not wait to hear what the loudest interviewer thought. That single habit reduces the loudest-voice problem more than any pep talk about bias.

Avoid scores based on “I could see myself grabbing coffee with them” unless rapport is a documented job requirement (it rarely is for ICs). Culture add and working norms can be evaluated through behavior: how they disagree, how they give credit, how they handle feedback in the interview itself.

Run a debrief that reduces the loudest voice

A good debrief is a structured evidence review, not a popularity vote.

Debrief agenda (30-45 minutes)

Recruiter opens: process reminder, timebox, decision options (advance / hold / reject).
Independent scores first: each interviewer shares score and recommendation without long storytelling yet.
Competency by competency: start with must-haves. Read evidence, not vibes.
Probe disagreements: “What would change your score?” Separate missing information from true risk.
Watch for proxies: pedigree, accent, similarity to the team, “polish,” or one charismatic answer outweighing thin evidence elsewhere.
Decision and next step: hire, another targeted interview, or pass. Name the owner and deadline.
Feedback quality check: if notes are thin, do not pretend the signal was strong.

The hiring manager should speak last on the overall recommendation after evidence is on the table. Directors improving hiring quality should audit a sample of debriefs: Are scorecards filled? Are must-haves actually discussed? Are “no” votes explained with job-relevant reasons?

Bias basics and process controls (high-level)

Everyone has shortcuts in judgment. Process does not make you perfectly objective. It makes decisions more reviewable and more tied to the job.

Helpful controls many companies use: written competencies before sourcing, the same core questions at the same stage, independent scoring before group discussion, diverse panels where practical, rubrics for work samples, documented advance/reject reasons, and recruiter or HR process audits.

This is education, not legal advice on protected classes or which questions are unlawful where you hire. Do not freestyle medical, family, age, or national-origin fishing questions. When unsure, ask HR or counsel before the loop starts. For sensitive issues outside hiring, when to talk to HR vs your manager maps typical lanes.

Work samples and references

Work samples beat hypotheticals when designed well: time-boxed, relevant, respectful of candidate time, and scored with a rubric. Pay take-home work when your company policy says to, and never use unpaid labor that looks like free consulting.

References are useful for pattern checks, not for hunting for a single glowing quote. Ask about scope, decision quality, collaboration under stress, and what support the person needed. Weight references that saw recent, similar work. Treat glowing-but-vague references as weak signal.

Decide: hire now vs keep searching

There is no universal “quality of hire” number that saves you. Use a decision frame:

Hire now when:
– Must-have evidence is strong across independent interviewers
– Gaps are coachable within your real capacity to coach
– The first six months of problems match their demonstrated decisions
– The team’s pain of waiting exceeds the risk of a known gap

Keep searching when:
– Interviewers disagree on a must-have and another interview will not resolve it
– The candidate is strong for a different job than the one you opened
– You keep lowering the bar because the calendar is tired
– Onboarding load would crush the team without a realistic ramp plan

“Good enough now” is a legitimate business decision when the role’s problems are urgent and the gaps are explicit. “We’ll fix them later” without a plan is how fuzzy reqs become fuzzy performance management. If you hire with known gaps, write the ramp plan the same week you offer. Your performance review manager guide will thank you later for clear expectations from day one.

Closing, offers, and what you should document

Hiring managers own more of the close than they think. Candidates decide with incomplete information. Sell honestly: real problems, real constraints, real teammates, and why the seat matters.

Offer kickoff checklist

[ ] Align with recruiter on level, comp band, start flexibility, and approval path
[ ] Confirm title and scope match what was interviewed
[ ] Prepare a close call: role outcomes, team, manager style, growth path, known challenges
[ ] Answer candidate questions without overpromising headcount, promotions, or roadmap certainty
[ ] Coordinate written offer through the official process (do not freelance side deals)
[ ] Plan day-one ownership with the onboarding checklist
[ ] Notify interviewers and stakeholders once accepted; protect declined candidates’ dignity

Document for fairness and future calibration:

The outcomes worksheet and must-have list used for the search
Scorecards and debrief notes retained per company policy
Why you hired (or passed) in job-relevant language
Known gaps and the 30/60/90 support plan

That packet helps the next search, helps calibration across managers, and reduces “we just had a feeling” folklore.

FAQ

How do I write a job req that is not a unicorn list?

Start with the first six months of problems, decisions, and deliverables. Convert those into a short must-have list. Park everything else under nice-to-have. If a requirement does not change those early outcomes, cut it.

What belongs in a structured interview loop?

A clear stage sequence, assigned competencies, shared scorecards, independent scoring, a work sample when useful, a facilitated debrief, and a documented decision. Length should match role risk, not habit.

How should interviewers take notes and score?

Capture question, evidence, score, and confidence before the debrief. Score only the competencies you were assigned. Avoid rewriting history after you hear peers speak.

How do we reduce the loudest-voice problem in debriefs?

Collect independent scores first, review must-haves with evidence, and have the hiring manager synthesize last. Thin notes should weaken a strong verbal opinion, not the other way around.

Is this legal advice on what I can ask in interviews?

No. This is workplace process education. Interview and hiring rules vary. Follow company policy and ask HR or counsel for jurisdiction-specific requirements.

When should I stop searching and hire?

When must-have evidence is solid, remaining gaps are coachable with a real plan, and waiting costs more than the known risks. Do not lower the bar silently because the team is tired.