Interviews rounds scoring protocol

Hi,

Cases are assessed holistically across several dimensions: structuring, quantitative analysis, business judgment, communication, synthesis, and overall interaction. The recommendation is important, but one weak conclusion does not automatically mean rejection, especially if the rest of the case was strong.

To pass the process, you need to pass each individual interview. It is better to perform consistently across the board than to be a superstar in one interview and mediocre in another.

Hope this helps,
FRanco

PS For future recommendations, return explicitly to the client’s objective, answer it directly, support your answer with the decisive evidence, and then mention risks and next steps

Hi,

From what you describe, one weak final recommendation does not automatically mean you failed the interview, especially if your structure, analysis and overall case performance were strong. Interviews are usually assessed across several dimensions, not just on the final answer.

There is also an important nuance: how you reacted when the interviewer challenged you or gave you information that went against your recommendation can also matter. If you were able to quickly recognize the point, adjust your reasoning and understand where you had overweighted the broader economic impact versus the client’s explicit objective, that can still work in your favor because it shows flexibility and coachability.

For your next interview, I would keep two things in mind:

• Always clarify the client objective. If it is not clear whether something is a hard requirement or simply a preference, ask. Asking is always a good idea when the answer could materially change the logic of your recommendation.
• If the requirement is hard, your recommendation needs to be clear and direct. If it is not a hard requirement and there is room to consider other factors, you can still give a clear recommendation first and then add the nuance of “not yet” or “not under the current design.”

But be careful with that nuance: a very common mistake is adding so many conditions that the interviewer is no longer sure what you are actually recommending. Clear recommendation first, nuance second.

Best,
Carlos

Hi there,

You're rated hollistically. Not nailing one element of the case is ok if you perform well in the rest. There's so much more to a case performance than just a recommendation.

Let's focus on what really matters.

You need to be a strong caser. You need to communicate and think in a clear and structured manner. You need to not let math or exhibits slip you up and you need to drive the case forward effectively.

If I tell you they rate you out of 5 or 50 or 1,000, does it change anything? Or if they all get together for a 3 day summit to make a decision? Nope!

Focus on what matters! I.e., get as good as you can at math, chart/exhibit reading, structured thinking/frameworking, business acumen, clear communication, case leadership.

Just like in a case, you need to focus on what matters here!

Good luck!

An optimal candidate performs strongly across structure, math, exhibits, business acumen, communication, case leadership, and synthesis without one major weakness pulling down the overall performance.

Of course, we can't tell you your odds based on a written description. We'd need to conduct a full mock and assessment to evaluate you hollistically. I recommend working with a case coach to diagnose your performance across the entire case, not just the recommendation.

Also, check out this guide on how to shift your mindset to ace the case, which should help strengthen the business judgment behind your recommendations.

hey there :)

I really wouldn’t assume you ruined your chances. At Tier 1 firms, cases are usually assessed across several dimensions, such as structuring, quantitative skills, problem solving, communication and business judgment. A weak final recommendation can hurt, but it is only one part of the overall assessment.

In your situation, I’d actually take some comfort from the fact that the case itself went very well. The interviewer’s comment about the client ultimately not proceeding may also have been testing whether you could think beyond the numbers and consider the broader strategic or public sector context.

For your next interview, focus especially on making your recommendation commercially grounded: answer the question, explain the key trade off, and mention any important factor that could change the decision. One imperfect recommendation definitely doesn’t automatically mean a rejection.

best,
Alessa :)

Hi there,

I would spend less energy on how the interview was scored and more on what that case was testing, because the detail you gave points at something specific.

A loss of USD 100K over 10 years, on an initiative generating hundreds of millions in revenue, is not a financial result. It is roughly 10K a year on a programme of that size, well inside the rounding error of any forecast you could have built. When the number a case hands you is that small relative to the scale of the decision, that is the signal that the number is not the decision. Your interviewer mentioning that the client rejected it 2 weeks later reads as a hint rather than a footnote.

• Ask what the client is accountable for, not only what they want. A public sector body answers for mandate fit, political exposure, delivery capacity and precedent. None of those sit in the P&L, and any of them can stop an initiative that roughly breaks even.
• Say out loud when the economics are immaterial. Naming the number as too small to decide on is itself the judgment call. Building a recommendation on 10K a year invites the question you were not ready for.
• Recommend, then name the condition. Give the answer, name the 1 factor that would reverse it, and say how you would test it. That closes stronger than confidence on a thin number.

Final comment: This is very unlikely to be a business judgment deficit. Candidates who structure and calculate well tend to arrive at the recommendation with no time left and improvise it. I would decide in advance what your final 2 minutes look like, so the close is something you execute rather than invent.

You cannot estimate your chances reliably from one written description, and firms do not publish the exact scoring protocol for each interviewer. A weak recommendation can matter, but it is one part of the overall performance.

The key issue is the objective. If the client required the initiative to be profitable, even by a small amount, a ten-year loss means the proposal failed the stated condition. The wider economic benefit is relevant only if the interviewer allowed you to trade that against the profitability requirement. That is why clarifying the objective early matters.

For your next interview, use a simple closing sequence: answer the client's question directly, cite the two facts that drive the decision, acknowledge the main risk, and state the next test. If the economics say no, say no. You can then add: “The policy benefits may justify redesigning the initiative, but not approving the current version.”