Hashedin By Deloitte SDE - I campus hiring experience
Question Details
HashedIn by Deloitte Interview Experience First round was OA, it was for 90 minutes and had 3 questions: - 1 easy and 2 medium LeetCode-type questions. - But there were no test cases...
Full Details
HashedIn by Deloitte Interview Experience
First round was OA, it was for 90 minutes and had 3 questions:
- 1 easy and 2 medium LeetCode-type questions.
- But there were no test cases to check if your code was right or not.
- You had to code and check against custom test cases of your own, find the edge cases, and then submit the result.
**
Technical Interview Round 1**
The next day, I was shortlisted for the 1st round of the technical interview. It started with:
-
Introduction \u2013 They asked about my passion and extracurricular activities.
Core subjects like OOPS, C++, and DBMS:
-
Diamond inheritance in C++.
-
Types of Joins in SQL.
-
Virtual Constructor concept.
-
SQL Query \u2013 Finding the second largest element in a table.
Coding Questions \u2013 The panel had 2 interviewers (one was asking most of the questions, the other was a bit dormant). I had to write code on paper (only logic explanation was also acceptable).
-
Longest Palindromic Subsequence (LCS variation): Given a string, reverse it and find LCS (from
LeetCode Striver Sheet).
- After solving the optimal approach, they further asked me to find the second largest palindromic subsequence. This was tricky, and I took some time, asked for hints, and was eventually able to solve it, though not in the most optimal way.
- Another
DP question on array partition, which I was able to solve.
**
Technical Interview Round 2**
In this round, they first asked some basic coding questions:
-
Detecting Cycle in a Linked List (Hare and Tortoise method).
Implementing Stack using Queue.
System Design:
-
Designing a high-level Flipkart-type app with features they mentioned.
- I created
API call flow diagrams and database schema with foreign key references.
- They then asked me to normalize the database, guiding me along the way. I made progress but couldn\u2019t complete it exactly as expected.
- A
SQL query based on the tables I created.
HR Round
This was the most chill round:
-
Discussion on projects from my resume \u2013 why I built them, the purpose, and technical details.
Casual Questions like
CR7 vs Messi, family background, and personal interests.
Situational Questions like \u201CWhat would you do if you received \u20B910 crore today?\u201D.
If you reach the
HR round, you\u2019re likely selected. They selected everyone who made it this far.
Preparation Tips:
-
Practice LeetCode (Striver Sheet) for
DP, Strings, and Array problems.
Revise OOPS, DBMS, and SQL queries.
- Learn basic System Design (API design, Database Normalization).
- Mention only the technologies you are confident in on your resume.
Overall, it was a well-structured process, testing
DSA, Core CS, and System Design skills.
About This Question
This is a reported interview question from a deloitte interview for a swe role during the oa round reported in 2025.
It covers the following topics: Arrays, Dynamic Programming, Linked List, Queue, Sql, Stack, Strings, System Design .
Difficulty rating: Easy
More Deloitte Interview Questions
About Deloitte Interview Reports
This question was reported by a candidate who interviewed at Deloitte. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Deloitte are the higher-signal extractions to take from this report.
For broader preparation context, the Deloitte interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Deloitte reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Deloitte Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Deloitte reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.