A practical roundup of 16 firsthand Deloitte new-grad and entry-level tech interview reports from 2019 through 2026.

Coverage: Deloitte new-grad and entry-level software, analyst, solution developer, Omnia / Applied AI, and Digital / AI / Algorithm Risk roles in the United States, Canada, India, and Europe (2019–2026). HashedIn by Deloitte is excluded because its SDE pipeline differs.

Dedicated to a fren~ but the fren already aced the assessment before i could finish it up LOL, which is awesome!! 🎉

Still sharing this anyway. Hope it can help more frenz out there 🤝

The short version

Deloitte does not have one universal new-grad SDE process—the role, practice, office, and recruiting channel can change the interview almost completely.

1. Read the exact job title, not only the Deloitte logo. Software-engineering tracks may use timed coding; analyst and AI tracks may emphasize projects, SQL, cases, presentations, or recorded video.
2. The OA format varies sharply. Formats ranged from three timed coding problems to mixed MCQs, HireVue, personality inventories, and SHL reasoning.
3. Most reported coding is foundational, but a clean solution still matters. Arrays, strings, hashing, sorting, and basic dynamic programming appeared repeatedly. A few candidates also saw trees, matrix problems, and optimization follow-ups.
4. SQL and object-oriented fundamentals are unusually high-yield. Joins, relational keys, normalization, OOP principles, and language fundamentals showed up across several offices and role families.
5. Your resume can become the interview syllabus. Expect questions about stack choice, architecture, ownership, tradeoffs, and scaling.
6. Communication is part of the technical bar. Several reports mixed coding with client scenarios, ambiguity, project explanation, and behavioral follow-ups.
7. Treat older reports as pattern evidence, not a process guarantee. The strongest current signals here come from 2024–2026.

A practical preparation formula: arrays and strings + SQL and OOP + one deeply rehearsed project + six adaptable STAR stories + role-specific case or data practice.

Reported OA and coding question bank

These are candidate-reported tasks; wording and constraints varied.

Coding tasks

The timelines below show the source round. Links appear only for close FastPrep matches.

1. Parameterized divisibility labels
2. Sorted character frequencies
3. Top N longest sentences
4. Pair elements with even sums
5. Minimum deletions for a non-palindrome
6. Minimum-cost solar rooftops
7. All pairs with a target sum
8. Largest array element
9. Maximum-sum rectangle
10. Install Carbon Filters
11. Longest Substring with Even Occurrences
12. Two Sum
13. House Robber
14. Left-rotate an array by k.
15. Return the left view of a binary tree.
16. Simple regex and string matching.
17. Select the longest string.

SQL, OOP, and core CS

1. Explain inner, left, and right joins; write simple MySQL with filters, aggregates, and joins.
2. Review primary and foreign keys, normalization, and relational design.
3. Compare OOP with functional programming and explain the four OOP principles.
4. Discuss Python multithreading and any language-specific fundamentals named on the resume.
5. Improve an earlier OA solution and defend its complexity.
6. Explain a project's architecture, stack choices, personal contribution, tradeoffs, and failure modes.

HireVue and behavioral questions

1. Introduce yourself; why Deloitte and this role?
2. What excites you about technology, and what is not on your resume?
3. Describe a mistake, difficult feedback, or a missed deadline.
4. How do you handle pressure, competing priorities, and multiple tasks?
5. Walk through your hardest data or software project.
6. Describe teamwork, leadership, conflict, communication, and learning with clear personal ownership.
7. For AI roles: how can AI strengthen Deloitte's work?

Cases, presentations, and consulting-style prompts

1. Improve emergency-room patient intake through process, hardware, and software changes.
2. Explain a project and its business value to a non-technical stakeholder.
3. Build a real-estate price model, present the findings, and defend the model in Q&A.
4. Defend regression, classification, random forest, PCA, transformations, and assumptions.
5. Plan training for client teams adopting a new data tool.

