Smart-and-gets-things-done is a hiring heuristic from Joel Spolsky's 2000 essay “The Guerrilla Guide to Interviewing”. Spolsky argued that the only two things that matter when hiring a software developer are whether they are smart and whether they actually get things done. All other interview criteria are either proxies for these two properties or irrelevant.

The “smart” criterion filters for reasoning ability: the capacity to understand complex systems, debug novel problems, learn new domains, and find non-obvious solutions. The “gets things done” criterion filters for execution: someone who is smart but produces nothing is not useful on a team.

The heuristic is sometimes used as a critique of over-structured hiring processes. A candidate who passes multiple algorithmic coding interviews and system design rounds may be smart but not particularly oriented toward shipping. Conversely, someone with an impressive portfolio of shipped work demonstrates “gets things done” directly.

The phrase “smart-and-vapid” is used for the failure mode: a developer who is visibly intelligent in conversation — articulate, knowledgeable, full of ideas — but produces little actual output. The ideas are good; the execution never materialises. This pattern is common enough to have a name because it is easy to be impressed by verbal intelligence in an interview without noticing the absence of shipped work.

The practical corrective is to interview for demonstrated output: ask about specific things the candidate built, decisions they made, tradeoffs they navigated — rather than abstract reasoning puzzles alone.