Hypothesis Statement in Interviewer-Led Interviews

Question:

Quick question: when is the best time to do the synthesis + hypothesis combination in interviewer-led interviews? I know that you would normally do it after closing each branch/moving to the next framework in candidate-led cases, but what about the interviewer-led cases? Do you do it before each new question is asked? After? At another interval? I tried to do the synthesis + hypothesis combination in a few of my practice interviews, but it seemed very forced, e.g.:

Me: "We know that the market conditions are favorable for McDonald's to enter region X, so my hypothesis is that McDonald's should enter, however I would like to test the hypothesis by looking at the risks."

Interviewer: "No, let us discuss the products with which  McDonald's should enter region X."

The type of example I said occurs with almost all the hypothesis statements I make in interviewer-led cases.

So, when would you recommend to do the hypothesis statement? Would you recommend it at all for interviewer-led cases?

My Reply:

For an interviewer-led interview, you do not want to force it. The time to do it is typically at the beginning and anytime they say something like, "what factors would be important in this decision..." or "what are the key issues..." or "how would you approach this problem..." or "how would you structure this problem"... or "how would you determine what makes sense here..."

Within the interviewer-led interview, this often comes up in the  first 5 - 10 minutes of the interview. After that, the questions asked are not problem-structuring questions, but rather "point" questions that are super specific. In those cases, you do not state a hypothesis, you just answer the specific question.

Also in an interviewer-led case, sometimes the interviewer will tell you or imply the hypothesis they want you to prove. In those cases, it is not necessary to restate the hypothesis (which conversationally can feel forced). Instead, silently think to yourself what's your hypothesis and then structure it.

The main point of the hypothesis isn't to say it, but rather to force yourself to make sure your structure will actually prove or disprove the hypothesis. Too many candidates just list a bunch of factors of things that might kinda, sorta be a little important... without ever critically thinking if each factor can logically prove or disprove the hypothesis. This leads to extremely inefficient problem solving.  Now I err on having candidates state the hypothesis out loud, not because the interviewer needs to hear it, but because the candidate needs to be reminded of it -- so the rest of the process in the case goes more smoothly.

As for the synthesis, at the end of each question, it is useful (but probably not mandatory) to tie your answer back to the specific question the interviewer just asked, to the overall question the client was concerned about in the entire case. It can be just a sentence or two, just to show that you still remembered the overall objective the client had in mind and didn't get lost in the details.

Give that a try and let me know if it feels more natural for you, or if anything else seems forced. It should definitely not be forced ever.

Additional Resources

If you found this post useful, I suggest becoming a registered member (it's free) to get access to the materials I used to pass 60 out of 61 case interviews, land 7 job offers, and end up working at McKinsey.

Members get access to 6 hours of video tutorials on case interviews, the actual frameworks I used to pass my interviews, and over 500 articles on case interviews.

To get access to these free resources, just fill out the form below:

First Name *
Email *

Note: All registrations require you to confirm your email address.
Please type your email address carefully, entering your email also subscribes you to my Case Secrets Email Newsletter.

mail
Facebookgoogle_pluslinkedin
0 comments… add one

Leave a Comment