16 Deloitte New Grad Tech Interview Experiences

01. United States: a software-engineering title with a scenario-first interview

Report date: April 12, 2026 · Role: Software Engineering Solutions Analyst · Location: United States · Result: Offer

The candidate had graduated with a computer science degree in 2025 and reported having no internships before receiving the offer.

1. Across two interviews, there were no conventional LeetCode questions or language-syntax drills.
2. The main technical scenario was how to improve emergency-room patient intake using options such as self check-in hardware, software for organizing patients, and a prioritization process.
3. The discussion rewarded structured problem solving and the ability to connect technology to an operational outcome.

02. Canada: HireVue followed by a surprisingly technical final

Report date: March 25, 2026 · Role: Enterprise Operate New Grad · Location: Canada · Status: Waiting when posted

1. The candidate first completed a HireVue stage.
2. The final interview had been described as behavioral, but the panel explained that it was looking for IT analysts and asked about programming languages, coding exposure, and technical projects.
3. The candidate felt the role and interview expectations were not aligned with the broad job posting. The panel mentioned possible recommendations to other departments.

03. India: two-question OA, then two technical rounds

Interview dates: March 25–31, 2025 · Role: Software Engineer, Fresher · Location: India · Result: Rejected

Online assessment — 60 minutes

1. DSA multiple-choice questions.
2. Two Sum, with a lexicographically smallest valid pair of indices.
3. Left rotation of an array by k; the candidate used the reversal method.

Technical interview 1 — 60 minutes

1. An age puzzle.
2. Left View of a Binary Tree, solved with BFS.

Technical interview 2 — 60 minutes

1. House Robber, solved with dynamic programming.
2. Python questions, including multithreading, plus detailed project discussion.

04. Greece: three Codility problems before the recruiter conversation

Interview period: August 2025 · Role: Junior Software Engineer · Location: Greece · Result: No offer

1. The first stage was a Codility assessment with three medium-difficulty problems in 70 minutes.
2. A recruiter interview followed on a later date.
3. Questions covered academic background, university work, and programming knowledge.

05. On-campus FTE: three concrete Codility problems in 90 minutes

Interview cycle: 2024 · Role: Entry-level FTE tech role · Location: Not disclosed · Result: Not disclosed

The coding test used Codility and contained three questions:

1. Pair Elements with Even Sums: decide whether every element can be paired so each pair has an even sum.
2. Minimum Deletions for a Non-Palindrome: find the fewest deletions needed to make the string non-palindromic.
3. Minimum-Cost Solar Rooftops: meet the colony's energy target using two installation costs as cheaply as possible.

06. Campus Codility: two exact string tasks preserved

Report date: October 21, 2023 · Role: General Tech, New Grad · Level: Undergraduate · Location: Not disclosed · Result: Passed

The candidate's screenshots preserve two of the Codility tasks:

1. Install Carbon Filters: replace every ? with a or b so the result contains neither aaa nor bbb; N could reach 500,000.
2. Longest Substring with Even Occurrences: return the longest contiguous substring in which every letter appears an even number of times; N could reach 100,000.
3. Task 1 was not preserved in the accessible screenshots, so it is not reconstructed here.

07. Digital / AI / Algorithm Risk: SHL reasoning, personality, and video answers

Report date: August 13, 2023 · Hiring cycle: 2024 · Role: Digital / AI / Algorithm Risk Analyst · Location: Not disclosed

1. Reasoning assessment — 46 minutes. Numerical calculations, pattern recognition, chart manipulation, and scheduling tasks. The candidate completed only about half because of the time pressure.
2. Personality inventory — 20 minutes. Repeated forced-choice statements about work style and preferences.
3. Recorded video — 10 minutes. Each question allowed about 15 seconds to prepare and 45 seconds to answer. The two reported prompts were a mistake story and a stressful-situation story.

08. Software Engineering Analyst: OA review plus live Codility

Report date: November 7, 2023 · Role: Software Engineering Analyst · Location: Not disclosed

