Your interview question just died: ask what breaks
A candidate can have Claude answer a how-to question in 30 seconds. Ask what broke instead: only someone who has spent real hours in the tool can answer.
"Build me an email waterfall." The candidate has Claude do it in 30 seconds. Your interview question just died.
Garrett Wolfe ran more than 30 interviews to hire GTM engineers at OneGTM. His finding: procedural questions no longer test anything.
He no longer asks how to do something. He asks what breaks. Where does Clay give out? What errors have you run into in Claude Code?
Only someone who has spent real hours in the tool can answer. The others recite.
He also has this line, which I find very accurate: some of the worst candidates he saw had the most certifications.
Then comes a paid trial, on real tasks, with one candidate at a time.
It applies well beyond GTM engineers. For an engineer, the right question is no longer "implement a cache." It's "tell me about the last time a cache failed on you in production."
And often, the answer is already written down somewhere: in an issue, a PR, a public post-mortem.
