J'ai postulé via un recruteur. Le processus a pris 6 semaines. J'ai passé un entretien chez DRW (Londres, Angleterre) en janv. 2024
Entretien
I applied for the Software Engineer - Elixir role at DRW for their London office.
I went through an initial screen that involved having a conversation about my background. The next interview was an interview with the hiring manager.
Unfortunately, I went into the hiring manager interview with wrong expectations because I was informed that the interview would be more of an in-depth technical conversation about my previous roles.
What actually happened was that it was a full-blown technical interview about Elixir. Normally, I would be able to answer such questions, but my mind went blank because of the fact that I was blindsided by what the interview actually was.
I did not pass the second round so I do not know what the next steps will be after this.
Questions d'entretien [1]
Question 1
What is a Process?
How does Elixir handle processes?
J'ai postulé en ligne. J'ai passé un entretien chez DRW
Entretien
Leetcode like question with follow ups on c++ concepts like virtual memory, address space, etc. Coding everything from scratch and there’re also weird concepts like function pointer. Question was not too hard but need to remember concepts and syntax clearly
J'ai passé un entretien chez DRW (Londres, Angleterre)
Entretien
HR, take home coding tests, behavioral, technical discussion, live codings for several rounds.
The live codings are a bit hard. Some are about problems solving, some are about data structure and algorithms.
J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez DRW (Londres, Angleterre) en août 2025
Entretien
Did a set of interviews in summer 25. The interviews were not that difficult, mostly problems you'll face in real life. The interviewers themselves were mostly nice, although a couple seemed like they didn't care, not very involved in the process.
Got rejected due to 2 sections having "mixed signals": one generic "not deep enough", the other didn't like the approach to solving a problem (it was solved on time anyway). Funnily enough, got praised for using the same approach in other section. Mixed signals also came from the people who wouldn't have been on the same team.
It would be nice if interviewers were aligned on evaluation criteria, otherwise it becomes a guessing game.
Other that that it was a positive experience and the rejection was delivered by phone, not a generic email.
Questions d'entretien [1]
Question 1
Some very down-to-earth problem on coding section, pleasantly surprised.
Unfamiliar algo problem, more like medium-hard.
And a data modelling exercise.