1. The first round began with projects from the resume.
2. The interviewer moved to conceptual questions such as the different SQL joins.
3. One OA problem was revisited, and the candidate was asked how the solution could be improved.
4. The candidate then opened Codility and solved a live medium-difficulty coding problem while reading the prompt aloud, clarifying constraints, and explaining the approach.

09. New York: coding, case review, and fit

Report date: January 1, 2023 · Role: Software Engineer, New Grad · Location: New York, United States · Result: No offer

1. The process was described as coding, case review, and fit.
2. The LeetCode-easy-level coding task was Minimum Deletions for a Non-Palindrome.
3. The candidate received positive feedback on the coding and case portions but did not progress to the fit round.

10. Applied AI Analyst: technical screen, take-home model, presentation, and MD chat

Report date: November 29, 2022 · Role: Applied AI Analyst, New Grad · Location: Not disclosed · Result: Offer

First interview

1. A 25-minute technical discussion followed by 25 minutes of behavioral questions.
2. Technical questions included right join versus left join and targeted follow-ups on projects and internships.
3. Behavioral questions focused on teamwork, leadership, and communication.

Take-home and second interview

1. The take-home used real-estate training and test CSV files with thousands of rows and 81 columns, including the target price.
2. Deliverables included EDA and visualizations, a price-prediction model, interpretation of important variables, recommendations, a slide deck, and the analysis notebook or R file.
3. Deloitte suggested budgeting six to eight hours and allowed four days.
4. The next interview began with a 20-minute presentation and moved into Q&A about data cleaning, log transformations, regression versus random forest or classification, PCA, assumptions, and future model improvements.

Final interview

1. A 15–20 minute conversation with an MD or partner.
2. Questions focused on intellectual curiosity, entrepreneurship, communication, and how to train teams on a new data tool.
3. The candidate received an offer call a little over a week later.

11. Canada Omnia AI: HireVue, simple coding and MySQL, then an offer

Report date: February 22, 2022 · Role: Technical Solution Analyst / Developer, Canadian Delivery Center, New Grad 2022 · Location: Canada · Result: Offer

1. The candidate attended a Deloitte networking event during the holiday period and applied in January.
2. A January 28 HireVue assessment mixed behavioral questions with three simple coding tasks involving regex and strings.
3. A February 11 one-hour video interview included another straightforward coding task and MySQL questions.
4. The candidate received a verbal offer on February 14.

12. Data Science OA: seven recorded prompts, then four coding tasks

Report date: May 9, 2021 · Role: Data Science · Level: Undergraduate · Location: Not disclosed

1. The assessment opened with seven recorded questions. Preserved prompts included why Deloitte, the candidate's last work experience, an open invitation to add anything else, and work authorization.
2. It then moved to four coding tasks. Three preserved prompts were All Pairs with a Target Sum, Largest Element in an Array, and Maximum-Sum Rectangle. The fourth was not preserved clearly enough to reconstruct.
3. Supported languages were C, C++, Java, Python 2, and Python 3.

13. Canadian Delivery Center Solution Developer: eight HireVue prompts

Report date: October 5, 2020 · Role: CDC Solution Developer, New Graduate 2021 · Location: Canada · Result: Waitlist

The asynchronous HireVue contained eight behavioral prompts, with roughly two minutes available per response:

1. Introduce yourself.
2. Why did you apply for this role?
3. What are you passionate about in technology?
4. How do you deal with a mistake?
5. Describe feedback from a manager.
6. How do you handle multiple tasks?
7. Have you missed a deadline?
8. A second deadline-related scenario.

14. Omnia AI Data Engineer: five-question HireVue

Report date: October 24, 2019 · Role: Omnia AI Data Engineer, New Graduate 2020 · Location: Not disclosed · Result: Rejected

The candidate reported five recorded questions:

