Real, anonymous reports from people who interviewed for Software Engineer at Chetu, newest first and distilled into what to expect across the loop.
I went through a campus-style, multi-stage loop with an aptitude/CBT gate, then group discussion and HR before a later technical assessment.
I interviewed in a comparatively low-difficulty track with an easy assessment and very basic technical questions, but a bond requirement affected the final decision.
Candidates typically begin with an online aptitude test that assesses quantitative reasoning, logical thinking, and basic computer science knowledge, which is crucial for progressing to the next stages.
Technical interviews focus on core programming concepts, particularly OOP principles and role-specific technologies, with questions ranging from basic to moderate difficulty, often including practical problem-solving scenarios.
Many candidates participate in group discussions that evaluate communication skills and teamwork, followed by HR interviews that address fit, career aspirations, and sometimes contractual obligations like employment bonds.
Candidates report a wide range of experiences, from well-structured and supportive interviews to instances where interviewers appeared unprepared or where role descriptions changed unexpectedly, impacting overall satisfaction.
Several candidates noted that offer conditions, such as lengthy employment bonds or unpaid training periods, significantly influenced their decision to accept or decline offers, highlighting the importance of understanding these terms early on.
Most candidates did not receive offers, emphasizing the need for solid preparation across all interview stages, particularly in technical fundamentals and understanding of personal projects.
