No answer for an interview question

  • Thread starter Thread starter deleted969405
  • Start date Start date
This forum made possible through the generous support of SDN members, donors, and sponsors. Thank you.
D

deleted969405

Is it common for applicants to have no answer or say something along the lines of "I simply do not know the answer to that question" during an interview? How should you react if you do not have an answer for an interview question? Perhaps a question that is not ABOUT you or your experiences, but one that is purely about your knowledge (tell me about the US healthcare system for example). Would a suitable answer be something along the lines of...

"Honestly, I don't know the answer to that question, but from my experiences and basic knowledge, I have this to say..."

Clearly that's not as good as giving an answer/justifying it, but would the above be a death-sentence and an automatic R? If not, what are ways to minimize freezing up and/or anxiety during, and after, that question is asked?

Or what is the best way to respond to a question that you do not know?
 
would the above be a death-sentence
People do not receive the death penalty for interviewing poorly.

automatic R
Still no. You are not expected to know everything. Just try to give the best answer you can. I would try to avoid qualifying statements such as “based on my limited knowledge” and such. The interviewer knows how little people in your position know, but it isn’t the end of the world. Again, just give the best answer you can. Take a few seconds to think about it before answering.
 
Last edited by a moderator:
Admitting that you don’t have all the answers is not a bad thing. That’s called humility and knowing your limitations. When they ask about a common issue in healthcare they want to see how you think and that you’ve thought about it. They don’t expect you to solve healthcare in a 30 minute interview.
 
Clearly that's not as good as giving an answer/justifying it, but would the above be a death-sentence and an automatic R?
It's okay to first acknowledge your own ignorance on an issue, but still do try to answer the question to the best of your ability. The point of these questions is to see your thought process.
People do not receive the death penalty for interviewing poorly.
I agree neither of the OP's responses are that bad, though some interviewees do interview so poorly to warrant rejection.
 
I read on a previous forum that acknowledging your ‘lack’ of an answer can be followed up with ‘ideas’ to find a more comprehensive answer.
 
They’re looking for you to be able to think on your feet. If you get stuck on something you don’t know the answer to try and form a hypothesis that’s defendable and you’ll be good!
 
“I can’t say I’m an expert on [topic], but I know it’s important and I’m eager to learn more about it as I continue to progress toward a medical career. Based on my current understanding of [topic]...”

Remember that you don’t actually need any hard facts or data to back up your points. In the context of an interview, all you need is anecdotes. You’re not defending a dissertation; you’re just trying to prove that you’re a pleasant, thoughtful human being.
 
Is it common for applicants to have no answer or say something along the lines of "I simply do not know the answer to that question" during an interview? How should you react if you do not have an answer for an interview question? Perhaps a question that is not ABOUT you or your experiences, but one that is purely about your knowledge (tell me about the US healthcare system for example). Would a suitable answer be something along the lines of...

"Honestly, I don't know the answer to that question, but from my experiences and basic knowledge, I have this to say..."

Clearly that's not as good as giving an answer/justifying it, but would the above be a death-sentence and an automatic R? If not, what are ways to minimize freezing up and/or anxiety during, and after, that question is asked?

Or what is the best way to respond to a question that you do not know?
No, it's not common, and you should be able to BS your way through an answer.

We expect people to be able to think on their feet.
 
It's okay to first acknowledge your own ignorance on an issue, but still do try to answer the question to the best of your ability. The point of these questions is to see your thought process.

I don’t mean any disrespect whatsoever, but I had an interviewer last year who had the exact opposite opinion. He strongly believed in the “If you don’t know something then keep quiet” philosophy.
 
I don’t mean any disrespect whatsoever, but I had an interviewer last year who had the exact opposite opinion. He strongly believed in the “If you don’t know something then keep quiet” philosophy.
None taken 🙂 . As I've said before, there's a diversity of opinions among adcoms, and no single response will please everyone. Almost all will appreciate the humility that is shown by acknowledging one's own limitations (though there is a fine line between humility and lack of confidence).

When someone asks these types of questions, they are likely ready to still prompt you for a position afterwards. No one realistically expects solutions to the problems posed (if it was that easy, we wouldn't still be dealing with them today!). Rather, it's to gain insight into an applicant's thought process, guiding principles, and ability to use the information they do have to formulate a reasonable argument. Through these questions, applicants can also demonstrate their listening skills, "teachability", and ability to respectfully disagree with alternative viewpoints -- all necessary skills for a physician to have.

By not engaging with the spirit of these questions (especially if prompted twice), an opportunity is potentially lost for an applicant to showcase these traits. Just my thoughts
 
Last edited:
Top