Real, anonymous reports from people who interviewed for Software Engineer at Infocepts, newest first and distilled into what to expect across the loop.
The first thing that stood out to me was the mismatch in how the rounds felt. The technical part was mostly about making sure my fundamentals were strong, while the HR round carried a different kind of risk—there was a real chance of rejection there rather than during the technical evaluation.
After an initial recruiter screening call, I was asked to talk through my background and share more about the role. That first conversation was fairly straightforward and set expectations for what the next steps would look like.
The interview process typically begins with an initial HR screening call, followed by two technical rounds focused on SQL and programming, and concludes with a final HR round. Candidates noted a structured flow, but some experienced frustration with communication and follow-up after the offer stage.
Technical interviews predominantly emphasize SQL skills, including querying, optimization, and reasoning about performance, along with some Python-related questions. Candidates should prepare for scenario-based prompts that relate to their past experiences and resume details.
The HR round is crucial and focuses on communication skills, alignment with company values, and framing of past experiences. Candidates should be prepared for detailed discussions about their background and how it relates to the role.
While some candidates found the interview process smooth and manageable, others reported a lack of clarity and consistency in communication throughout the process, leading to frustration. It's important to remain proactive in seeking updates post-interview.
Overall, candidates described the difficulty of the interviews as average, with a focus on evaluating competencies rather than obscure trivia. However, the experience varied, with some feeling the process was straightforward while others found it less favorable.
Candidates suggested focusing on SQL fundamentals, understanding performance optimization, and being ready to discuss personal projects in detail. Preparing for scenario-based questions and aligning responses with past experiences is also beneficial.