Real, anonymous reports from people who interviewed for Software Engineer at Ness Digital Engineering, newest first and distilled into what to expect across the loop.
After a recruiter conversation, I moved into a fairly classic screening-to-technical flow. HR asked a lot of general questions about my background, past work, and my degree, and it all felt like they were trying to understand me before going deeper. A technical interview followed where I got into a mix of OOP and Java fundamentals—things like SOLID and general object-oriented reasoning—along with SQL and topics around Kafka. I also remember a quiz component and a coding interview that felt like it was testing whether I could translate the fundamentals into working code.
After the initial recruiter call, I was pulled into an HR screen that went heavy on general topics—my background, my degree, and my past experience. It was fairly standard and didn’t feel adversarial, just like they were calibrating fit before getting technical. Soon after, a technical exercise came up that was tied to a web stack.
The interview process typically follows a structured format starting with an HR screening, followed by multiple technical rounds, and concluding with an HR discussion. Candidates noted that the progression through these stages felt organized and clear, with timely communication about next steps.
Candidates faced a variety of technical challenges, including coding exercises focused on Java, OOP concepts, and practical problem-solving. The difficulty of these assessments varied, with some candidates experiencing a mix of live coding and take-home assignments that emphasized deliverables.
Interviews often included discussions about past projects and experiences, where candidates were asked to explain their contributions and reasoning. This behavioral aspect was important for assessing fit and communication skills alongside technical capabilities.
Many candidates expressed frustration with the communication process post-interview, particularly regarding delays in feedback and clarity about offers. Several reported long waiting periods without updates, which negatively impacted their overall experience.
The overall atmosphere during interviews was generally described as supportive and friendly, with interviewers encouraging candidates to ask questions. However, some candidates encountered less favorable interactions that felt more adversarial, particularly during technical assessments.
Candidates noted that while the initial rounds felt manageable, later stages often ramped up in difficulty, requiring not just coding skills but also the ability to handle complex problem-solving under time constraints. This expectation was a common theme across various reports.