Most candidates prep "consulting recruiting" as if Accenture Technology, Deloitte Technology, IBM Consulting, and McKinsey share one funnel. They do not. Technology consulting and strategy consulting sit inside the same industry label and run different calendars, different first filters, and different scoring sheets.
The thesis is simple: the interviewer is not grading you on "consulting potential" in the abstract. A tech-practice assessor is listening for applied technical judgment and delivery credibility. A strategy interviewer is listening for structured problem solving under ambiguity. Prep that ignores which sheet is open is how strong resumes still die in round one.
This piece stays inside consulting. If you are weighing consulting against a product or engineering job at a tech company, that is a different comparison. After you read, you should be able to map any open role to the right prep stack in under five minutes.
Two hiring machines, one word on the resume
"Consulting" on LinkedIn collapses two machines. Strategy houses (McKinsey, BCG, Bain, and the strategy arms of the Big Four) hire against a problem-solving case bar. Technology practices (Accenture Technology, Deloitte Technology and related digital tracks, IBM Consulting tech and implementation seats, and similar Big Four tech practices) hire against role-specific technical and delivery bars, with cases used selectively.
The firms' own pages make the split plain. Accenture says interview count depends on the role; some seats get an online activity for technical skills, strengths, or decision-making, with technical assessments typically 30 to 90 minutes in a coding environment inside a window often about 72 hours. IBM Careers lists coding assessments, video assessments, and structured behavioral interviews. Bain and BCG put cases at the center of client-facing consulting hiring. McKinsey pairs personal-experience interviews with problem-solving cases for most consulting roles, sometimes adding Solve.
Same industry. Different first question on the scoring sheet.
Timelines: campus clocks versus role clocks
Strategy recruiting for campus and MBA pipelines still runs on hard intake windows. Schools publish firm deadlines that cluster in summer for full-time roles. MIT Sloan's career office lists Bain, BCG, and McKinsey MFin deadlines in summer 2026 with interview waves tied to each window. Miss it and you wait for the next cycle or shift to experienced-hire.
Technology consulting hiring tracks job postings more than campus calendars. Accenture, Deloitte experienced hire, and IBM fill seats when a practice needs capacity. Deloitte UK is explicit that assessment varies by business area and grade, with a recruiter as the constant. IBM says process length depends on role, response speed, and volume, with no single published timeframe.
| Dimension | Strategy consulting (typical campus / core) | Technology consulting (Accenture Tech, Deloitte Tech, IBM, Big Four tech) |
|---|---|---|
| Application rhythm | Seasonal intakes; apply in the published window | Continuous / role-by-role; postings open when teams hire |
| First filter | Resume + firm assessment (Solve, CCA, aptitude) | Resume + coding, video, or domain screen for many seats |
| Interview center of gravity | Case + fit / PEI | Technical depth + behavioral; case when the seat is consultant-shaped |
| Offer clock | Weeks inside a recruiting season | Weeks to months, driven by hiring-manager availability |
| Reapply cost of a miss | Often next cycle | Often another open req after a cooldown (Accenture: 90 days for the same assessment) |
Ned's estimate from sitting both sides of the table: if you are optimizing one calendar year, strategy campus has fewer shots and a sharper peak. Tech practices give more shots and punish stack mismatch harder.
What the online filter actually measures
Read the invitation. Do not prepare for the test your friend took last cycle.
Strategy-side filters lean on general problem solving. McKinsey's Solve is a gamified assessment of natural problem-solving ability for many consulting roles; the firm says no business prep is required and that results sit alongside the rest of the application. BCG's U.S. associate process sends a Consultant Career Assessment soon after apply (about 30 to 35 minutes, 48-hour window) and invites selected candidates to an online case of roughly 35 minutes. Those tools are built to rank analytical judgment before a human case interview.
Technology-side filters lean on applied skill. Accenture describes technical assessments as evaluating problem solving, logical reasoning, and applied technical knowledge in a coding environment that reflects engineering tasks; scoring is against predefined criteria such as test cases, and a threshold gates interviews. Deloitte UK lists Codility-style coding tests among possible tools for professional hires, alongside technical questions, case studies, and HireVue for some roles. IBM may send a coding assessment for Developer or Data Scientist tracks and a recorded video assessment in some regions before live interviews.
If your first email is a HackerRank or Codility link, case frameworks will not move the needle. If your first email is Solve or a CCA, grinding algorithm puzzles will not either.
Case versus technical: what the sheet rewards
Live interviews diverge even more than the online filters.
Strategy case interview. The interviewer scores structure, quantitative accuracy, insight, and communication on a business problem you have not seen. Bain notes that consultant-style roles may include a case and looks for problem-solving plus role-relevant aptitude. BCG frames the case as problem-solving and analytical skill for client-facing roles. McKinsey's problem-solving interview is a typical client scenario. PEI or behavioral rounds sit beside the case and are scored separately.
Technology interview. The interviewer scores whether you can do the work on Monday. Accenture says each interview is unique to the role's skills. Deloitte lists technical questions, case studies, behavioral questions, and coding tests as possible tools. IBM's entry-level consultant guidance can include a case then a behavioral round for Consultant tracks, while Developer and Data Scientist tracks add coding earlier. For tech seats, expect architecture tradeoffs, stack depth, delivery risk, and explaining complexity to a non-technical client.
Hybrid seats (digital strategy, tech transformation) are two bars, not one soft bar. A tech-flavored case still needs a crisp recommendation; a strategy case that wanders into tools without a decision still fails.
Worked example: one answer, two scorecards
A candidate is asked: "A national retailer wants to move its ecommerce platform to the cloud in 18 months. What would you do?"
Answer A (delivery-native). "I would inventory workloads, classify by criticality, run a pilot on non-customer-facing services, use a lift-and-shift for the catalog, refactor the checkout path for elasticity, set a cutover weekend with rollback, and staff a 12-person squad across cloud, QA, and ops."
Answer B (decision-native). "I would start from the business constraint: peak season is non-negotiable, so the decision is sequencing, not whether cloud is fashionable. Split the 18 months into three waves by revenue-at-risk. Wave 1: non-checkout services to prove reliability. Wave 2: catalog with a dual-run. Wave 3: checkout only after error budgets clear. Cost target is a 20 percent run-rate reduction by month 24, with a hard stop if latency at peak rises more than 10 percent."
Score them the way each room actually scores.
| Dimension | Strategy interviewer (typical) | Tech interviewer (typical) |
|---|---|---|
| Structure | B wins: decision criteria and waves | A is fine; B still better if tradeoffs are explicit |
| Technical depth | Optional color | A wins if the stack and cutover plan are credible |
| Business math / risk | B wins: latency and cost thresholds | Useful but secondary to feasibility |
| Recommendation clarity | B wins | Both pass if ownership is clear |
| Likely outcome | A gets "too executional"; B advances | B advances if tech specifics hold up under probe; A advances if probes land |
Same prompt. Opposite failure modes. Strategy rooms punish tool lists without a decision. Tech rooms punish slide logic that cannot survive a "which service fails first?" follow-up.
Ned's rule. Prepare for the filter that kills you first. If the invitation is a coding IDE, own the IDE. If the invitation is Solve, CCA, or a case loop, own structure and math. Dual-tracking both without choosing which sheet is open is how candidates split their prep and lose both.
How to choose a prep stack in one sitting
Use the job title and the invitation, not the firm logo.
| Signal on the posting or invite | Primary prep | Secondary prep |
|---|---|---|
| "Case interview," "problem-solving interview," PEI language | Cases + fit stories | Light domain color |
| Coding / HackerRank / Codility / "technical assessment" | Timed coding + system design for the stack | Behavioral STAR with delivery outcomes |
| Architecture, cloud, ERP, cyber, data engineering title | Domain depth + architecture tradeoffs | Short business case practice |
| "Technology consultant" / "digital" with client-facing language | Hybrid: one case per week + one technical deep dive | Why this practice, not generic "why consulting" |
| Strategy / S&O / generalist associate or consultant | Full case volume + PEI | Skip LeetCode unless the invite says otherwise |
IBM's entry-level consultant blog is the primary signal for hybrid seats: case comfort, probing questions, and a sharp why-this-firm answer. Accenture's technical FAQ is the match for engineering seats: approach and solution quality in a coding environment, with interviews still required after the score.
Practice this week
Pick one open role and write the scoring sheet before you open a prep book.
- Copy the invitation language into three lines: first filter, live interview type, what "good" means.
- Run one drill that matches that sheet. Strategy: timed case on CoachNed (three typed turns, instant scores; everything open for seven days, no card; then $120 for a recruiting season or $49 a month). Technical: one timed coding session and one architecture walkthrough out loud.
- Hybrid seats: alternate case day and technical day. Do not average into vague "consulting prep."
For a live voice case against a strategy-style sheet, use the CopperCup interview (~18 minutes). For IBM-shaped hybrid cases, see the IBM Consulting case guide.
Frequently asked questions
Do Accenture Technology and McKinsey use the same interview format?
No. Accenture's published process varies by role and may include a technical coding assessment plus role-specific interviews. McKinsey's consulting process centers on personal-experience and problem-solving interviews, often with Solve for consulting seats. Treat the firm brand as a label, not a format.
Does IBM Consulting always give a case interview?
Not for every track. IBM's public entry-level guidance lists a case in the first live round for Consultant paths, while Developer and Data Scientist paths add coding assessment earlier. Confirm with your recruiter for the req you applied to.
How long do Accenture technical assessments take?
Accenture states most technical assessments take about 30 to 90 minutes and are completed online in one sitting within a window that is typically about 72 hours. The invitation shows the exact limit.
Can I prepare one set of cases for both tech and strategy recruiting?
You can reuse communication habits, but not the scoring sheet. Strategy cases reward decision structure and business math. Tech interviews reward applied depth and delivery judgment. One generic case bank without a target format underprepares both.
Is Deloitte Technology hiring the same as Deloitte Strategy?
Deloitte itself says assessment varies by business area and grade. Technology seats are more likely to include technical or coding tools; strategy and advisory seats lean harder into case and judgment interviews. Read the posting and ask the recruiter which tools apply.
Sources
- Accenture Recruiting and Hiring Process — process steps, technical assessment length (30–90 minutes), coding environment, 72-hour window, 90-day retake rule. Checked 2026-09-24.
- IBM Application Steps and Tips — coding, video, and language assessments; structured behavioral interviews; technical practice guidance. Checked 2026-09-24.
- IBM: Entry Level Consultant candidate tips — track-dependent rounds including case and behavioral for Consultant paths. Checked 2026-09-24.
- Bain hiring process and interview prep — role-tailored interviews; case interviews for consultant-style roles. Checked 2026-09-24.
- BCG consulting interview process — skills, case, and team interview sequence for client-facing roles. Checked 2026-09-24.
- BCG U.S. associate opportunities — CCA timing (~30–35 minutes, 48-hour window) and online case (~35 minutes). Checked 2026-09-24.
- McKinsey interviewing — personal experience and problem-solving interviews; assessments by role. Checked 2026-09-24.
- McKinsey Solve — gamified problem-solving assessment for consulting recruitment. Checked 2026-09-24.
- Deloitte UK Professional Careers Assessment — variable process by area; technical questions, cases, Codility, HireVue. Checked 2026-09-24.
- MIT Sloan CDO: MBB deadlines 2026–2027 — institutional example of strategy intake windows and interview waves. Checked 2026-09-24.
CoachNed is not affiliated with Accenture, Deloitte, IBM, McKinsey, BCG, Bain, or any firm named above.