Real, anonymous reports from people who interviewed for Software Engineer at Zensar Technologies, newest first and distilled into what to expect across the loop.
It started with an on-campus setup, but the flow was split into two parts: first an online assessment, and then an interview and an HR round. I remember the whole process feeling fairly straightforward to moderately challenging—nothing about it felt especially punishing, but it wasn’t completely trivial either.
One part of my process felt smooth, but another part left a strong negative impression. In the first technical round, the questions stayed focused on .NET fundamentals and cloud basics, and it ran like a professional interview.
The interview process typically begins with an online assessment followed by multiple technical rounds and an HR discussion, often feeling structured and organized, though some candidates experienced frustrating delays and lack of communication afterward.
Candidates reported a strong emphasis on core technical skills, particularly in Java, .NET, SQL, and cloud basics, with questions often centered around practical problem-solving and foundational concepts rather than obscure trivia.
The coding assessments varied in format, including online coding challenges and hands-on problem-solving tasks, with a mix of languages like Python and Java, often requiring candidates to demonstrate their coding logic and application skills under time pressure.
The HR rounds generally focused on cultural fit and communication style, with candidates experiencing a mix of supportive and abrupt interactions, leading to varying levels of satisfaction with the overall process.
While many candidates felt the interviews were manageable and well-coordinated, several reported issues with follow-up communication and feedback, leaving them feeling uncertain about their performance and the overall outcome.
The overall difficulty of the interviews was perceived as average, with some candidates finding the process straightforward while others encountered unexpected technical challenges or a lack of clarity in expectations.