Real, anonymous reports from people who interviewed for Quantitative Analyst at G-Research, newest first and distilled into what to expect across the loop.
My interview journey was pretty compact and structured. After the initial screening step, I went through two rounds: first a coding round, and then an onsite divided into three segments. Each segment focused on different parts of the technical stack—system design, algorithms, and coding again—and all of them were run by members of the quant dev team.
The sequence was a bit of a marathon right from the start. I had an initial quiz, then a triage interview over Zoom, and then a string of mentor interviews. The whole structure ended with a final conversation with the research manager. Even though it was all focused on the job, I felt like the total load was heavier than I expected for the level I was applying for.
Candidates typically start with a timed online assessment focused on probability, statistics, and basic coding, often featuring a mix of straightforward and tricky questions designed to challenge their quantitative reasoning under time constraints.
The interview process usually consists of multiple technical rounds, often including coding, algorithms, and system design, with a strong emphasis on both breadth and depth of knowledge across quantitative topics.
Candidates report a fast-paced interview environment where quick, confident responses are expected, making it crucial to manage time effectively and maintain composure throughout the technical discussions.
Interviews often include discussions about candidates' backgrounds and motivations for transitioning into finance, requiring them to articulate their experiences clearly alongside technical skills.
Candidates generally receive timely feedback after interviews, which is appreciated, but some report inconsistencies in communication and follow-through during the scheduling and assessment phases.
The interview environment is described as generally friendly and supportive, although some candidates noted that the tone can vary, impacting their overall experience and comfort level during technical evaluations.