I generally agree with a lot of what's suggested - incremental problems, open-ended questions, conversational tone - but don't think this post describes particu

I generally agree with a lot of what's suggested - incremental problems, open-ended questions, conversational tone - but don't think this post describes particularly effective ways of doing them. And while I disagree on the value of introversion as a indicator of engineering skill, the suggestions here seem worse for introverts than the "standard" google-type interview, IMO. Leaving information out, or railroading apparent open-ended questions down to a single thing (like in the SQL example) could easily frustrate and confuse someone, especially if they're not comfortable with challenging an interviewer, but feel more like "they asked me about this thing, but then left out a bunch of important details" or "they asked me about performance overall but then didn't care about anything I knew about performance outside of SQL."