Real, anonymous reports from people who interviewed for Software Engineer at SBS, newest first and distilled into what to expect across the loop.
I had a pretty relaxed, low-friction interview that ended up being simpler than what I expected. It was supposed to be two stages, but it turned into a single interview with two people on the panel.
After a recruiter call, the process moved quickly into interviews that were much more about fit and practical understanding than stress. I ended up doing a straightforward coding test meant to probe how I think and how clearly I explain my reasoning, and then I had additional rounds focused on my resume and my real-world experience.
The interview process typically begins with a recruiter call to assess fit, followed by a series of technical and HR interviews that can vary in length and complexity. Candidates often experience delays in scheduling and communication, leading to feelings of uncertainty about the process.
Technical interviews emphasize Java programming, OOP concepts, and SQL queries, often incorporating practical scenarios rather than purely theoretical questions. Candidates should be prepared for a mix of coding challenges, DSA questions, and discussions on backend frameworks like Spring Boot.
Many candidates encounter initial rounds that include multiple-choice questions and aptitude tests focused on software engineering fundamentals, such as DBMS and flowchart problems. These rounds serve as early filters and can be challenging, with some candidates feeling unprepared for the pace and difficulty.
The HR rounds tend to focus on personal background, project discussions, and cultural fit, often described as conversational rather than interrogative. However, candidates frequently report a lack of feedback or closure after these discussions, which can be frustrating.
Overall, candidates describe the interview atmosphere as friendly and low-pressure, although some technical rounds can be moderately difficult. The experience is generally seen as straightforward, but the outcome can feel abrupt, especially without clear communication post-interview.
Candidates suggest focusing on practical applications of Java and SQL, as well as being ready to discuss past projects in detail. Many felt that a deeper understanding of the technologies mentioned in their resumes would have better prepared them for the technical discussions.