> "What the candidate has done in the past" is always a good one A candidate answering this question well is a necessary but not sufficient condition to being

> "What the candidate has done in the past" is always a good one A candidate answering this question well is a necessary but not sufficient condition to being a good hire. Some people can deftly spout bullshit about their prior experience, coming across as a high-level expert but completely lacking in any low-level ability. I once interviewed a candidate who initially impressed the whole interviewing panel with a presentation on a complex machine learning model they supposedly developed, yet subsequently couldn’t answer extremely basic questions in probability and statistics. This is exactly the phenomenon described in Jeff Atwood’s famous FizzBuzz article, “Why Can’t Programmers.. Program?” [0] The reason senior programmers can’t solve FizzBuzz is because they’ve only ever been hired based on their ability to bullshit about their past projects, without any assessment of their ability to actually code. [0] https://blog.codinghorror.com/why-cant-programmers-program/ https://blog.codinghorror.com/why-cant-programmers-program/