Solicité el puesto a través de un captador. Acudí a una entrevista en G-Research
Entrevista
Approached by a recruiter then arranged a phone interview with an engineer in the company.
Phone interview was terrible - the interview was late, didn't break the ice or really introduce themselves and just launched into a series of quick fire questions with a tone of voice making it sound as if they'd rather be doing anything else. This was then followed by a simple coding test.
Overall an off putting experience (as were some of the responses to questions I asked about engineering which I can't tell the answers to)
Preguntas de entrevista [1]
Pregunta 1
NDA but essential a CS fundamentals pop quiz + coding test
Acudí a una entrevista en G-Research (Londres, Inglaterra)
Entrevista
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.
