Management Consultant Interview Questions

"I studied engineering, then spent three years in operations at a mid-sized manufacturer. The part of that job I liked most was a project where I had six weeks to find out why one plant ran slower than the others. I interviewed the shift leads, pulled the maintenance logs, and found that most of the lost time came from changeovers between products. Fixing that was the most satisfying work I've done. Consulting gives me that kind of problem again and again, across different industries, with people who push my thinking. Now feels right because I've got real operating experience to bring, so I can talk to a plant manager in their language, but I'm early enough in my career to learn the toolkit properly."

"Yes, I'm talking to a couple of other firms, and I'd rather be straight about that. What stands out here comes from the three people I spoke to. Each of them described getting real client time early, and one presented to a client's leadership team in her first year. That matters to me, because I learn fastest when I'm in the room. The second thing is your operations practice. My background is in supply chain, and your work there includes helping clients put changes in place, not just handing over recommendations at the end. I want to see my work actually land. Finally, everyone I spoke to named a partner who'd coached them, which tells me the mentoring is real, not a slogan."

"My understanding, from people I've spoken to, is that a junior consultant usually owns one piece of the problem, a workstream. In a normal week that means gathering data from the client, running the analysis in a spreadsheet, interviewing people who do the work, and turning what you find into a few clear slides. There are daily team check-ins where the manager pushes on whether a finding is really an answer, and a regular meeting where the client sees progress. A lot of it is less glamorous than people think: cleaning messy data, fixing charts late in the evening. What makes it worth it for me is that each piece connects to a real decision the client has to make."

"I know some weeks will be long, and I'm fine with that when the work matters. What I've learned from busy periods before is that quality drops when I'm tired and rushing, not simply because the hours are long. So I plan the day around the one or two things that must be right, and I do those when I'm fresh. I protect sleep as much as I can, because a slide I build at two in the morning usually needs fixing the next day. I also check anything going to a client in the morning rather than sending it late at night. And if the load is more than I can do well, I tell my manager early so we can reprioritise, instead of quietly letting something slip."

"I start by playing the question back and asking what success looks like: is the goal profit, market share, or a yes-or-no decision, and by when. Then I ask for a minute to write the structure. I try to split the problem into three or four branches that don't overlap and together cover the whole question, and I tailor them to the case instead of reaching for a stock framework. If the question is whether a hospital should open a new clinic, my branches might be patient demand, the hospital's ability to staff it, the economics, and the risks. Under each I list the few things I'd want to know. Then I say which branch I'd start with and my early guess at the answer, so the interviewer can see where I'm heading."

"I'd give the answer first, because a CEO with two minutes wants the decision, not the journey. Using a coffee chain entry case as an example, I'd say: we recommend entering the new market, starting with a pilot of ten stores in the capital with a local partner. Three reasons. The coffee market there is growing fast, there's no strong premium chain, and our numbers show a typical store paying back in about three years. Two risks. Rents in the best locations are rising, and the partner has never run cafés. Next steps: shortlist sites, agree terms with the partner, and set the numbers that would tell us to expand or stop after year one. Then I'd stop and ask if they have questions."

"Hypotheses are there to be tested, so a wrong one is normal. The real risk is sitting on it. I'd first make sure I'm right: recheck the data and have a teammate test my logic. Then I'd go to my manager the same day and ask to brief the partner quickly, rather than waiting for the weekly review. I'd bring three things: what we assumed, what the data actually shows, and what I think the new answer looks like. That gives the partner something solid to take to the client. In my experience clients respect a team that says it dug deeper and found something different far more than one that bends the evidence. The earlier we reset expectations, the easier that conversation is."

"Profit is revenue minus costs, and since revenue grew, my first guess is that costs grew faster, or the mix shifted toward lower-margin products. I'd split costs into variable ones per item, like ingredients and packaging, and fixed ones, like rent and staff. Then I'd segment. Say the data shows the older stores are steady, but the six stores opened last year are losing money, and ingredient costs rose by about a fifth. That gives two causes: the young stores haven't built their customer base yet, and the chain didn't pass higher ingredient costs into its prices. I'd recommend raising prices on best sellers where customers are least price sensitive, pausing new openings until the young stores break even, and giving each of them a clear target date."

