Real, anonymous reports from people who interviewed for Software Engineer at Drw Holdings, newest first and distilled into what to expect across the loop.
I interviewed for a Software Engineer path that shifted from a very senior trading support need, and it felt moderately paced with strong experience-fit questions.
I went through an OA-first process that culminated in an intense technical onsite, and while it was well-structured, I didn’t get to an offer.
Candidates typically start with a timed online assessment that includes multiple coding questions, often resembling LeetCode-style problems. Performance in this stage is crucial, as many candidates report being cut off early based on their scores.
Following the OA, candidates participate in one or more technical interviews that focus on algorithms, data structures, and sometimes language-specific details, particularly in C++. The interviews can vary in difficulty but generally require a solid grasp of core computer science concepts.
Candidates often face a series of back-to-back interviews during an onsite or superday, which may include live coding, system design questions, and discussions about previous projects. The intensity and structure of these sessions can vary, but they are generally seen as demanding.
Behavioral interviews are integrated into the process, assessing candidates' soft skills and cultural fit within the team. These discussions may occur at various stages, including the final rounds, and can significantly influence the hiring decision.
Candidates frequently report issues with communication and feedback throughout the interview process, including delays in scheduling and a lack of follow-up after interviews. This can lead to frustration and uncertainty about their standing in the process.
Many candidates experience rejections despite strong performances, often due to fit with specific team needs or competition from other candidates with more relevant backgrounds. Persistence and follow-up can sometimes lead to re-engagement opportunities.
