First of all I want to thank you for your informative videos and articles on case interviews strategies.
I have a background in information technologies and have an office visit interview with one of the top 4 consulting firms in the coming week. It is for an IT advisor position.
I have heard that the recruiters ask IT related questions generally based on merger and acquisition cases.
Could you please tell me some of common questions which could be asked in the case interview for such position?
What should be my approach to go about such IT related cases ?
Also how could I present my answers graphically in such type of questions ?
Looking forward to hearing from your end.
I am not very familiar with IT-type cases, so I don't a useful set of experiences to draw from on this.
However, I have been a CIO before and in my experience the essence of technology is 1) understanding the capabilities of what a technology can and can not do, 2) understanding what you need the technology to be able to do, and 3) making trade-off decisions (do we do option 1 or option 2).
- Do we buy or do we build?
- Do we go with Vendor A or Vendor B?
- Do we do it in-house or outsource?
- Do we do it on-shore or offshore?
So a guess would be to expect some kind of case around which decision to go with. The easiest way to solve this kind of case is to create an issue tree based on the key factors that would determine whether one decision made more sense than another.
So if we go with a Vendor A or Vendor B type case, then what you want to decide at the start of the case are the key decision-making criteria.
So the factors might be:
1) ability to meet requirements
2) cost of project
3) time to launch
or something along those lines.
The other type of common technology issue I have seen is technical troubleshooting. This is really just root cause analysis. The problem that is visible is often just a highly visible symptom of an underlying problem that is hard to see.
So an oversimplified example would be: you hit the "power" button on your television remote, but nothing happens, what do you do?
In the manufacturing world, a similar case might be the production line's daily output has dropped from 1,000 units per day to 500 units. You are called in to solve this problem. What do you do?
If you think carefully about these two questions, they are actually the SAME case (though it might not seem that way at first).
The general approach, by the way, is to map out the process in steps, and measure performance at each step. When you do this, you will often find that one step is broken (not all the steps).
So in the case of the remote control, you can start at the last step and work backwards, or start at the first step and move to the last.
If you start at the first step, you would unplug the TV from the wall, plug in a lamp that you know has a working light bulb and see if the outlet has power. If it does, you know the problem is not the power.
Next you plug in the power strip into the outlet and plug the lamp into the power strip. If the lamp works, you know the problem is not the power strip. You keep doing this, working your way up to the remote control and putting in new batteries.
Troubleshooting your TV remote control and troubleshooting a $1 million IT system is essentially the same process. I have done both, and the overall approach is the same.
Again, this is just my best guess. I would recommend asking your recruiting coordinator what kinds of cases they give in the interviews you have coming up.
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:
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.
Tagged as:case interview questions, consulting interviews, sample case interview questions
Case interview tips
Cases can help us assess a candidate across multiple dimensions, and your answers should project clear thinking, practical judgment, and a professional demeanor. Apply this five-step approach while working through the case interview:
- Understand the issue; ask clarifying questions as needed
- Identify the underlying assumptions
- Summarize specific issues and findings
- State your recommendations
- Outline next steps and expected results/impacts
We want candidates to have an effective and enjoyable case discussion so we encourage you to follow the case interview tips below. You are not expected to provide the "right" answer, but rather clearly convey your logic and thought process. Sample case interviews provide examples and mimic an actual case dialogue.
To help you demonstrate your best thinking in the case interview, we encourage you to:
- Take notes throughout the case exercise
- Be sure you understand the case question
- Ask questions, but don't use them as a crutch—we're interested in how you connect the dots, not in painting the picture for you
- Develop and articulate a framework and the initial hypothesis that you intend to explore
- Take time to compose your thoughts–don't just start talking
- Structure your analysis into a clear, logical story
- Walk the interviewer through your thinking and explain your assumptions
- Don't panic—engage the interviewer in a business conversation
- Don't forget that the case interview is an opportunity to learn about a Deloitte project
View our case interview preparation tool for more help in getting ready for your case interview