Most companies hire engineers the same way they've always hired engineers: post a job description, interview whoever applies, rely on gut feel. This works when you're hiring one person a year. It breaks down badly when you're hiring five or ten.
The good news: there's a substantial body of knowledge on how to hire well — structured interviewing, calibration, sourcing, offer strategy, the equity conversation. It's not secret knowledge. It's in books that the best engineering leaders have read and the majority haven't.
Here are the ones worth your time.
The most important hiring book written. Smart and Street studied 313 CEOs and 9,000 professional interviews to identify what separates "A players" from mediocre hires — and what hiring practices produce better outcomes at higher rates.
The core framework: define the Scorecard (outcomes + competencies for the role), then use a structured interview methodology to assess for those specific outcomes. The four interviews — Screening, Topgrading, Focused, and Reference — build a picture of a candidate that unstructured conversation doesn't.
What it's good for: Any hiring manager. If you read one book on this list, read Who. The key insight: Most hiring is guesswork dressed up as process. Structured interviews tied to explicit scorecards dramatically improve prediction accuracy.---
Will Larson's blog at lethain.com is required reading for engineering managers; An Elegant Puzzle is the book version. Chapter 4 ("Hiring and Sourcing") is the best single source on engineering team building at startups and growth-stage companies.
The key contributions: how to think about team sizing and hiring ratios, the "hiring funnel" from sourcing through close, and the management overhead of building a hiring function from scratch.
What it's good for: Engineering managers and VPs building teams of 5–50 engineers. The key insight: Hiring is a system, not a series of one-off decisions. The teams that hire well build repeatable processes; the teams that don't rely on heroics.---
The most comprehensive free resource on technical hiring, period. Written by practitioners (Aditya Agarwal was CTO of Dropbox; the guide draws on extensive practitioner interviews), it covers the full recruiting funnel from role definition through offer and onboarding.
At 440+ pages, it's reference material more than a cover-to-cover read. But the sections on compensation strategy, technical interviewing design, and diversity and inclusion in hiring are among the best treatments of those topics anywhere.
What it's good for: Anyone building a hiring function from scratch or trying to improve a specific part of their process. Free at the link above. The key insight: The way you write job descriptions and conduct interviews has measurable effects on who applies, who accepts, and who ultimately succeeds. Small process changes compound.---
Bock ran People Operations at Google during its hypergrowth years. The hiring chapters are the most data-driven treatment of recruiting bias, structured interview methodology, and what actually predicts performance.
The most cited finding: structured interviewing is dramatically more predictive than unstructured interviewing. GPA and academic credentials predict almost nothing after the first two years. Work samples and structured behavioral interviews predict the most.
What it's good for: Engineering leaders who want to understand the evidence base behind best practices, not just the practices.---
Claire Hughes Johnson ran operations at Stripe during its breakout years. Scaling People is the most practical book on building hiring systems at fast-growing companies — covering leveling frameworks, the interview bar, and how to maintain quality as volume increases.
The Stripe hiring bar became a model for the industry. This is the book that explains how it works and how to adapt it.
What it's good for: Engineering leaders at companies growing from 20 to 200 engineers.---
Hoffman's framework for employer-employee relationships — "tours of duty" instead of lifetime employment — is essential context for understanding what engineers want from their next role. The engineers you're hiring are thinking about what they'll learn and how this role fits their career arc. The Alliance gives you language for that conversation.
What it's good for: Anyone conducting offer conversations and trying to understand why top candidates sometimes decline.---
Not primarily a hiring book, but the chapters on hiring executives and "why do we need to hire senior people anyway?" are among the most honest treatments of the topic. Horowitz is blunt about the costs of hiring slowly vs. hiring wrong.
---
Beyond books, these are the ongoing resources that engineering leaders cite most:
The Pragmatic Engineer (Gergely Orosz) — the most widely-read engineering newsletter. The hiring coverage is exceptional: what engineers actually care about in job searches, how different companies run interviews, compensation transparency. $15/month, worth every cent if you're hiring regularly. lethain.com (Will Larson) — the blog behind An Elegant Puzzle. Essays on team sizing, technical hiring, and engineering management at Stripe, Calm, and other high-growth companies. Lenny's Newsletter — covers hiring from the founder/PM perspective. The posts on recruiting strategy and offer closing are particularly practical. LeadDev — engineering leadership publication with strong hiring content. Conference-quality articles by practitioners.---
We've placed engineers at over 100 funded startups. The patterns from Who's structured interviewing and An Elegant Puzzle's systems thinking are the ones that show up in the best hiring processes we've been part of. We work as an extension of your recruiting function, bringing this thinking to your searches. Start a search →
Related: How to Close More Engineering Offers at a Startup · Why You Can't Find Senior EngineersTell us about your open roles and we'll start sourcing within 48 hours.
