G-Research Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 75 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at G-Research.
G-Research
Software Engineer
Mid Average Positive experience Decline offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Recruiter call
Interview formats
Technical Coding System Design Behavioral
So the interview process had four rounds. The first round was for an hour. It was split into two parts: 30 minutes for computer science fundamentals and 30 minutes for pair programming where I could use any language I wanted. The second round was two hours long. The first hour was spent solving an algorithmic problem, which wasn't too hard. The second hour involved solving a software architecture problem, focusing on OOP. The third round was also an hour and focused on a high-level system design task. I think it was about designing a chat system, but I can't recall the exact task. Finally, the fourth round was a casual chat with the hiring manager about my career goals and motivations. It wasn't technical at all.
Confirmed questions1 question
- Can you tell me about the types of testing you're familiar with?
G-Research
Software Engineer
Entry Average Positive experience No offer 3 rounds
Interview process
Take home Recruiter call Technical screen
Interview formats
Coding Behavioral Technical
So the interview process started with a coding assessment that you had a week to complete. After that, there was a behavioral interview, and then finally a technical interview. They were pretty clear about what the technical interview would cover, so the whole thing felt pretty transparent. The behavioral part was especially well done, they really knew how to ask the right questions.
Confirmed questions3 questions
- Can you tell me about your coding assessment from earlier?
- Let's talk about your resume and experience.
- What do you know about networking?
G-Research
Software Engineer
Intern Average Neutral experience No offer 2 rounds
Interview process
Technical screen Group Presentation
Interview formats
Coding Group System Design
I interviewed in October 2020. The whole process was pretty smooth, with the assessment centre being completely remote. It included a group design session and then some individual interviews with other software engineers. They said there were 2-3 questions to get through in the technical interview, which were medium to hard difficulty. The only downside is I never heard back after the assessment centre.
Confirmed questions2 questions
- Answered 3 LeetCode-style questions during the technical interview.
- Participated in a group system design session.
G-Research Software Engineer Interview Questions
Quoted word for word from G-Research interview reports.
“What is the time complexity for operations on common containers?”
Read reports →“How would you implement binary search in a continuous space?”
Read reports →“Could you describe the difference between TCP and UDP?”
Read reports →“Could you write a program to determine if a string is triangular, using examples like 'a', 'abb', 'accbbb', or 'xyyzzzqqqq'?”
Read reports →“Could you implement a "most recently used" cache eviction strategy as part of a memoized function?”
Read report →“Do you need to use the restroom?”
Read report →“Can you outline the key changes in Java since 2005?”
Read report →“Given the appointments of n people and a period of time (in ms), write a software that finds the soonest moment in which you can organize a meeting with all of them present which lasts that long. You'll be given a premade class for appointments and you need to build upon it.”
Read report →“Can you explain your understanding of garbage collection in .Net?”
Read report →Formats, difficulty and experience
Across all 75 G-Research interview reports.