Real, anonymous reports from people who interviewed for Software Engineer at Neudesic, newest first and distilled into what to expect across the loop.
After a recruiter call, about a week later I went straight into an online coding round to evaluate my problem-solving. I worked through the exercise in the scheduled format and then moved into the next stage with two technical discussions labeled L1 and L2. Those were more conversational and role-focused than purely algorithmic, and each round helped build on what they were looking for in my day-to-day work.
My first round was mostly the fundamentals: OOPs concepts along with .NET and SQL, and a lot of C#-centered questions. The tone felt straightforward, and the questions weren’t too hard—more about making sure I really understood the core concepts than testing deep, obscure details.
The interview process typically begins with a coding assessment followed by multiple technical discussions and concludes with an HR round to discuss role fit. Candidates noted that while the structure was generally clear, delays in communication and scheduling issues were common, leading to frustration.
Candidates experienced a variety of coding challenges, often focusing on core programming concepts, algorithms, and specific technologies like .NET, C#, and Java. The difficulty level varied, but many noted that clear communication of their thought process during coding was crucial.
Behavioral interviews were a significant part of the process, focusing on cultural fit and communication skills. Candidates were often asked to discuss their project experiences and reasoning, which highlighted the importance of soft skills alongside technical abilities.
The atmosphere of the interviews varied widely, with some candidates reporting a relaxed and friendly environment, while others described it as tense or chaotic, particularly during group interviews. This impacted their overall impression of the process.
Candidates frequently expressed dissatisfaction with the lack of feedback and follow-up after interviews, often feeling left in limbo regarding their application status. This lack of communication was a common source of frustration.
The technical interviews often included questions that tested both foundational knowledge and specific technologies relevant to the role, such as database design and system architecture. Candidates noted that the depth of questions varied, with some feeling overly focused on memorization rather than practical application.