Real, anonymous reports from people who interviewed for Software Engineer at Sonata Software, newest first and distilled into what to expect across the loop.
My interview process started off with a recruiter-managed setup through Risebird, and the early technical conversation didn’t feel properly connected to the actual project. Both rounds were essentially led by interviewers who weren’t closely tied to the client or familiar with the role details, and the second round followed the same pattern—questions and context that didn’t seem to line up with what the client was expecting. What really bothered me was how little continuity there was: the interviewer didn’t seem to know what had been covered earlier.
After a recruiter-style touchpoint, the process moved into a technical screening first, followed by additional rounds that mixed technical and people-focused evaluation. What stood out was that I didn’t just do one interview—I ended up walking through a multi-round sequence, and it took long enough that it felt like a full pipeline rather than a single conversation.
The interview process typically consists of three main rounds: an initial aptitude test, followed by a technical interview focused on fundamentals, and concluding with an HR discussion about fit and expectations. Some candidates experienced variations with additional managerial or architect discussions, but the core structure remains consistent.
Candidates reported a strong emphasis on core programming fundamentals, data structures, and SQL queries during technical interviews, with varying levels of difficulty that often leaned towards average to challenging. The expectation is to demonstrate problem-solving skills and clarity in reasoning rather than just rote memorization.
Communication throughout the interview process has been noted as inconsistent, with some candidates experiencing delays in feedback and a lack of transparency regarding their application status. This has led to feelings of uncertainty and frustration, especially when verbal commitments were not followed by formal offers.
Candidates described varying experiences in terms of interview environment, with some feeling well-supported and others encountering technical issues or unprepared interviewers. The overall atmosphere can significantly impact a candidate's confidence and performance.
Candidates emphasized the importance of solid preparation in core concepts, especially in programming and database management, as well as being ready to discuss projects listed on their resumes. Practicing problem-solving under pressure is also recommended to navigate the interview format effectively.
The timeline for the interview process can vary, with some candidates experiencing a quick turnaround from application to interviews, while others faced prolonged waits and disorganization. A clear and efficient process flow is often appreciated, contributing to a more positive candidate experience.