Skip to content
All insights

Insights

How to tell someone who did the work from someone who talked about it

A good interview can make proximity sound like ownership. These questions bring the conversation back to what the person actually built and decided.

Keith Anderson, Founder4 min read

Some candidates interview beautifully. They describe the project, the stakes, and the outcome in clean sentences. That skill is real and useful. It is also not the same as having done the work.

The gap shows up after the hire, when the work gets specific. The best way to close it is to make the interview specific too.

Ask for the moment before the decision

A project summary usually starts after the choice was made. Go earlier. What were the options? Who disagreed? What did they know at the time, and what did they get wrong? Someone who was in the room can describe the uncertainty. Someone repeating the outcome usually cannot.

Then ask what they personally did next. Not the team. Not the org. Them. A simple follow up works: "What part of that was yours?" It is not hostile, and it gives an honest person room to be precise about where their work ended and someone else's began.

Listen for tradeoffs, not adjectives

  • What did they cut to make the date, and who noticed?
  • What broke after launch, and how did they find out?
  • Which part of the system would they rebuild differently now?
  • Who had to approve the change, and what did that cost in time?
  • What did they hand off, and how did they know it was ready?

Answers with tradeoffs tend to be shorter and less polished. That is a good sign. Real work leaves a trail of compromises, and people who did it remember the compromises because they had to live with them.

Check the references with the same questions

Reference calls often turn into a character check. Make them a work check instead. Ask the reference what the candidate owned, where they needed support, and what changed because of them. Ask for one thing they would want the next team to know. The answers should line up with the interview, not repeat it word for word.

Hire for the trail

Clear communication is worth hiring. Proximity to important work is worth something too. But the trail matters more: decisions made, problems found, handoffs completed, and the willingness to say plainly what was theirs. That is what shows up on a Tuesday six months in, when the story is over and the work is not.

Keith Anderson, Founder

TechStarsGroup

Connect on LinkedIn

Next step

Have a role that needs to move?

A 30 minute conversation about the role, the gap, and whether the market can support the hire you have in mind.