J'ai postulé via la recommandation d'un employé. Le processus a pris 5 semaines. J'ai passé un entretien chez DRW (Montréal, QC) en juin 2020
Entretien
Job Description was full of different technologies (Python, Java, JS, C#, Spring, .Net and others). And then I learned that they put one posting for multiple positions. There are six interviews including assessments and I got rejected after 3rd interview (took them five weeks for those three interview)
Questions d'entretien [1]
Question 1
Mixed behavioral and technical questions. Such as what is a weakness of yours?, Describe a challenge you had at work, A conflict happened with a co-worker before?
They also showed me a table in canada.ca website and asked me how to fetch information.
The interview ended with them explaining about next process and assessment which I never received.
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.