Real, anonymous reports from people who interviewed for Software Engineer at G-Research, newest first and distilled into what to expect across the loop.
My interview journey felt rigorous and heavily centred on algorithmic problem solving. It started with a structured process that stayed focused on data structures and algorithms, with the difficulty level described as broadly in line with a serious software engineering interview—except for me, where it leaned hard. I remember the preparation being clearly applicable to standard coding interviews, but the actual tasks still demanded full attention under pressure.
I went through an experience that started with an upfront test and then moved into mostly algorithmic whiteboard work. After that, there was also a lunch with junior staff where I got a sense of how people interacted day to day, and then I waited to hear whether I was pulled into the next round.
The interview process typically begins with a recruiter screening followed by an online coding assessment, often using HackerRank. Candidates should prepare for a mix of general programming questions and algorithmic challenges during this initial stage.
Candidates can expect multiple technical interviews focused on algorithmic problem solving and system design, often involving whiteboard coding or pair programming. Emphasis is placed on reasoning and collaboration, so candidates should be prepared to discuss their thought processes and iterate on solutions.
Behavioral interviews are a key part of the process, assessing candidates' motivations, teamwork, and cultural fit within the company. Candidates should be ready to articulate their experiences and how they align with the company's values.
The overall difficulty of the interviews is reported to be high, with candidates needing to perform consistently across various rounds. Candidates should practice under time pressure and be prepared for challenging questions that test their depth of knowledge.
Candidates have noted mixed experiences regarding communication and feedback throughout the process, with some reporting delays or lack of closure after interviews. It's advisable to follow up proactively and seek feedback to understand areas for improvement.
While many candidates found the interview process structured and fair, some expressed frustration over poor communication and follow-through from the recruitment team. Candidates should be prepared for a potentially lengthy process and maintain realistic expectations about outcomes.