Consulting Interview Guide

Framework — Clarify -> split profit -> segment -> diagnose driver -> recommend

First clarify the objective: restore profit, understand root cause, or decide whether to close locations. Ask about geography, timeframe, whether decline is same-store or total chain, and whether revenue or margin changed. Structure the problem into revenue and cost. Revenue can be broken into price, traffic, average order size, product mix, and channel mix such as dine-in, takeout, and delivery. Costs can be broken into food cost, labor, rent, utilities, delivery platform fees, marketing, and overhead. I would segment by store, region, daypart, customer type, and channel. If profits declined mainly in delivery-heavy stores, platform fees and packaging costs may be the issue. If traffic fell across all stores, demand, competition, pricing, or customer experience may be driving it. If revenue is flat but margin fell, input costs or labor efficiency may be the driver. Recommendation depends on root cause. If food costs rose, renegotiate suppliers, adjust menu mix, or selectively raise prices. If traffic fell due to competitors, improve local marketing or menu differentiation. If delivery is unprofitable, change delivery pricing or channel strategy. I would include risks such as customer pushback from price increases and operational complexity.

Framework — Route economics -> network value -> alternatives -> recommendation

I would not decide based only on route-level profit. Airlines have network effects: an unprofitable route may feed profitable connecting flights, preserve airport slots, support loyalty customers, or serve strategic markets. Start with route economics: passenger volume, ticket price, load factor, revenue mix, cargo revenue, variable costs, aircraft utilization, fuel, crew, landing fees, maintenance, and allocated fixed costs. Separate avoidable costs from allocated overhead because cutting the route may not remove all costs. Then evaluate strategic value: connecting traffic, competitive presence, corporate contracts, loyalty impact, airport slot constraints, and alternatives for aircraft deployment. If the aircraft can be redeployed to a more profitable route, opportunity cost matters. Recommendation: cut the route only if it is unprofitable on an avoidable-cost basis, has limited network or strategic value, and aircraft capacity can be redeployed more profitably. Otherwise, consider improving schedule, aircraft size, pricing, partnerships, or marketing before exiting.

Framework — Price, mix, variable cost, fixed cost, productivity

If sales are stable but margins are declining, revenue volume may not be the problem. I would investigate price realization, product mix, input costs, labor productivity, overhead, discounting, warranty costs, and capacity utilization. Revenue-side margin pressure could come from more discounts, shift toward lower-margin products, channel mix changes, or customers negotiating lower prices. Cost-side pressure could come from raw material inflation, labor cost increases, energy cost increases, supplier issues, freight costs, scrap, rework, or underutilized plants. I would segment margin by product line, customer, geography, plant, and channel. A mix shift can hide inside stable total sales. For example, total revenue may be flat while high-margin products decline and low-margin products grow. Recommendations could include pricing actions, supplier renegotiation, product mix management, SKU rationalization, automation, process improvement, or capacity consolidation. The right answer depends on which driver explains most of the margin decline.

Framework — Population -> coffee drinkers -> frequency -> cups -> price

I would size annual revenue from purchased coffee, not home-brewed coffee, unless the interviewer says otherwise. NYC has roughly 8 million residents. Add commuters and tourists, but to keep the math simple, assume the resident base plus visitors averages to about 9 million people present on a typical day. Assume 60% drink coffee: 5.4 million people. Segment frequency: 30% heavy buyers purchase 1 cup per day, 40% moderate buyers purchase 3 cups per week, and 30% light buyers purchase 1 cup per week. That gives weekly purchased cups: heavy 1.62M x 7 = 11.3M, moderate 2.16M x 3 = 6.5M, light 1.62M x 1 = 1.6M. Total about 19.4M cups per week. Annual cups: roughly 19.4M x 52 = 1.0B cups. If average price is $4, annual market size is about $4B. Sanity check: NYC has dense office, tourist, and cafe demand, so a multi-billion-dollar annual coffee market is plausible. I would mention that the estimate is sensitive to average price and whether we include convenience stores, restaurants, and home coffee.

Framework — EV fleet -> charging demand -> home charging -> public sessions -> charger utilization

