> Unless the job is mostly giving presentations, it seems like its optimizing for the wrong thing. Technically speaking, if we're in an interview to "optimize

> Unless the job is mostly giving presentations, it seems like its optimizing for the wrong thing. Technically speaking, if we're in an interview to "optimize for the right thing", then we would just have them come in and type. But we all know that's also optimizing for "the wrong thing" despite it being what we do physically day in and day out. This is because you _CAN'T_ "optimize for the right thing" in an interview. It's not possible and this needs to be acknowledged. Therefore you go for something else. Anyone who is a software developer can listen to a 5-10 minute presentation from another developer and start forming general, broad opinions. They can then start asking questions afterwards to help clarify those opinions. But the Q&A also has another purpose. Way too often interviewers will come to conclusions that don't follow (non-sequitur). I once had someone tell me they didn't feel I would be a team player because I told them as long as I had headphones, open office would be ok. The main difference I've found between business people and technical people is that business people will ask clarifying questions. The Q&A sets the expectation for the _INTERVIEWER_ to ask clarifying questions.