Real, anonymous reports from people who interviewed for Software Engineer at eClerx, newest first and distilled into what to expect across the loop.
After a recruiter interaction, I later went through two technical rounds for a Software Engineer role. The first round leaned theoretical, where I had to answer fundamentals and concepts, and the second round mixed theory with actual coding. Even though the interview was framed as both backend and frontend, the topics I faced clustered around .NET and SQL Server, plus TypeScript and Angular questions on the frontend side. The panel had a senior developer and the team lead for the project they were hiring for.
My process started with group discussion rounds—there were two of them—before I moved into purely technical interviews. After that came two separate technical interviews, and then I ended with an HR round. The final HR conversation covered practical topics like work-from-home versus office preferences for the group discussion and tech segments.
The interview process typically follows a structured sequence, starting with group discussions or aptitude tests, followed by technical interviews focusing on coding and concepts, and concluding with an HR round. Candidates should prepare for each stage as a distinct evaluation point, with the HR round serving as a final checkpoint.
Technical interviews often blend theoretical questions with practical coding tasks, primarily centered around .NET, SQL, OOPs concepts, and web technologies like TypeScript and Angular. Candidates should be ready to demonstrate both their conceptual understanding and coding proficiency under time constraints.
Candidates reported varied experiences regarding interviewer engagement, with some feeling that interviewers were unresponsive or disinterested, leading to a lack of constructive feedback. It's important to prepare for potential variations in interviewer style and to seek clarity during discussions.
Overall, the difficulty of the interviews is reported to be average, with a mix of straightforward and challenging questions designed to assess both technical knowledge and problem-solving abilities. Candidates should practice a range of topics to feel adequately prepared.
Several candidates experienced a lack of follow-up communication after their interviews, leading to feelings of being 'ghosted' or left without closure. It's advisable to follow up proactively after interviews to seek updates on the process.
Some interviews included practical scenarios or real-world problem-solving tasks, emphasizing the need for candidates to connect theoretical knowledge with practical applications. Candidates should be prepared to discuss their past projects and how they relate to the role.