Interviewing and Evaluating Candidates

Move beyond resumes to assess high-fidelity signals like agency, first-principles thinking, and actual craft.

Help the user with interviewing and evaluating candidates using insights from 27 guests and posts across Lenny's Podcast and Newsletter.

How to Help

1. Define the Role Core - Identify specific competencies and core jobs the candidate must perform based on your unique organizational needs.
2. Design Practical Assessments - Move from abstract case studies to almost-real-life assignments or paid work trials that mimic the actual job.
3. Apply Standardized Evaluation - Implement consistent rubrics and thematic questioning to reduce bias and increase signal quality.
4. Conduct High-Fidelity Reference Checks - Verify performance with past collaborators to triangulate interview signals and uncover long-term patterns.

Core Principles

Prioritize Enthusiastic Rehires

Brian Halligan: "I think CEOs and everyone dramatically overrates their ability to interview, and overrates their gut feeling, and underrates a really high quality blind reference."

The most effective hiring signal is asking a reference if the candidate was in the top 1 percent of employees and if they would enthusiastically rehire them.

Use the Unsell Email

Kevin Yien: "When you get to offer stage, I send an email and I say all the terrible things that are probably going to reinforce their fears. If you can tell them that upfront and they can read that whole email and still be equally excited to join you, find yourself a A+ hire."

Send an email at the offer stage detailing your company's biggest flaws and challenges to ensure the candidate's commitment is based on reality.

Screen for First-Principles Thinking

Melissa Tan: "I think they looked for two main things. They looked for first principles thinkers, so not necessarily your experience, but how do you approach problems, how do you know the right questions to ask? And then create your own framework around that. Dropbox also hired for people that were just really humble, collaborative and team oriented."

Evaluate how candidates create their own frameworks rather than relying on experience to find those capable of driving cross-functional innovation.

Hire Future Strategy Drivers

Peter Deng: "In 6 months, if I'm telling you what to do, I've hired the wrong person. It helps me and the person operate on a different level where the goal is not, did you hit this OKR? The Meta goal becomes, are we calibrating enough? Are we actually getting into a spot where in 6 months you're the one telling me what needs to be done?"

Focus on finding individuals who will eventually drive the strategy and direct their managers within six months of starting.

Stack Rank References First

Shishir Mehrotra: "I generally value the reference check over interview signals. If I had to stack rank in interviews, what is the best signal? The reference check is the top of the list. Those people, they worked with this person sometimes for years, their knowledge, what you're going to get out of 30 minutes of artificial scenarios it's just like never going to compare what a good reference check will give you."

Reference checks offer a high-fidelity signal of long-term performance that artificial interview environments cannot replicate; treat them as your primary signal.

Questions to Help Users

• "What are the specific jobs or outcomes this hire needs to achieve in their first six months?"
• "Are you currently using a standardized rubric to evaluate all candidates for this role?"
• "What real-world problem from your current roadmap could serve as a work trial project?"
• "How are you screening for cultural traits like humility, agency, or clock speed?"
• "What is the most common reason candidates fail in this specific role at your company?"
• "How are you differentiating between a candidate's personal impact versus the success of their previous company?"

Common Mistakes to Flag

• Over-indexing on interview charisma - Polished interview skills are often poor predictors of actual job performance and technical depth.
• Hiring for domain experience over first-principles - Relying on established playbooks prevents candidates from solving unique problems in evolving environments.
• Treating reference checks as a formality - References provide the only longitudinal data on a candidate's behavior and performance over years.
• Using abstract or hypothetical case studies - Hypotheticals reveal how someone thinks about imaginary problems rather than how they execute on real ones.

Deep Dive

For all 39 sourced insights from 27 guests, see references/guest-insights.md

Related Skills

• Hiring Product Talent
• Org Design
• Building Growth Team
• Founding Exec Team