The Holloway Guide to Technical Recruiting and Hiring

Book · 2019

Ozzie Osman's 2019 Holloway guide, co-written with dozens of engineering leaders and recruiters, on building a technical interview process from scratch — candidate-company fit, IC leveling, rubric design, interviewer panels, and debrief sessions. MC's most operational reference for turning hiring theory into a repeatable process.

Author
Ozzie Osman
Published
2019

  • Candidate-company fit — alignment between what a company needs and what a candidate wants, not a copied template process — is the guide’s governing philosophy for the whole hiring funnel [1].
  • Levels exist to do real work, not just create titles: they support engineers’ growth, unify expectations across a team, map compensation fairly, and let a company evaluate candidates against a consistent, less-biased bar [2].
  • A rubric — written guidance for what counts as a poor, fair, good, or excellent answer to a given interview question — is what makes a structured interview fair; without one, interviewers default to gut feel and inconsistent standards [3].
  • Not everyone on a team should interview. Interviewer roles need to be assigned deliberately, matched to who can actually assess a skill or represent the company well, rather than opened to anyone willing [4].
  • The debrief session has one non-negotiable discipline: every interviewer states an explicit answer to “should we hire this person?” before the group synthesizes feedback, surfaces disagreement, and decides [5].
  • Referrals, especially from current employees, are the most common source of hires across industries and company stages — the guide treats them as the highest-leverage sourcing channel to build a process around, not an incidental one [6].

  • Building your first leveling ladder from nothing: without this guide, “level 4” and “senior” are titles you’re guessing at, and compensation and hiring-bar decisions drift with whoever’s negotiating hardest. The guide’s leveling chapter gives you the reasoning (growth, fairness, consistent evaluation) to build a ladder that does actual work rather than decorate an offer letter. See Defining roles and The MOC for the underlying leveling logic.
  • An interview loop that produces wildly different verdicts from different interviewers: without a rubric, each interviewer is scoring against their own private bar, and the debrief becomes a negotiation between opinions instead of a synthesis of evidence. The guide’s rubric-and-debrief discipline — everyone answers the same explicit question before the group talks — is the corrective. See Running interviews that predict performance and The Calibration Call.
  • Assembling an interview panel by asking whoever’s free: without this guide, “everyone should interview” gets applied literally, and a panelist with poor judgment or a bad bedside manner does real damage to the candidate experience and the hire/no-hire call. The guide’s answer is that panel membership is a deliberate assignment, not an open invitation.
  • Deciding where to spend sourcing effort: without this guide, sourcing budget defaults to job boards and outbound recruiters because they’re the most visible channel. The guide’s data-backed case for referrals says the highest-signal channel is usually already inside the company. See Building a pipeline.

1
Ozzie Osman et al., The Holloway Guide to Technical Recruiting and Hiring (Holloway, 2019), § "Candidate-Company Fit".
2
Osman et al., Technical Recruiting and Hiring, § "Setting Levels and Titles".
3
Osman et al., Technical Recruiting and Hiring, § "Evaluating Interviews".
4
Osman et al., Technical Recruiting and Hiring, § "Should Everyone Interview?".
5
Osman et al., Technical Recruiting and Hiring, § "Debrief Sessions".
6
Osman et al., Technical Recruiting and Hiring, § "Referrals".