Real, anonymous reports from people who interviewed for Software Engineer at Deloitte, newest first and distilled into what to expect across the loop.
I started with a recruiter-style conversation, but the main interview that stood out was very resume-driven. The discussion centered on the projects I’d listed, and I ended up walking through the architecture, the features I built, the challenges I ran into, and how I implemented different parts. It felt interactive throughout, with the interviewer pushing for concrete details—what my exact contribution was, which technologies I used, and how I approached solving problems during development.
My path started with a recruiter conversation and then moved into a team round. The team questions felt a bit like knowledge checking—there were random Java questions meant to see how solid my understanding was.
The interview process typically begins with a recruiter conversation that assesses the candidate's background and fit for the role. This stage may involve basic questions about experience and expectations, and candidates should be prepared for a straightforward discussion about their resume.
Candidates can expect a series of technical assessments, including online coding tests and live coding interviews that focus on data structures, algorithms, and core programming concepts. It's essential to practice coding problems and be ready to explain your thought process clearly during these sessions.
Interviews often include in-depth discussions about past projects, where candidates are expected to articulate their contributions, technologies used, and problem-solving approaches. Candidates should prepare to provide detailed examples and connect their experiences to the role's requirements.
Behavioral interviews focus on assessing cultural fit and interpersonal skills, often using scenario-based questions. Candidates should be ready to discuss their teamwork experiences and how they handle challenges in a collaborative environment.
The interview process is generally well-structured, with a clear sequence of stages that may include assessments, technical interviews, and HR discussions. Candidates should expect a methodical approach and be prepared for a mix of technical and non-technical questions throughout.
Candidates often report a lack of feedback post-interview, which can lead to uncertainty about their performance. It's advisable to follow up for feedback after the process to gain insights into areas for improvement, even if the outcome is not favorable.