Sonata Software Software Engineer Interview Questions
& Process

I interviewed for a Senior Software Developer role. The first technical interview went well, and I got the confirmation that I passed. But, the subsequent steps were kind of messy. Before the client interview, I had to go through an internal call that felt like it was just a formality. What really bothered me was being asked to change my resume to fit the client's specific needs and then prepare for the client interview last minute. As someone already working, it felt like too much to ask to spend so much time tweaking documents and getting ready for a role that wasn't even clearly defined from the beginning. There was a lot of confusion and back-and-forth, making the whole thing pretty annoying. A smoother and clearer process would be great, especially for experienced folks.

The interview process at Sonata Software consisted of 3 rounds, and it was a pretty smooth and organized experience overall. First, there was an Online Assessment that lasted about 90 minutes and covered both Aptitude (logical reasoning, quantitative ability, verbal questions) and Technical MCQs (C, Java, DBMS, OOPs, operating systems). This was followed by 1 or 2 basic coding questions in Java or Python. Then, a Technical Interview was conducted virtually. They asked questions on programming fundamentals like arrays, loops, and strings, OOP concepts with real-world examples, database queries and basic SQL, and a discussion about your final year project. They also gave one or two coding questions, ranging from simple to medium difficulty. Lastly, an HR Interview took place, which was a general chat about your introduction and background, why you chose Sonata, your willingness to relocate or work in shifts, your career aspirations, and salary discussions if relevant.

The interview process was a bit all over the place. They asked questions based on my resume and interests, especially around Gen AI. There were also some basic DSA and data structure questions. Hiring was super inconsistent, which was weird because people who didn't even pass the technical round ended up getting hired. Honestly, it felt like a bad interview process overall.