"Fuller planes with falling profit usually means the airline is filling seats cheaply. Revenue per flight is seats times load factor times average fare, plus extras. Load factor is up, so I'd look at the average fare, which airlines track as yield, meaning revenue per passenger kilometre, and at cost per flight: fuel, airport fees and crew. On fares I'd segment by route and fare class. A likely story is that a low-cost rival entered the airline's busiest routes, and the airline answered by releasing many more discount seats. The planes fill up, but the average fare falls faster than passenger numbers rise, and business travellers who used to pay more now buy the cheap seats. I'd recommend limiting discount seats on each flight to protect later, higher fares, and reviewing whether some contested routes are worth flying at all."

"I'd want to answer four things. First, is the market attractive: how many people buy coffee outside the home, is that growing, and is it cafés or mostly home brewing. Second, competition: who the big chains are, how crowded the city centres are, and whether there's a gap, say a premium segment nobody serves well. Third, can this client win there: does the brand mean anything locally, can it source beans and milk reliably, and does it have managers who can run stores abroad. Fourth, the economics and how to enter: what a typical store earns, how long it takes to pay back its fit-out, and whether owning, franchising or a joint venture with a local partner makes more sense. If the market is growing and there's a clear gap, I'd lean toward a pilot in one city with a local partner."

"I'd split it into three questions: is the segment worth being in, can this client win, and what's the best way in. For the segment, the number I care most about is repeat purchase. Lots of shoppers try a plant-based product once, so trial numbers can look healthy while repeat buying stays weak. For the client, its strength is supermarket relationships and shelf space, but it may lack the food science to match taste and texture. So I'd compare building in-house, buying a start-up whose product people already like, and partnering. I'd say no if repeat rates are low, the shelf already has several strong brands cutting prices, or margins would sit well below the core range. In that case, a small stake in a start-up could keep the option open at lower risk."

"I'll split the five million people into three groups, because they get haircuts at different rates. Say one million children and two million each of adult men and women. Men go more often, so I'll assume every six weeks, about eight a year. That's 16 million. Women go less often but for longer appointments, say four a year, which is 8 million. Children, maybe six a year, so 6 million. That adds up to about 30 million haircuts a year. To sanity-check, 30 million over roughly 300 working days is 100,000 a day. If a barber or stylist does about 15 a day, the city needs around 6,700 of them, roughly one for every 750 people, which feels believable. Some people cut hair at home, so this may be slightly high."

"I'd size it from the café's capacity, then cross-check. Say it opens from six in the morning to eight at night, fourteen hours. Seven of those are rush hours, the morning and evening peaks. At peak there are two tills, each serving about one customer a minute, so 120 customers an hour, which over seven hours is 840. In the quieter seven hours, maybe 30 an hour, so 210. That's about 1,050 customers. Some buy for a colleague too, so at around 1.2 cups each I get roughly 1,250 cups. For a demand check, a busy station might see 100,000 passengers a day. If the café sells one cup for every 80 passengers, that's also about 1,250. Two different methods landing close together gives me confidence the answer is in the right range."

"First, the container. A standard 20-foot one is just under six metres long inside and a little under 2.4 metres wide and high, so I'll assume about 33 cubic metres inside. A ping-pong ball is four centimetres across. The easy way is to treat each ball as sitting in its own four-centimetre cube, which is 64 cubic centimetres. 33 cubic metres is 33 million cubic centimetres, and 33 million divided by 64 is roughly 515,000. That's the count if you stack them in neat columns. But if you pour them in and shake the container, balls settle into each other's gaps, and that packing is about a fifth denser. So my answer is roughly half a million stacked neatly, or closer to 600,000 poured in and shaken down."

"First I'd frame the target. Doubling in five years means growing about 15 percent a year, every year, from a standing start, so it probably needs several levers at once. I'd split revenue into members times revenue per member. On members, I'd look at how many join and how many leave each month, because in gyms keeping members is often cheaper than winning new ones. On revenue per member, add-ons like personal training, paid classes and a premium tier. Then growth beyond the current gyms: new locations, corporate deals, or buying smaller local chains. I'd size each lever roughly and stack them. If retention and add-ons get us a third of the way and new sites another third, the gap tells the CEO whether an acquisition is needed or the target should change."

