In a typical Slalom first-round loop of six to eight candidates, two or three lose the room before they finish the structure: they design a national program that the local office cannot staff. The interviewer is not scoring your framework vocabulary. They are asking one quieter question: would I put this person on a client floor in this city for the next four months?
That is the thesis. Slalom sells local delivery with global backing — consultants who live where the work is, plus a partner network — so cases and fit talks reward staffing realism, MVP scope, and client-floor judgment more than MBB-style strategy theatre. After this piece you should be able to close a Slalom-style problem with a sprint plan, a bench math check, and a crisp reason you want this market, not a Sunday-night flight schedule.
What the firm publishes about itself
As of its public "Who we are" page, Slalom describes itself as a business and technology consulting company with 54 local offices and more than 700 technology partners. The same page frames the model as "local soul, global scale": people committed to long-term client success who live where they work, backed by a global network. Treat that as the firm's own positioning, not folklore.
Culture is part of the brand, not a soft afterthought. In April 2024, Slalom announced it ranked #17 on Fortune's 100 Best Companies to Work For list for the ninth consecutive year, citing Great Place to Work survey analysis. That does not tell you the interview scoring sheet. It does explain why loops lean hard on behavioral evidence and why a polished case with the wrong lifestyle signal can still fail.
Recruiting process detail is thinner than prep sites invent. Slalom's candidate privacy notice describes a standard sequence: screen the application, invite to interview, then (if an offer is contemplated) references and/or a background check as permitted by law. Exact rounds, whether you get a classic case, a take-home, a technical deep-dive, or mostly behavioral, vary by market, capability, and role. Your invitation email beats any guide, including this one.
How the interview actually filters
Think in three filters, not four sacred "rounds."
| Filter | What they are listening for | What fails fast |
|---|---|---|
| Market and capability fit | Why this city, why this practice (cloud, data, CX, Salesforce, advisory), why delivery | Prestige travel story; "any office is fine" |
| Problem-solving | Can you scope an MVP, name risks, do simple staffing math | National strategy with no bench or timeline |
| Behavioral / culture | Collaboration under incomplete requirements; client presence; honesty about limits | STAR stories that never touch delivery conflict |
Slalom also publishes how it wants candidates to use AI: prep tools for resumes are acceptable if truthful; live interviews expect unaided answers, and over-reliance on AI for assignments can disqualify. That is a firm rule, not etiquette advice.
Candidate forums talk as if every loop includes a textbook case. That is folklore. Some technology and Salesforce tracks skew technical or portfolio-heavy. Some markets lean take-home plus discussion. Confirm with recruiting. When a case does appear, treat it as a delivery design problem with a local constraint attached.
One practical habit: before you open your structure, ask what the market can actually bench this quarter — skills, contractors, and whether a client product owner exists. That single question signals you understand how Slalom staffs work. If the interviewer cannot answer, state your assumption out loud ("assume five people, two with integration") and keep going. Silent assumptions about infinite talent are how candidates invent floating New York squads.
Ned's scoring sheet (what I listen for)
I have scored hundreds of cases across firms. On a Slalom-shaped problem, my mental sheet looks like this — rough weights, labeled as my estimate, not Slalom's confidential process:
| Dimension | Weight (Ned's estimate) | Pass signal |
|---|---|---|
| Problem framing | 15% | Success metric is time-to-usable outcome and risk, not "best in class" |
| Structure | 15% | Outcomes, integration, buy/build/compose, operating model, staffing |
| Math / trade-offs | 20% | Reproducible numbers tied to delay cost or capacity, not vanity NPV |
| Recommendation | 20% | Phased MVP, what you will not build, next spike this week |
| Local realism | 20% | Bench size, skills, contractors; no flying circus from another coast |
| Client communication | 10% | You can say the 16-week target is fiction if APIs are fiction |
Ned's rule. If your answer still works after you delete the local office and staff the team from New York, you solved the wrong firm's case.
Worked example: Harbor Clinic patient portal (12 weeks)
Prompt. Harbor Clinic is a 14-site outpatient group in your Slalom market. Patient calls about appointments and results have risen 28% year over year. The COO wants a patient portal live in 12 weeks before open enrollment. IT wants a custom React build on the electronic health record (EHR). The vendor that already sells the EHR offers a portal module. Compliance worries about PHI access logs. Your local market can free five consultants: two with EHR integration, one CX, one change, one engagement lead. What do you recommend?
Clarify. Success is reduction in call volume and a compliant go-live date, not "best digital clinic in the country." You may phase features. Local bench is a hard constraint.
Structure (delivery, not 3C).
- Outcomes for week 12: schedule, message provider, view results; what waits (billing, proxies, telehealth)
- EHR integration path and audit logging (the usual 12-week killer)
- Buy vs build vs compose (vendor portal shell + local configuration + change team)
- Operating model: clinic product owner, sprint cadence, compliance in the sprint not after
- Staffing: five people plus contractors; what skills are missing
Math you can reproduce.
Assume 18,000 inbound calls per month related to appointments and results, of which 40% could move to self-serve if the portal works (7,200 calls). Average handle cost is $6.50, so monthly call-cost at stake is about $46,800. An eight-week slip past open enrollment keeps that pipe open for two more months: roughly $94k of avoidable call cost — material, but not the real board story. The real cost is enrollment friction and patient churn the COO already feels.
Custom React on the EHR: $1.9m, 12 weeks, 40% chance integration slips eight weeks (Ned's illustrative risk). Vendor portal module configured on existing APIs: $720k, 8–10 weeks to MVP, less "unique" UX. Custom needs roughly nine people for a safe build; you have five. Contractor fill at $95/hour × 1,200 hours = $114k. That premium is cheaper than an eight-week slip if open enrollment is fixed.
Recommendation. Compose: vendor portal module + local integration and change squad; ship schedule, messaging, and results in 10 weeks; defer billing and proxies. Risk: marketing hates the vendor look. Next step: a one-week API and audit-log spike. If the EHR APIs cannot support results with logging, the 12-week date is fiction and you must say so in week one.
That close is more Slalom than an industry-attractiveness tree.
Where strong MBB-trained candidates leak points
They optimize brand and market entry. They staff a national flying team. They treat agile as a slide deck. They give a crisp recommendation with no sprint plan, no product owner, and no compliance touch inside the iteration. They answer "why Slalom" with work-life balance as the product. Balance may be true for many people; interviewers hear deeper market relationships and delivery presence more cleanly than "I hate airplanes."
Name a local industry without fakery when you can: health systems in Nashville, tech and retail in Seattle, energy in Houston, finance in Charlotte. Fake local color is worse than none.
Prepare like a delivery lead, not a case club president
Practice problems that end in an MVP scope and a team shape. Drill math that converts delay into capacity or cash, not decorative precision. Rehearse behavioral stories about incomplete product ownership, standup conflict, and telling a COO the deadline is wrong.
On CoachNed, start with a five-minute typed rep at /start (no account needed), then run a full voice case at /interview (~18 minutes, seven-score debrief). Use /drills/structure and /drills/math until your close includes staffing and a "what we will not build" line. Everything is open for seven days, no card; then $120 for a recruiting season or $49 a month.
One assignment for tonight
Write a two-sprint plan for Harbor Clinic: sprint goals, roles (including the client product owner), compliance touchpoints, and the demo you will show. Do not write another issue tree. That artifact is closer to what a Slalom interviewer is buying than a perfect MECE map.
Frequently asked questions
Does Slalom always use a case interview?
No. Format varies by market, role, and capability. Some loops are behavioral and technical; some include a take-home or presentation. Treat your recruiter's brief as the source of truth.
How is Slalom different from McKinsey, BCG, or Bain in the interview?
Slalom's public model emphasizes local offices, technology delivery alongside advisory, and long-term client presence in market. Cases and fit talks, when present, lean toward staffing and MVP realism more than pure strategy. Confirm pay and process with recruiting; CoachNed does not publish confidential firm scorecards.
Do I need Salesforce, AWS, or Azure certifications?
They help for matching capability tracks and show delivery intent. Do not claim what you cannot defend in a technical conversation. A honest adjacent project story beats a borrowed cert story.
What does Slalom say about using AI during recruiting?
Slalom's public guidance allows AI help on application materials if they stay accurate, expects live interviews without AI-generated answers, and wants assignments to reflect your own synthesis. Ask Talent Acquisition if anything is unclear.
Is CoachNed affiliated with Slalom?
No. CoachNed is independent and not affiliated with Slalom or any firm named here for interview practice. Confirm current process and compensation with Slalom recruiting.
Sources
- Who we are | Slalom — 54 offices, 700+ technology partners, local-soul / global-scale positioning. Checked 2026-09-24.
- Fortune 100 Best Companies to Work For announcement | Slalom — #17 ranking in 2024, ninth consecutive year. Checked 2026-09-24.
- Candidate Privacy Notice | Slalom — application screen, interview, then references/background check as permitted. Checked 2026-09-24.
- What you need to know about AI when applying to Slalom — firm rules on AI in applications vs live interviews and assignments. Checked 2026-09-24.
- Locations | Slalom — local-market footprint across countries. Checked 2026-09-24.