HashedIn by Deloitte Business Analyst Interview Experiences 2026
Real, anonymous reports from people who interviewed for Business Analyst at HashedIn by Deloitte, newest first and distilled into what to expect across the loop.
Get your personalized HashedIn by Deloitte Business Analyst prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
The process stretched for about two months and it felt pretty relentless—four rounds total, plus a test that ended up deciding the direction of the interview. After an initial recruiter touchpoint, I moved into technical discussions that were very hands-on. I worked through topics that landed around .NET, SQL, and Angular, and the early vibe was technical enough that it felt like they were screening for specific working familiarity.
Then I got scenario-style questions where I had to talk through how I’d implement something, not just name concepts. By the time I reached the managerial round, the questions were more about how I would approach things from a leadership/ownership angle. Even though the interviews kept progressing, the overall difficulty stayed “average but demanding,” and the final result was ultimately rejection—once they realized I wasn’t the fit they were looking for, it made the later rounds feel a bit anticlimactic.
> 1 year
Difficult Negative Chennai
My interview felt tough from the start. The interviewer pushed hard on system design questions, but it also didn’t stay neatly within my resume—I got asked about topics that weren’t where my background was strongest, which made it harder to settle into a groove.
There was also a clear SQL component threaded through the conversation, so I was juggling design-style reasoning and query-related thinking at the same time. The overall difficulty landed at “very difficult,” and I never really got the feeling that I could recover once I was off-track.
> 1 year
Average Neutral Bengaluru
My first step was a coding-focused round on a platform that didn’t feel very user-friendly—part of the problem description wasn’t as clear as I would’…
> 1 year
Average Positive India
I went through a pool interview specifically for women candidates, and the scale was honestly intense—around 250 people were in the pool. It started w…
> 1 year
Difficult Positive Greater Noida
My hiring journey started with a written round, and then I moved into two technical interviews plus an HR conversation. The technical interviews were …
Unlock every Business Analyst interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically spans several weeks to months, often involving multiple rounds including written tests, technical interviews, and HR discussions. Candidates noted the length and intensity of the process, with some reporting it could take up to two full days or stretch over two months.
TimelineMultiple RoundsIntensity
Technical Assessment Focus
Candidates faced a strong emphasis on technical skills, particularly in areas such as data structures, algorithms, SQL, and system design. Many reported that the technical interviews tested not only coding ability but also the depth of understanding and reasoning behind solutions.
Data StructuresAlgorithmsSQL
Behavioral & Cultural Fit
Behavioral fit was a significant aspect of the interviews, with many candidates noting that interviewers assessed communication skills and cultural alignment throughout the process, especially in the later rounds. This included discussions about teamwork, leadership, and personal values.
BehavioralCultural FitCommunication
Difficulty Level & Expectations
Overall, candidates described the difficulty of the interviews as ranging from average to very difficult, with some feeling that the expectations were high and the pace was relentless. Many reported that once they fell behind in a question, it was challenging to recover.
DifficultyHigh ExpectationsPace
Written Test Components
The initial stages often included a written test that assessed both technical knowledge and problem-solving skills, covering topics such as time complexity, coding problems, and theoretical concepts. Candidates felt that clarity and correctness in their submissions were heavily scrutinized.
Written TestTime ComplexityProblem-Solving
Feedback & Reflection
Many candidates expressed a desire for earlier feedback on their fit for the role, noting that the lengthy process could feel anticlimactic if the outcome was rejection. Reflecting on the experience, candidates wished they had better understood the expectations and focus areas beforehand.