Software Engineer applicants have rated the interview process at G-Research with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 44% positive. To compare, the company-average is 51% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 15 days to get hired, when considering 16 user submitted interviews for this role. To compare, the hiring process at G-Research overall takes an average of 23 days.
Common stages of the interview process at G-Research as a Software Engineer according to 16 Glassdoor interviews include:
Skills test: 31%
Phone interview: 28%
One on one interview: 19%
Background check: 9%
Presentation: 6%
IQ intelligence test: 3%
Group panel interview: 3%
Here are the most commonly searched roles for interview reports -
I applied through a staffing agency. The process took 1 week. I interviewed at G-Research (London, England) in Mar 2018
Interview
First stage was a programming exercise that could be done at home - rather tricky, but very fun to work on.
This was followed by on-site interviews, which lasted ca. 4 hours with 3 interviews in total, each led by 2 people. These mostly focused on technical questions, testing both a broader understanding of programming principles, as well as some more in-depth questions. The questions were fair and well thought through; each solvable rather quickly in principle, but allowing for different approaches while leaving room to explain one's thought process behind whatever approach was taken; and presented in a way that would allow the interviewers to give certain tips to formulate a solution, rather than strict "do or do not know it"-questions).
Feedback after the interview was given within 3 working days.
All in all, a tough but very enjoyable experience - which is quite a rarity to say about any job interview.
The interview process was thorough and well structured. It focused primarily on data structures and algorithms, and the level was broadly in line with what you would expect for a software engineering interview of this type. I cannot share specific details of the questions, but standard preparation in algorithms, data structures, problem solving, and coding under interview conditions should be sufficient. Overall, it felt rigorous but fair.
There were mostly algorithmic questions to be solved on a whiteboard. Then, after a lunch with a couple of the junior staff, the tell you whether you’re into the next round. There is also a test beforehand.
2-3 parts depending on team. Pretty in depth on topics. 2 coding rounds I believe. Interview process is fairly quick. It’s not a process that takes 3-4 weeks. 2 weeks max, 1 week if you’re really adamant.