Real, anonymous reports from people who interviewed for Software Engineer at Qinetiq, newest first and distilled into what to expect across the loop.
My first step was a fairly relaxed conversation, and it honestly felt like they were just trying to get to know me. I spoke with two people who I would potentially work with, and the vibe was casual—more about my background, skills, and interests than trying to catch me out with tricky questions. The questions were thoughtful, and I remember feeling welcomed rather than interrogated.
My process started with an online interview focused heavily on my experience and why I wanted to join. Beyond the usual conversation, I had to give a presentation on systems engineering, which was the part that stood out because it wasn’t just verbal Q&A.
The interview process typically begins with relaxed conversations focused on fit and background rather than technical grilling, allowing candidates to express their experiences and interests comfortably.
Candidates can expect a mix of technical interviews and coding tests, which assess both theoretical knowledge and practical application, often requiring demonstration of coding skills in real-time.
Some candidates reported having to deliver presentations or participate in group exercises, which evaluate both technical understanding and interpersonal skills, adding a layer of complexity to the assessment.
The interview process is generally structured in multiple stages, often involving HR, technical leads, and peer interviews, each focusing on different aspects of the candidate's fit and skills.
Candidates noted varying levels of feedback during interviews, with some feeling that the evaluation was rigid and score-based, while others experienced a more conversational and supportive atmosphere.
While many candidates felt positively about their interview performance, external factors such as funding issues or organizational changes sometimes affected the final outcome, leading to unexpected results.