Real, anonymous reports from people who interviewed for Software Engineer at Kanini, newest first and distilled into what to expect across the loop.
I took a day off and went to their office for what ended up being a long, structured sequence. Even before any technical interviews, it started with a laptop-based technical test. After that, I had an English and hearing assessment. Only after clearing that did I reach HR, and then I had two more technical rounds. The whole thing felt tightly scheduled, but also exhausting because it all happened in one stretch at the office.
My process started with an online test that mixed a few different question types. I had aptitude MCQs, technical MCQs, and then programming tasks, all split into timed sections on a website. The MCQs were auto-scored, and the coding part was evaluated in a more structured way, so the emphasis felt like they were trying to measure how I approached problems, not just the final answer.
The interview process typically begins with an online test that includes aptitude questions, technical MCQs, and coding tasks, often with a timed format to assess problem-solving approaches rather than just final answers.
Candidates undergo a structured communication evaluation that includes listening, writing, and speaking components, emphasizing clarity and coherence in expression throughout the process.
The technical rounds focus on core knowledge and project experience, with questions designed to gauge both technical proficiency and the ability to articulate thought processes clearly.
The interview experience is characterized by a tightly scheduled, multi-round format that can feel exhausting, with limited downtime between assessments, often spanning a full day or several weeks.
Candidates report an average to difficult difficulty level, with particular pressure during the communication and technical rounds, where clarity and consistency are crucial for success.
Post-interview reflections indicate that candidates wish they had better prepared for the communication assessments and the specific nuances of coding tasks, particularly regarding input handling.