Clarify whether we are estimating public charging ports or station locations. I would estimate public charging ports needed for daily demand. Start with EV fleet. Suppose California has about 2 million EVs in the near term. Assume 70% of charging happens at home or work, leaving 30% for public charging. If an average EV needs 40 kWh per week and 30% is public, that is 12 kWh public charging per EV per week. Across 2M EVs, public demand is 24M kWh per week. Assume an average public charger session delivers 40 kWh, so that is 600,000 public sessions per week, or about 86,000 sessions per day. If one charging port can support 6 sessions per day on average after accounting for utilization, downtime, and uneven demand, California would need around 14,000 public charging ports. Then adjust upward for geographic coverage, peak demand, highway corridors, low-income neighborhoods, reliability, and future growth. The answer should be framed as a directional estimate, not a precise infrastructure plan.

Framework — Market attractiveness -> competitive landscape -> economics -> capabilities -> entry plan

I would evaluate five areas: market attractiveness, competition, unit economics, operational feasibility, and strategic fit. Market attractiveness includes population, target households, online grocery adoption, meal kit awareness, disposable income, cooking habits, and growth rate. Competition includes local meal kit players, grocery delivery, restaurants, and supermarkets. We need to know whether the market is underserved or already saturated. Economics include customer acquisition cost, average order value, gross margin, packaging and delivery costs, retention, and payback period. Meal kits often struggle if CAC is high and repeat rates are weak. Operational feasibility matters heavily: supplier network, fulfillment centers, cold chain logistics, delivery density, food regulations, localization, recipes, and customer service language. Strategic fit includes whether Germany can become a beachhead for Europe and whether the company has capabilities that transfer. Recommendation would depend on evidence. I might recommend a pilot in one dense city like Berlin or Munich before national rollout, with clear success metrics around CAC, retention, gross margin, delivery reliability, and repeat orders.

Framework — Acquire -> activate -> retain -> monetize -> expand

I would break subscriber growth into acquisition, activation, retention, monetization, and expansion. Acquisition includes brand, content slate, partnerships, pricing, paid marketing, bundles, and geographic expansion. Activation includes trial experience, onboarding, first content watched, and profile setup. Retention includes content engagement, recommendation quality, release cadence, price-value perception, and churn drivers. Monetization includes plan mix, ad tier, pricing, password sharing policy, and upsell. Expansion includes new geographies, demographics, devices, sports, live events, gaming, or partnerships. I would quantify each lever: subscriber impact, cost, time to execute, confidence, and risks. For example, lowering price may increase subscribers but hurt ARPU. Investing in premium content may reduce churn but require large upfront spend. Partnerships may drive acquisition but reduce margin. The strongest recommendation should identify the highest-ROI lever for the company context. If churn is the main issue, acquisition spend may be wasteful. If awareness is low in a new market, partnerships or localized content may matter more.

Framework — Objective -> customer behavior -> economics -> design -> risks

First clarify the objective: increase repeat purchases, raise basket size, collect customer data, defend against competitors, or shift customers to owned channels. A loyalty program should be judged against that goal. Analyze current customer behavior: purchase frequency, retention, average order value, margin, customer segments, and whether customers already behave loyally. If customers are naturally frequent and price-sensitive, rewards may subsidize behavior that would have happened anyway. Economics include reward cost, incremental revenue, margin impact, breakage, technology cost, fraud, and operational complexity. Design choices include points, tiers, personalized offers, free shipping, exclusive access, or partner rewards. Recommendation: launch if the program creates incremental behavior, improves data capture, and has positive unit economics. Start with a pilot and compare members to a matched control group or randomized rollout to measure incrementality.

Framework — Demand -> capacity -> process flow -> bottlenecks -> interventions

I would start by mapping patient flow: arrival, triage, registration, waiting, provider evaluation, tests, treatment, discharge or admission. Then identify where queues form and whether the issue is demand spikes, staffing, room availability, diagnostics, inpatient bed constraints, or discharge delays. Demand analysis: arrivals by hour, day, severity, ambulance versus walk-in, and seasonal patterns. Capacity analysis: doctors, nurses, rooms, lab/radiology turnaround, specialist availability, and inpatient beds. Process analysis: triage time, time to provider, test ordering, results wait, decision time, and discharge processing. Interventions depend on bottleneck. If low-acuity patients clog the system, create fast track care. If lab turnaround is slow, improve diagnostic workflow. If admitted patients wait for inpatient beds, the ED may be blocked by hospital-wide discharge delays. If staffing mismatches demand peaks, adjust schedules. Success metrics: door-to-provider time, total length of stay, left-without-being-seen rate, patient outcomes, readmissions, staff utilization, and patient satisfaction. Guardrails are clinical quality and safety.

Framework — Define lateness -> segment -> root cause -> intervention -> monitor