"I'd use three lenses. Cost gives me the floor: what it costs to host and support one firm, because I never want to sell below that. Value gives me the ceiling: if the product saves a small firm, say, twenty staff hours a month, I can estimate what those hours are worth to them, and the price should be a fraction of that so buying is an easy yes. Competitors and alternatives give me the reference: what similar tools charge, and what doing it in spreadsheets really costs. Then I'd pick a structure. Small firms like predictable bills, so a flat price per firm with two or three tiers based on the number of clients may beat charging per user. Finally, I'd test it with real firms before fixing it."

"I wouldn't answer yes or no straight away, because matching a price cut is expensive. If the cut takes a quarter off the client's margin on each tonne, it needs to sell a third more tonnes just to earn the same profit, and in a commodity market that rarely happens. So I'd ask why the rival cut. If it has a newer plant with lower costs, that's a price war we'd lose. If it has spare capacity after losing a big contract, the cut may not last. Then I'd check who's leaving. Large builders buying on price may go, but smaller contractors may care more about reliable delivery. My likely answer is to match only for the large accounts we can't afford to lose, and hold price elsewhere while competing on delivery and credit terms."

"I'd start with why the bank wants it. If the goal is quick loan approvals for small businesses, I'd check the target really does that better than the bank could build it. Then I'd look at the fintech on its own: how fast it's growing, how its loans have performed through a tough period, and whether its technology can scale. Next, synergies. The bank has cheaper funding and lots of customers, so there's real upside, but I'd be sceptical about timing, because integration often takes longer than planned. Then price: does what the bank pays still leave value once realistic synergies are counted? Finally, culture. If the founders and engineers leave after the deal, the bank has paid for something that walks out the door. I'd compare all of this against simply partnering."

"With one week, I'd focus on what decides the investment. First the market: is demand for dental care growing, and is it fragmented, with lots of single-dentist practices, because that makes a buy-and-add strategy possible. I'd also check the rules on who can own clinics, which differ by country. Second, the target: profit per clinic, not just the total, and how much depends on a few dentists. If the best dentists own the patient relationships and could leave, that's the biggest risk. Third, the value plan: buying smaller clinics, sharing purchasing and booking, and filling empty chair time. Fourth, the exit: who would buy this in a few years, a larger group or another fund. I'd give the firm a one-page view by midweek so they can tell me where to dig deeper."

"In my last role I led a project to cut the time it took to close the monthly accounts, and the people doing the work sat in three different teams, none reporting to me. My first step was to ask each team lead what annoyed them most about month-end, so the project solved their problems too. Then I mapped the whole process on a whiteboard with them, which showed that most delays came from teams waiting on each other. I set up a short daily check-in during close week and gave each team one clear change to own. Within three months, the close went from ten working days to six. What I learned is that people commit when they can see what's in it for them."

"The one I'm proudest of is from my final year at university. Our student society ran a charity event that had lost money two years in a row, and I took over as treasurer. I went through three years of spending and found two things: we were paying for a venue far bigger than we needed, and most tickets sold in the last week, so we never knew what to plan for. I negotiated a smaller venue, switched to early-bird tickets to bring sales forward, and got two local businesses to sponsor the drinks. That year the event raised more for the charity than the two years before it combined. What I'm proud of is finding the real cause in the numbers rather than just cutting everything."

"On a group project at business school, we had to recommend whether a local bike shop should start renting e-bikes. My teammate wanted to survey a few hundred customers first. I thought we didn't have time and should use the shop's records of rental enquiries instead. Rather than argue it out, we agreed on what we actually needed to know: would enough people rent to cover the cost of the bikes. We realised the enquiry records answered part of it, and a short survey of fifty customers in the shop would cover the rest. We did both in a week. The recommendation was stronger for it, and we worked well together for the rest of the term. Most disagreements get easier once you agree on the question."

