Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso DRW
Colloquio
I got rejected on the take home assignment, so can't say too much for what comes next.
1. Hand-wavey conversation to see if you understand big-O complexity of sorting algorithms.
2. Take home assignment to build a variant of tetris in your language of choice,
Overall, and compared to other firms in this industry, this is a hilariously poorly thought out process from DRW. Take home tests are negative experiences for candidates across the board, because they are usually poorly specified, and weigh so heavily on the candidate's efforts, and not at all on an interviewers. If candidates are spending 2-4 hours on a submission, DRW interviewers should take that time to review it (not 20 minutes and going "it doesn't run the way ours does so fail"). The effort equilibrium is out of whack completely.
Domande di colloquio [2]
Domanda 1
Given a galaxy, and an arbitrary point in the galaxy, how would you find the K nearest stars
Build a variant of tetris where after a clearing a line, shapes don't fall into empty spaces below (unless an entire line is cleared). Return the height of the tallest column of blocks at the end of a given set of pieces.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso DRW
Colloquio
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
Ho sostenuto un colloquio presso DRW (Londra, Inghilterra)
Colloquio
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.
Ho presentato la mia candidatura online. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso DRW (Londra, Inghilterra) nel mese di ago 2025
Colloquio
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.
Domande di colloquio [1]
Domanda 1
Some very down-to-earth problem on coding section, pleasantly surprised.
Unfamiliar algo problem, more like medium-hard.
And a data modelling exercise.
