Hi there,

My response is going to be based on my personal experience and may or may not be useful for you or others reading this.

I had some successful interviews in industry post-exiting McKinsey and I never prepared my responses to such questions in line with any framework. The reason being two-fold:

• NO NEED: My time at McKinsey helped me become a very comfortable and effective communicator who can tailor responses on the spot, depending on what the situation calls for. Being overly prepared typically hurt my ability to communicate instead of helping it. Especially because nobody ever asked me “tell me about this project x on your resume”. However, that's a very subjective experience and it may be very different for other people.
• CONSTRAINT: I was typically asked about projects, or brought them up myself, in the context of discussing a specific topic e.g. change management from a leader's perspective. In that case, you don't want to give a rehearsed answer for project x because it's limited in its impact. Instead, you want to pick relevant bits and pieces from your various experiences and reassemble them in a way that portrays you as an experienced practitioner in this field.

BOTTOM-LINE: Ask yourself whether you really need to prepare this in such a systematic way, which may well be, or whether you have indeed developed your communication skills to the extent where such preparation becomes superfluous.

Hope this helps a bit. Best of luck!

Moritz

_______________________________________________________
>> Need a specialized McKinsey coach & mentor? 
     See my full profile 
>> Need real McKinsey cases?
     Zero Carbon Mine (hard)
     Car Convenience (Intermediate + brand new)

(editiert)

Hi there,

Ultimately, the right way needs to be spoken. As in, I need to actually hear you say it!

Please don't generically do STAR/SCAR methodology as you see some other coaches recommending.

Why?

They are NOT asking for a story.

Rather, answer like a normal human being!

Summarize the projects. If you can categorize and group them, give an overview of what each was about, and aim to highlight the key skills required/responsibilities, then you've done well.

The answer is inherently going to be different for each person though….ultimately, be clear/concise, and put yourself in a good light! Of course, maintain the confidentiality required.

Happy to help you craft your specific answer!

Hi,

Be prepared to tell about your projects in greater detail if asked to elaborate on a certain point, e.g. what were the names of the participants, the exact words you or they used getting getting a point across, the actual motivation you had taking a certain course of action etc.

Ideally, if you prepare three types of FIT stories:
1. Mini FIT: a short overview or a sales pitch of your achievements (20-30 seconds per story);
2. Standard PEI - around 2 minutes per story;
3. Expanded FIT - a 4-5 mines per story for a deep dive into your experiences with the exact names, reasoning, thoughts, as described above.

Good luck!
Nick

Hi,

One good option is to use the SCAR approach:

S: Situation, context → 10% of total duration
C: Complication → 20% of total duration
A: Action & thinking  → 50% of total duration
R: Results  → 20% of total duration

Then to keep confidentiality, juste name the industry and the function.

Cheers,

Hi!

Yes, confidentiality is important. So refrain from mentioning client names. 

In terms of structure, start by discussing the context of the project, then the main problem you were working on, then the actions that you individually took (basically try to identify your individual contribution) and then the result. Lastly, it's always good to identify 1-2 learnings you had from this experience. 

Good luck!
Cristian

———————————————

Practicing for interviews? Check out my latest case based on a first-round MBB interview >>> CodeWave  

Hi there,

You received some great feedback already from other coaches.

One thing I would add is to be observant of your interviewer early on the interview. This is coming from actual experience passing my 2nd round of interview at McKinsey. Some interviewers might prefer more structure vs others who might come across might laid back (they say to not fall into that but I think the human factor is essential). Use your intuition to your best.

Cheers,

Aude Augias

Just as you would do in a normal conversation. Make sure to give some context, mention industries, your role and the impact achieved. Use direct communication without loosing yourself in details if you are not asked to do it.

Best,

Alberto

—

Check out my latest case based on a real MBB interview: Sierra Springs