First define late: relative to promised window, customer expectation, internal SLA, or regulatory requirement. Then segment late deliveries by geography, route, driver, warehouse, carrier, product type, time of day, day of week, weather, and order size. Root causes could include warehouse pick/pack delays, inventory inaccuracies, routing inefficiency, traffic, driver capacity, unrealistic delivery promises, address errors, failed handoffs, or last-mile carrier performance. I would map the delivery funnel from order placement to fulfillment, dispatch, transit, and doorstep delivery. Identify the largest source of delay and whether it is controllable. If promises are too aggressive, fix ETA logic. If warehouse processing is slow, improve staffing or batching. If routes are inefficient, optimize routing and driver allocation. Metrics: on-time delivery rate, lateness minutes, cost per delivery, failed delivery rate, customer complaints, refund/credit cost, driver utilization, and SLA performance by segment.

Framework — Revenue up, margin down -> price, mix, cost, investment

The immediate inference is that margin has declined. Revenue growth is not translating into profit, so either costs grew faster than revenue, product/customer mix shifted toward lower-margin segments, discounting increased, or the company invested heavily in growth. I would quantify margin before and after if the chart provides absolute numbers. Then segment by product, channel, geography, customer type, and cost category. If revenue grew through promotions, gross margin may be lower. If growth came from a new geography, logistics or launch costs may be high. If revenue came from low-margin products, mix is the issue. The case implication depends on sustainability. If profit decline is due to temporary growth investment with strong customer lifetime value, it may be acceptable. If it is due to structural cost inflation or poor pricing power, the company needs pricing, cost reduction, or mix improvement.

Framework — Round -> structure -> calculate -> sanity-check

I structure the equation before calculating. Then I use round numbers where appropriate, keep units visible, and calculate in steps. For example, instead of multiplying 37 x 4.8M directly, I might round to 40 x 5M for an estimate, then refine if precision matters. I also sanity-check magnitude. If I estimate a coffee market and get $400 per person per day, something is wrong. Consulting math is not about being a calculator; it is about producing a reliable directional answer quickly. If I make a mistake, I correct it calmly. Interviewers care more about composure and structured correction than perfection.

Framework — Answer first -> reasons -> risks -> next steps

Lead with the answer. Do not recap the entire case chronologically. A strong final recommendation sounds like: “I recommend the client enter the German market through a Berlin pilot because the market is growing, unit economics appear attractive, and the company has transferable logistics capabilities.” Then give 2-3 supporting reasons with numbers if available. After that, state risks: competitive response, customer acquisition cost, operational complexity, regulation, or implementation timeline. Finally, give next steps: validate assumptions, run a pilot, negotiate suppliers, collect customer data, or refine pricing. The recommendation should be decisive but not reckless. If the evidence is incomplete, say what decision can be made now and what must be validated before full rollout.

Framework — Problem solving -> impact -> learning curve -> client exposure

A strong answer should be specific and credible. Good themes include solving ambiguous business problems, working across industries, learning quickly, having measurable client impact, and collaborating with high-performing teams. Avoid saying only that you want prestige, travel, exit opportunities, or broad exposure. Those may be true, but they do not show client readiness. Instead, connect consulting to your past experiences: “I enjoyed breaking down ambiguous problems in my strategy internship, working with cross-functional stakeholders, and turning analysis into recommendations leadership could act on.” Then explain why now and why the firm. Tie your background to the role and mention firm-specific reasons such as industry strength, office culture, mentorship model, or client work.

Framework — Context -> challenge -> action -> result -> reflection

Choose a story with real stakes: tight deadline, conflict, unclear direction, underperformance, or changing requirements. Start with the context and why the challenge mattered. Then focus on your actions. Did you align the team around a goal, divide work, resolve conflict, motivate someone, reset scope, communicate with stakeholders, or make a difficult tradeoff? Use “I” for your specific role while still giving credit to the team. Close with measurable result and reflection. Consulting interviewers look for leadership, drive, empathy, and learning. A strong ending explains what you would repeat or do differently next time.

Framework — Failure -> ownership -> correction -> lesson

Pick a real failure, not a disguised strength. The best examples show accountability and growth. Briefly explain what happened, why it mattered, and what you personally could have done better. Then explain how you responded. Did you communicate early, fix the issue, ask for help, change the plan, or repair trust? Avoid blaming teammates, unclear instructions, or external factors. End with a concrete lesson and evidence that you changed. For example, you now align expectations earlier, create risk checkpoints, validate assumptions, or communicate tradeoffs sooner. Consulting firms want people who can learn quickly under pressure.