Deloitte Interview Prep
Deloitte spans audit, tax, consulting and advisory, and the process differs by service line, but graduate and experienced-hire loops share a common shape: online reasoning tests, a recorded or live competency interview, and, for most consulting and advisory roles, a group case exercise at an assessment centre. The biggest reason candidates report failing Deloitte interviews is not weak case skills, it is underestimating the competency-based behavioural questions and the group format, where assessors watch how you collaborate as closely as what you say. Deloitte's consulting business alone generates tens of billions in revenue globally and graduate acceptance rates sit in the low single digits, so volume of applicants is real, but the bar is about structured, specific answers delivered consistently across every stage, not raw brilliance in one round.
The Deloitte interview process
This is how the process usually runs, so nothing on the day is a surprise. Your recruiter is the one who knows for certain, so ask them what your version looks like.
- Online application and assessment: Numerical and verbal reasoning tests plus, for many graduate schemes, a game-based situational judgement assessment. What to expect: Practise reasoning-test format beforehand under real time pressure; this stage filters out the largest share of applicants before any human sees your application.
- Digital or video interview: Recorded competency questions answered without a live interviewer, or a short live call, depending on service line. What to expect: Concise, structured STAR answers delivered clearly to a camera. Practise this format specifically; performing to a recording feels different from a live conversation.
- Assessment centre: group case exercise: Candidates work together on a business problem in front of assessors, then often present a joint or individual recommendation. What to expect: Visible collaboration and structure: building on others' points, bringing in quieter candidates, and keeping the group on track, not dominating the airtime.
- Individual case or partner interview: A one-on-one case, lighter than a pure strategy-firm case, combined with deeper competency probing, often with a manager or partner. What to expect: Comfort structuring a business problem live and defending a recommendation to a senior stakeholder who pushes back.
- Final decision: Service-line leadership signs off, sometimes after one further partner conversation for senior or specialist hires. What to expect: Consistent competency evidence across every stage. Assessors compare notes, so a strong group exercise cannot offset a vague individual interview.
Common Deloitte interview questions
Why Deloitte, and why this service line specifically?
Why they ask: Tests whether you understand the real difference between audit, tax, consulting and advisory, or applied broadly without research.
How to answer: Name the specific type of work in that service line that appeals to you, and connect it to something concrete you have done or studied. Show you understand what a first-year in that service line actually does day to day, not just the brand name.
Your team represents a mid-size retailer deciding whether to close underperforming stores. Work with your group to build a recommendation.
Why they ask: The classic Deloitte group case: tests structured thinking under real-time collaboration, not just individual case skill.
How to answer: Help the group agree a structure early, financial performance per store, lease terms, cannibalisation risk, brand and employee impact, rather than jumping straight to an answer. Contribute specific analysis, bring in quieter teammates, and help the group land on one clear recommendation before time runs out.
Tell me about a time you worked in a team where someone wasn't pulling their weight.
Why they ask: Tests how you handle team friction constructively, a daily reality in client engagement teams.
How to answer: Describe the situation specifically and what you actually did, a direct conversation, redistributing work, escalating appropriately, rather than just tolerating it or complaining. Avoid a story where you simply did their work for them; that signals poor delegation, not leadership.
Tell me about a time you had to explain something complex to someone with no background in it.
Why they ask: Client-facing roles constantly translate technical findings for non-technical stakeholders.
How to answer: Pick a real example and show how you adapted the explanation, using an analogy, cutting jargon, checking understanding as you went, rather than just simplifying vocabulary. Name the outcome: did they actually understand and act on it.
A client's IT project is six months behind schedule and 20 percent over budget. How do you approach fixing it?
Why they ask: A lighter advisory-style case testing structured diagnosis rather than pure strategy-case rigor.
How to answer: Structure the diagnosis first: scope creep, resourcing gaps, technical complexity underestimated, or stakeholder misalignment. Ask what data is available before proposing fixes. Recommend a path forward with trade-offs (re-scope, re-resource, or reset timeline) rather than assuming more budget solves everything.
Describe a situation where you had to manage multiple deadlines at once.
Why they ask: Consulting and advisory staff routinely juggle several client workstreams simultaneously.
How to answer: Name the real competing deadlines, how you prioritised (client impact, dependency, effort required), and what you communicated to stakeholders about trade-offs. Show a system, not just working longer hours.
Tell me about a time you made a mistake at work. What did you do?
Why they ask: Tests honesty and ownership; assessors are wary of answers where the "mistake" is a disguised humble-brag.
How to answer: Pick a real mistake with a real consequence. Own it plainly without over-apologising, explain how you fixed or mitigated it, and name the specific change you made to avoid repeating it. Skip mistakes that are actually strengths in disguise.
How do you stay current on developments in this service line?
Why they ask: Checks genuine interest beyond the interview process itself.
How to answer: Name specific sources, publications, newsletters, a course, a regulatory change you have followed, and something you learned recently that changed your thinking. Generic "I read the news" answers do not land.
What Deloitte looks for
These are the things they listen for, even when the question is about something else entirely.
- Integrity
- Collaboration over ego
- Client service
- Inclusion
- Continuous learning
- Making an impact that matters
How to prepare
Do not skip reasoning-test practice; it eliminates more candidates than any interview round. Prepare STAR stories for the standard competency set, teamwork, leadership, conflict, resilience, learning from failure, and rehearse them to a camera if your process includes a digital interview, since that format feels different live. For the group case, practise in a mock group if you can: the skill being assessed is visible collaboration, not who reaches the best answer alone. Prepare one lighter business case structure (issue-diagnosis, not strategy-consulting rigor) and be ready to defend a recommendation to a partner who disagrees. Research the specific service line's recent public work, not just Deloitte as a brand. Run a Voxxhire mock interview out loud for the competency round in particular; the words that sound fine in your head often come out shapeless the first time you say them under pressure.
Roles this guide applies to
This guide fits best if you are going for one of these.
- management-consultant
- accountant
- financial-analyst