My Interview Journey with Deloitte: A Deep Dive into Technical Rounds and Salary Negotiations

My interview experience at Deloitte for a Senior Frontend Engineer

One day, I received an exciting call from Deloitte regarding a Senior Frontend Developer position. During the brief 10-minute conversation, they asked me about my previous experience, salary expectations, and a few other basic details. By the end of the call, my interview was scheduled.

Interview Round 1:

The interview was conducted over a Zoom call with a panel of two friendly interviewers. The session began with a brief introduction before diving into the technical questions. Most of the questions were fundamental, focusing on JavaScript, with a few touching on Angular, Node.js, and optimization. The level of questioning felt very basic — primarily testing bookish knowledge or documentation familiarity. Considering the senior-level position I was applying for, I expected more in-depth, challenging questions. To sum it up, this was a casual, basic filtering round, and I found myself waiting for the “real” interview to begin.

Interview Round 2:

This was the real deal, and I could feel the intensity of the round. It kicked off with JavaScript questions, diving into intriguing topics like hoisting and closures. The interviewers presented on-the-spot scenarios, throwing random edits and expecting immediate solutions. I was required to share my screen, think on my feet, and write the code live — no general discussions here.

The focus was heavily on optimizing code, improving efficiency, and providing clear reasoning behind every approach. This round tested my deep understanding of JavaScript concepts and my ability to apply them effectively. Since my resume emphasized JavaScript and related frameworks, the questions were tailored accordingly — this focus might vary for others. The session lasted around an hour, with the majority of the discussion centered on JavaScript.

In the same round, I was given the option to proceed to a third interview, either immediately or on a different day. I opted to continue. This round primarily focused on the work I had been doing at my previous company, with questions presented in scenario-based formats. For example, I was given hypothetical situations and asked how I would handle them.

The topics covered a wide spectrum, starting with Angular and diving into advanced aspects of CSS, including optimizations, accessibility, printing, and unit testing. They also asked about functional testing, interpreting requirements, and leadership skills — how to delegate tasks, manage teams, and interact with business stakeholders.

On the technical side, there were questions about Git, lazy loading, and both popular and niche Angular techniques. The discussion extended to Webpack, frontend optimization, backend integration, and the handshake between the two. Coding questions were less frequent but required using techniques like hoisting to produce specific outputs. Emphasis was placed on explanations, communication skills, and how well I could articulate concepts to juniors.

Node.js and database-related questions were also part of the round, though not as deep as the frontend topics. These included making API calls, connecting to databases, and basic querying knowledge. Overall, this round was thorough, covering nearly every relevant topic, ensuring a comprehensive evaluation.

Interview Round 3:

This round came as a surprise — I was informed it would be an HR round, but it turned out to be another technical interview. The focus shifted towards machine learning and its integration into web applications. The discussion revolved around planning the architecture of a web application, designing an MVP, and strategizing for scalability.

Optimization was a recurring theme, along with integrating third-party packages and ensuring seamless functionality. The session delved into practical aspects of building robust and efficient applications. Despite being unexpected, the round was engaging and lasted for about an hour.

Interview Round 4:

The final HR round was quite unexpected — it was more relaxed and filled with laughter. I had anticipated typical questions like, “Where do you see yourself in the next five years?” or other career-oriented queries, but none of that came up. In fact, I was so curious that I turned the tables and asked why such questions weren’t asked, which only added to the humor of the conversation.

Instead, the HR asked simple, personal questions like, “Where are you from?” and kept the tone lighthearted. It felt more like a casual chat than a formal interview, which was surprising but refreshing.

Result on a phone call:

Finally, I received the news of my selection from a lady who initiated the salary discussion. However, it wasn’t much of a discussion — it felt more like a declaration. She quoted a package, and I was expected to simply say “yes” or “no,” leaving no room for negotiation.

This aspect of the process was slightly disappointing, especially since I had clearly stated my expectations during the initial call, and they had agreed to them. Despite this downside, the overall interview experience was positive and well-organized.

Conclusion:

Overall, the interview process went smoothly, but I was quite disappointed with the salary discussion round. While a small adjustment in salary is understandable, being presented with a fixed package and asked for an immediate “yes” or “no” felt somewhat abrupt. It would have been better if this had been communicated at the start of the interview process.

Nonetheless, I received an offer, and the entire interview process spanned over a month. One thing I noticed during the rounds was that it was difficult to contact the HR team, but once I was selected, they became very approachable and responsive.

Feel free to post any questions if you need further clarification — I’m happy to share my experience. Best of luck with your interviews, and I hope this helps you in your journey!