Week 25 Day 2: How to Spot a Finisher in an Interview

Ask a candidate to walk you through a project from start to finish. Listen for where they spend their time in the narrative. Starters will spend 80% of the story on the beginning: the problem they identified, the vision they articulated, the team they assembled, the early wins. They will skim past the ending or describe it in vague terms. Finishers will spend time on the end: the final testing phase, the last-minute scope decisions, the deployment complications, the documentation nobody wanted to write. The narrative distribution tells you which part of the work they value.

Here are three interview techniques for spotting finishers. First -- the last 10% question: 'Describe the last two weeks before your most recent project shipped. What were you doing day to day?' A finisher will describe specific, tedious work: triaging the last bugs, writing release notes, coordinating with stakeholders on launch timing, handling the edge case that surfaced during final testing. A starter will describe this period in general terms or skip it entirely. Second -- the boring middle question: 'What was the most tedious part of the project, and how did you get through it?' A finisher has a detailed answer because they lived in the boring middle. They can describe specific days when the work felt pointless and what kept them going. A starter will struggle with this question because they left before the boring middle ended. Third -- the multi-project test: 'Walk me through the last three projects you worked on. For each one: did you start it, did you finish it, and how long was the gap between the two?' A finisher has a consistent pattern of completion. A starter has a consistent pattern of handoffs -- they started the project, then 'transitioned to another opportunity' before it shipped. One handoff is normal. Three handoffs is a pattern. I weight finisher evidence heavily in my hiring decisions. I would rather hire someone who has finished five mediocre projects than someone who has started ten impressive ones.

The finisher detection methodology draws on research in goal attainment and task completion. Research by Gollwitzer (1999) on 'implementation intentions' demonstrates that the gap between starting and finishing is mediated by the specificity of execution planning -- individuals who can articulate the specific steps needed to complete a task are 2-3 times more likely to actually complete it. The 'last 10%' focus is supported by research on the 'project completion effect' (Kivetz, Urminsky, and Zheng, 2006), which shows that motivation and effort allocation change dramatically in the final phase of a project, with completion-oriented individuals increasing effort as the end approaches while abandonment-prone individuals experience 'goal disengagement' (Wrosch, Scheier, Miller, Schulz, and Carver, 2003). The multi-project consistency check reflects what personality psychologists call 'cross-situational consistency' (Mischel and Shoda, 1995) -- the principle that the best predictor of future behavior is the consistent pattern across past situations, not the single best instance. Research by Steel (2007) in a meta-analysis of procrastination and task completion found that 'task aversiveness' -- the experience of a task as boring or unpleasant -- is the strongest predictor of non-completion (r = -0.40), and that individuals who complete aversive tasks do so through what Baumeister and Tierney (2011) call 'willpower as a practiced skill' rather than willpower as an innate trait.