1. Introduce yourself.
2. Why Deloitte?
3. Describe your most challenging data project and how you solved it.
4. How can artificial intelligence strengthen Deloitte's work?
5. Tell us something that is not on your resume.

15. Canada: basic OA, a short technical screen, and a director conversation

Report date: February 27, 2019 · Role: Entry-level technology role · Location: Canada · Result: Passed

1. The OA was described as very basic; the hardest task was finding a longest string. The reviewer later commented positively on the candidate's use of a lambda expression.
2. The next stage could be conducted by Skype and included about 15 minutes of behavioral questions plus 15 minutes of technical questions.
3. Technical topics included OOP, inner joins, and a basic comparison of supervised and unsupervised learning.
4. A later 30-minute conversation with a director focused heavily on the director's experience building the group, qualities valued by the team, the candidate's co-op work, and the questions the candidate asked.

16. Developer OA: three deliberately basic implementation tasks

Report date: February 12, 2019 · Role: Developer, New Grad · Location: Not disclosed · Result: Not disclosed

The test contained three questions in one hour, weighted 15, 20, and 25 points:

1. Parameterized Divisibility Labels: print AB, A, or B using two divisors.
2. Sorted Character Frequencies: count a word's characters and print them alphabetically.
3. Top N Longest Sentences: return the first N longest sentences from a list.

What repeated often enough to prioritize

Tier 1: Practice until automatic

1. Arrays, strings, hash maps, sorting, and one-dimensional dynamic programming.
2. SQL joins, keys, normalization, and a few clean queries without autocomplete.
3. A two-minute explanation of one project from problem to architecture, personal contribution, tradeoffs, and result.
4. Writing edge cases before submitting, especially when hidden test feedback is limited.

Tier 2: Be ready to explain deeply

1. Why an approach is correct, its time and space complexity, and how to improve it.
2. OOP and language fundamentals that appear anywhere on the resume.
3. How a technical choice affects a client, user, team, cost, or delivery timeline.
4. Six flexible STAR stories covering mistake, conflict, feedback, leadership, pressure, and competing priorities.

Tier 3: Role-specific differentiators

1. For Applied AI or data roles: EDA, model selection, assumptions, evaluation, visual explanation, and defensible recommendations.
2. For consulting-heavy analyst roles: cases, stakeholder communication, requirements gathering, and ambiguity.
3. For pure software-engineering roles: live coding narration, trees, matrix problems, and medium-level optimization follow-ups.

Final checklist

OA and coding

☐ Solve all 13 linked practice tasks once without hints.

☐ Run a 60-minute mock with three short problems and a 90-minute mock with three medium problems.

☐ Test empty, one-element, duplicate-heavy, negative-only, and large inputs.

☐ Practice explaining complexity and one better alternative after every solution.

SQL and core CS

☐ Write inner, left, and right joins from memory.

☐ Review primary and foreign keys, normalization, indexing, and common query patterns.

☐ Prepare concise examples for the four OOP principles.

☐ Revisit every language or framework named on the resume.

Projects and live interviews

☐ Prepare a five-minute project walkthrough and a 60-second non-technical version.

☐ Be ready to defend the stack, describe a failure, and propose one scaling improvement.

☐ Practice reading a prompt aloud, clarifying constraints, and narrating while coding.

HireVue and behavioral

☐ Record answers for “Why Deloitte?”, mistake, feedback, conflict, pressure, and missed deadline.

☐ Keep each answer specific about personal ownership and measurable outcome.

☐ Prepare one strong question about the actual team, client work, and expected technical depth.

AI, data, and case tracks

☐ Practice turning a messy dataset into a short recommendation deck.

☐ Review when to use regression, classification, tree-based models, and dimensionality reduction.

☐ Explain one technical decision in business language without hiding behind jargon.

Come hangout with us on FastPrep Experience~

Jane from FastPrep 🐳
I collect, distill, and share highly concentrated, high-quality tech interview stuff 🌱

Like always, the sources come from anywhere across the internet where useful interview information can be found.