Walk through the candidate's career in order, job by job. For each role, ask what they were hired to do, what they achieved, what went wrong, how their boss would rate them and why they left. Patterns across jobs predict performance better than rehearsed answers. Then confirm the story with references.
Talent leads tell me the most common hiring miss they see in the portfolio looks the same every time. A founder meets a senior candidate, has a great 45-minute conversation, and makes an offer. Six months later it isn't working, and when everyone looks back, nobody can point to a single hard fact the founder learned about how this person actually performed.
The deep-dive interview is the fix. It's slower and more structured than a normal interview, and that's the point. It's often called a chronological or career-walkthrough interview, and it's the core of Topgrading-style hiring methods. A platform talent team that can run it well, and teach founders to run it, is giving them one of the most useful hiring skills there is.
Why the chronological interview works
A normal interview asks hypothetical questions ("How would you handle…?") and gets rehearsed answers. Most senior candidates have done dozens of interviews, and they're good at them.
The chronological interview asks about what actually happened, in order, across every job. That changes three things:
- It's hard to fake for two hours. A candidate can polish one story. Polishing a consistent story across five jobs, with names and numbers, is much harder.
- Patterns show up. One bad boss is bad luck. A bad boss at every job is information. The same goes for reasons for leaving, the kind of wins, and the kind of mistakes.
- References become a check, not a formality. Because you've heard the candidate's version in detail, you know exactly what to ask their former managers.
The trade-off is time. Plan on about 90 minutes for a mid-level role and up to three hours for an executive. For a hire that will shape a company for years, that's cheap.
Start with a scorecard, not a resume
Before the interview, write down what success looks like in this role: the three to five outcomes the person must deliver in their first 12 to 18 months, plus the competencies those outcomes need. Without that, the interviewer ends up judging likability. I covered how to build one for platform roles in what good looks like when hiring VC platform talent. The same structure works for portfolio hires.
Then read the resume against the scorecard. Mark the jobs that matter most, usually the last 10 to 15 years, and note any gaps or short stints you want to understand.
How to run the interview
Use two interviewers if you can: one asks, one takes notes. If you record or transcribe the conversation, tell the candidate up front and get their agreement.
The flow:
- Set expectations. Tell the candidate you'll walk through their career in order, it'll take a while, and you'll ask about every role. Mention that you'll later ask them to set up calls with some of their former managers. That one sentence makes answers more candid for the rest of the interview.
- Go fast through the early years. Education and first jobs get a few minutes. You're looking for early signs of drive and choices, not detail.
- Go deep on recent roles. For each job in the last 10 to 15 years, ask the same core questions, in the same order.
- Close with the future. What do they want next, and why does this role fit?
The discipline is asking the same questions for every job. That's what makes the patterns visible.
Dig until you get specifics
The first answer to any question is usually the polished one. The real information comes from the follow-ups. Some probes that work:
- "What, specifically, did you do?" (as opposed to the team)
- "What was the number before, and what was it after?"
- "Who else worked on that, and what would they say your part was?"
- "What did your boss think of the result?"
- "Knowing what you know now, what would you do differently?"
Listen for "we" versus "I." Some "we" is healthy and honest. A career told entirely in "we," with no clear personal contribution, deserves more probing. So does a career told entirely in "I," where nobody else ever helped.
Read the patterns, not the stories
After the interview, the two interviewers fill in the scorecard separately, then compare. Look across the whole career:
| Look for | Watch out for |
|---|---|
| Scope that grew job over job | Same level of role for many years without a clear reason |
| Left because they were pulled to something bigger | Left because of conflict, repeatedly |
| Specific wins with numbers | Vague wins that can't be measured |
| Mistakes owned, with a clear lesson | Mistakes blamed on others, or no mistakes at all |
| Former bosses they'd happily have you call | Reluctance to name any former manager |
No candidate is perfect on every row. What you want is a story that holds together and a scorecard backed by evidence.
Close the loop with references
Ask the candidate to set up calls with two or three former managers you choose from the interview. Use the same structure: what was this person hired to do, what did they deliver, where did they struggle, how would you rate them, and would you hire them again? Compare the answers to what the candidate told you. Differences in detail are normal. Differences in the overall picture are what you're looking for.
AI can help with the admin around all of this. It can turn a transcript into a draft summary per job against the scorecard, flag where the candidate's numbers changed between answers, and draft reference call guides. It shouldn't make the call. A person reads the evidence and decides. I wrote more about where AI fits in hiring in how VC talent teams can use AI to automate recruiting workflows.
What questions belong in a deep-dive interview?
Ask the same core questions for every job: what were you hired to do, what are you most proud of, what were your mistakes, who did you work with and how would they rate you, and why did you leave. Follow up on each answer until you have specifics, numbers and names.
A one-page template you can hand to a founder:
For each job, in order:
- What were you hired to do? How was success measured?
- What are you most proud of in this role? What were the numbers?
- What were your mistakes or low points? What did you learn?
- Who was your boss? What would they say were your strengths and weaker areas?
- Who did you work with or manage? How would they describe you?
- Why did you leave?
Keep the order the same each time. Candidates settle into the rhythm by the second job, and the answers get more honest as they go.
How can VC talent teams teach founders to run deep-dive interviews?
Give founders a one-page guide, run a mock interview with them, and sit in on their first real one. Then debrief together right after. Founders learn the method fastest by practicing it on a live hire, so offer the help when an important search opens, not as a generic workshop.
Timing matters most here. A workshop on interviewing in a quiet month gets polite attendance and then gets forgotten. The same help offered the week a founder posts a VP Sales role gets used. Watch for the signal (a senior role posted, a hiring plan in a board deck, a hiring struggle mentioned in an update) and reach out then.
A simple teaching sequence:
- Send the guide and the question template the day the search opens.
- Run a mock with the founder playing the interviewer and you playing a candidate, for 30 minutes.
- Sit in on the first real interview as the note-taker.
- Debrief within the hour: what patterns did you both see, and where should the founder have pushed harder?
After two or three hires, most founders run it on their own. Your role shifts to reference calls and a second opinion on the final candidates. For the wider view of what founders need from a talent team, see what portfolio companies need from VC talent teams.