"I'd talk to them first, privately and without accusing them. Something like, I've noticed the hand-offs slipping and it's squeezing my part, is something going on? Often they're overloaded, stuck on a hard piece of analysis, or dealing with something personal. Then I'd see what I can do: agree clearer hand-off times, take a piece off their plate if I have room, or help with the part they're stuck on. If it keeps happening and the client work is at risk, I'd tell our manager, but I'd frame it as a workload problem to solve, not a complaint about a person. And I'd tell my teammate I'm doing it, so it doesn't feel like I've gone behind their back."

"In my first job, my manager told me my updates were too long. I'd walk through everything I'd done, and she'd have to dig for the point. It stung a bit, because I thought I was being thorough. But she was right. I started writing the answer as the first line of every email, with the detail underneath for anyone who wanted it, and I'd practise a two-sentence summary before meetings. A few months later she started forwarding my updates straight to her own boss, which told me it had worked. Since then I ask for feedback at the end of every project, and I try to pick one thing to change, not five."

"At my last company our sales director was convinced we should drop a product line because its sales had fallen. I was asked to pull the numbers, and I noticed the line was small, but customers who bought it spent much more across our other products and stayed with us longer. Before the big meeting, I went to see him on his own and walked him through it, starting with his concern about falling sales so he knew I'd listened. I'd also checked the numbers with finance, so he could trust them. He asked good questions, and in the end he proposed keeping the line but trimming it to the best sellers. Letting it be his proposal mattered more than being proved right."

"In my second year as an analyst I built a forecast showing one region beating its target. Two days after I sent it to my manager, I spotted that I'd counted one big order twice, and the region was actually behind. I went to my manager straight away, before she used it, told her what had happened and gave her corrected numbers the same afternoon. It was embarrassing, but she used the right version in her meeting. After that I started a simple habit: every model I build gets a check tab that ties the totals back to the source data, and for anything important I ask a colleague to spend ten minutes trying to break it. I haven't sent a wrong total since."

"At my last company, the operations head had three days to decide whether to add a second shift at a warehouse before the busy season. We had no forecast by product, only last year's total orders. I used last year's weekly pattern, adjusted it for this year's growth so far, and checked it against what our two biggest customers said they planned to order. That showed we'd run out of capacity in about the fourth week. I recommended starting the shift, but hiring on short contracts so we could scale back if orders came in lower. I was clear that I was fairly confident, not certain, and I named the weekly number that would tell us early if we were wrong. The shift turned out to be needed."

"First, I wouldn't argue in the room. I'd thank them and ask what specifically doesn't match what they see, because they often know something the data doesn't show, like a one-off order or a change in how something is counted. I'd write it down and promise to come back by a set time. Then I'd genuinely test their point. If they're right, I'd correct it and say so openly, which usually builds trust. If the analysis holds, I'd go and see the executive before the next meeting, walk through the numbers together, and ideally ask one of their own people to check the source data with me. Either way, the goal is that they trust the final answer, not that I win the moment."

"First I'd make sure the finding is watertight, because it'll be tested hard. Then I'd raise it with my manager, and we'd plan to take it to the sponsor privately before any group meeting. Nobody senior should hear bad news about their own area for the first time in front of their peers. In that conversation I'd lead with facts and causes, not blame. For example, the division's costs rose because it took on work other units dropped, not because people were careless. And I'd bring a way forward, so the sponsor can present the fix as their own plan. What I wouldn't do is water the finding down to keep them happy. I can change how it's said, but not what it says, or the project loses its value."

"I'd first try to understand why. Usually it isn't resistance, it's a busy person with a vague request, or someone worried the data will make their team look bad. So I'd go and see them in person, explain exactly what I need and why, and cut the request down to the minimum. Often I'd offer to sit with their analyst and pull it together. If they're worried about how it'll be used, I'd explain that we're looking at processes, not judging individuals. Meanwhile I'd start with proxies so Friday isn't at risk. If nothing has moved by Wednesday, I'd tell my manager, who can raise it with the client's project lead. I'd rather escalate through the right channel than go over the person's head myself."