Real, anonymous reports from people who interviewed for Software Engineer at Accenture in India, newest first and distilled into what to expect across the loop.
My process started with a recruiter call after I applied, and then a few more rounds followed. The first technical part felt pretty straightforward: a math segment with about 30 questions covering basic addition, subtraction, multiplication, and division.
My interview journey ran in three rounds with a clear technical progression. The first round focused on DSA, and the second shifted into system design. The last round brought them together—DSA questions mixed with Amazon Leadership Principles themes and behavioral-style questions.
The interview process typically consists of multiple rounds, starting with an assessment followed by technical and HR interviews, often spaced out over a week or two. Candidates noted a mix of structured stages and occasional delays in communication, impacting their overall experience.
Candidates faced a variety of technical assessments, including coding questions, SQL, DSA, and real-world scenario-based problems. The technical difficulty was generally rated as average, but the focus varied between hands-on coding and system design discussions.
Behavioral interviews often focused on situational questions and alignment with company values, with some candidates expressing a desire for more HR interaction to clarify role expectations. The HR discussions typically covered strengths, weaknesses, and salary expectations.
Many candidates experienced a lack of communication post-interview, leading to feelings of uncertainty and frustration. Clearer follow-up and feedback were highlighted as areas for improvement in the overall candidate experience.
Overall, candidates rated the difficulty of the interviews as average, with some reflecting on how preparation and understanding of the role could have influenced their outcomes. Many noted that even a strong technical performance did not guarantee an offer.
Interviews often included questions that connected technical skills to real-world applications, such as discussing previous projects and scenario-based problem-solving. This approach aimed to assess both technical knowledge and practical reasoning.