Real, anonymous reports from people who interviewed for Software Engineer at Impact Analytics, newest first and distilled into what to expect across the loop.
I went through a compact set of rounds that were mostly focused on coding and DSA-style problems. The process started with an online assessment, then I got a technical interview that was explicitly DSA-focused.
My process began with a recruiter screening focused on my background and how I communicated. After that, I moved into a technical round where the tone was fairly structured: we talked through core concepts and my projects, then I had to show problem-solving as the conversation shifted into technical questions.
Candidates typically start with an online assessment focused on coding tasks, often involving hands-on implementation with frameworks like React and Redux. The assessment is designed to evaluate the ability to read and complete a starter project rather than build from scratch.
Following the assessment, candidates face multiple technical interviews that may include DSA-style problems, with a focus on algorithmic challenges and problem-solving skills. The difficulty can vary significantly between rounds, with some candidates finding later rounds unexpectedly harder.
Candidates also participate in behavioral interviews that assess communication skills, teamwork, and real-world problem-solving approaches, moving beyond pure technical skills to evaluate fit within the team and company culture.
The interview process can be lengthy, with some candidates experiencing abrupt endings and poor communication from HR, leading to frustration over a lack of feedback or closure after the final rounds.
There is a notable inconsistency in the technical depth of interviews, with some candidates reporting a lack of deep technical questioning in later stages, which can leave them unsure of what the company is truly evaluating.