Real, anonymous reports from people who interviewed for Software Engineer at Impetus Technologies, newest first and distilled into what to expect across the loop.
I started with interviews that felt very backend-focused and Java-heavy, moving from core concepts into the Spring Boot and messaging ecosystem. After the initial stage, I ended up in technical discussions where the interviewer dug into core Java and then followed through on Spring Boot and microservices-style thinking. Kafka came up directly, and I also had to talk about how testing fits into the workflow with JUnit.
My interview journey started in a pretty straightforward way: the session kicked off with my resume and prior projects. I talked through what I built, what technologies I used, and how I would implement the key parts. I also had to explain the basics behind any newer tools I’d been learning, which kept the conversation grounded.
The technical interviews primarily centered on core Java concepts, data structures, algorithms, and practical coding problems, often requiring candidates to explain their reasoning and approach in detail.
Candidates reported that the interviews demanded a deep understanding of both theoretical concepts and practical applications, especially in areas like Spring Boot, SQL, and big data technologies.
The interview process typically followed a structured format, starting with a coding test, followed by multiple technical rounds, and concluding with an HR discussion, providing a clear progression through the stages.
The overall tone of the interviews varied, with some candidates feeling supported and others experiencing discomfort due to unclear expectations or abrupt changes in questioning style.
Several candidates expressed frustration with the lack of follow-up or clarity after the interviews, particularly regarding offer decisions and feedback, which contributed to a feeling of uncertainty.
The difficulty of the technical questions varied, with some candidates finding them straightforward while others faced challenging scenarios that tested their problem-solving skills under pressure.
