Interview Structure & Rounds
The interview process typically consists of three rounds: two technical rounds focused on coding and problem-solving, followed by an HR conversation that often includes salary negotiation.

Real, anonymous reports from people who interviewed for Software Engineer at GSPANN, newest first and distilled into what to expect across the loop.
My process ended up being three technical rounds followed by a final HR conversation. Everything stayed tightly connected to the software engineering role I’d applied for, and the interviews consistently framed questions around what I’d done before and how I could contribute if I joined.
After the initial recruiter stage, I got an online assessment made up of aptitude along with coding and logical reasoning. It also included SQL questions, and everything was multiple choice.
The interview process typically consists of three rounds: two technical rounds focused on coding and problem-solving, followed by an HR conversation that often includes salary negotiation.
Technical rounds emphasize practical coding skills, particularly in JavaScript and core Java, with a strong focus on how candidates connect their past experiences to the tasks at hand.
Candidates should expect to solve coding problems live, often discussing their thought process and implementation choices, which highlights the importance of clear reasoning and coding discipline.
The final HR round assesses cultural fit and communication skills, with interviewers looking for alignment between the candidate's background and the company's values.
The overall difficulty of the interviews is considered average to challenging, with a clear expectation for candidates to demonstrate solid fundamentals and practical knowledge.
Candidates reported mixed experiences with feedback and communication throughout the process, with some feeling that the evaluation criteria were not consistently applied or clearly communicated.