Search across courses, lessons, cases, drills, coaches and more.
I can usually get the math right, but when I explain every step out loud I sound slow and mechanical. How much of the calculation should I actually verbalize in a case interview?
Sometimes an exact calculation would take time, but a quick estimate seems enough to make the decision. How do I know when approximation is acceptable, and how much error is reasonable before the estimate becomes misleading?
Mayank G.CoachApproximation is acceptable when the case needs direction rather than precision, but you should make the level of accuracy explicit. The estimate must still be good enough to support the decision.
If I calculate something quickly in a case, is it okay to spend a few seconds checking it by reversing the operation, or does that look too slow?
Mayank G.CoachYes, a quick sanity check is useful when the calculation materially affects the recommendation.
I get thrown off when a division gives something like 33.333% or 16.667%. Should I keep carrying decimals, round immediately, or tell the interviewer what level of precision I am using?
Mayank G.CoachUse the level of precision the business decision actually needs. In most case calculations, carrying many repeating decimals creates extra work without improving the conclusion.