Real, anonymous reports from people who interviewed for Software Engineer at Kumaran Systems, newest first and distilled into what to expect across the loop.
I went through a fairly organized, multi-round loop that felt professional from start to finish. After an initial introductory interaction, the process moved into core-skill discussions and a structured coding-heavy flow. Across the rounds, I kept getting pulled back to the fundamentals behind what I’d listed on my resume, especially Java topics and microservices-style thinking, plus how I handled responsibilities in earlier projects.
My first steps felt smooth and pretty easy to navigate. I started with an aptitude-style round focused on logic, reasoning, and numeric questions, and it stayed in the realm of fundamentals rather than tricky puzzles. After that, the next stage shifted into coding with a small set of problems—enough to test whether I could actually implement cleanly, not just talk about it.
The interview process typically follows a structured sequence starting with an aptitude test, followed by technical rounds that delve into core concepts and coding challenges, and concluding with HR discussions. Candidates can expect a clear progression from general screening to more specific technical and people-focused conversations.
Candidates should prepare for a mix of coding problems, data structures, algorithms, and engineering fundamentals, with a focus on practical implementation and core concepts related to their resume. The difficulty can vary, but many report a consistent level of challenge across technical rounds.
HR rounds often focus on fit, logistics, and personal experiences, with questions designed to assess communication skills and cultural alignment. Candidates should be ready to discuss their backgrounds and preferences in a straightforward manner, as this part of the process is generally supportive rather than adversarial.
The pace of the interview can feel demanding, especially in technical rounds, where candidates are expected to think on their feet and demonstrate a solid grasp of concepts. Some candidates noted that the perceived difficulty may exceed expectations, particularly in the early technical stages.
Candidates have reported mixed experiences regarding feedback, with some feeling a lack of closure after the process, especially if they did not receive an offer. It's advisable to follow up for clarity on outcomes, as some candidates experienced delays or silence post-interview.
Candidates should prioritize reviewing core technical skills relevant to the role, such as Java, OOP concepts, and data structures, as well as practicing coding problems under timed conditions. Understanding the company culture and being able to articulate personal experiences will also be beneficial.