Real, anonymous reports from people who interviewed for Software Engineer at Info Edge, newest first and distilled into what to expect across the loop.
My process started with an HR touchpoint, and then I moved into a structured set of rounds. The first technical round was DSA mixed with core Java and SQL, and it also tied back to my prior work experience. After that, the next technical round shifted toward low-level design and development concepts, with a chunk of DevOps basics and cloud fundamentals alongside discussion of what I had done before.
What surprised me most was how the process started very formally and then stayed tightly technical. After HR scheduled things, I showed up for the interview in an offline format the same day, and I went through multiple technical rounds back to back. The first technical round focused on DSA plus my project details. The second technical round again included DSA, but it also became more specific—React, OOP, and operating system concepts came up.
The interview process typically consists of an online assessment followed by multiple technical rounds and an HR round, with a total of three to five rounds depending on the candidate's progression. Candidates noted that the scheduling can sometimes feel chaotic, with interviews set randomly without confirming availability.
Technical interviews predominantly cover data structures and algorithms (DSA), core programming concepts (Java, SQL), and system design, with varying levels of difficulty. Candidates should prepare for a mix of coding problems, theoretical questions, and practical applications related to their past projects.
The final HR or managerial round often incorporates behavioral questions alongside technical discussions, assessing candidates' problem-solving approaches and communication skills. This round is seen as a way to evaluate how candidates think under pressure and fit within the company culture.
Candidates reported a range of difficulty levels across technical rounds, with some finding the questions challenging and detailed, especially regarding DSA and system design. It's important to be prepared for in-depth questioning and to demonstrate clear reasoning and optimization in coding solutions.
Interviews often include discussions about candidates' previous projects, focusing on how they applied technical concepts in real-world scenarios. Candidates should be ready to explain their thought processes and decisions made during project development.
Some candidates felt that the interview process lacked follow-up communication, which left them uncertain about their status. Additionally, candidates expressed a desire to have better clarity on expectations and to focus more on problem-solving rather than optimization during coding tasks.