Real, anonymous reports from people who interviewed for Software Engineer at Drw, newest first and distilled into what to expect across the loop.
I made it pretty far—up to the fourth technical round. The sequence felt like multiple technical screens building on each other until I reached a C++-focused interview where I got a C++ problem question. After that, the conversation shifted toward my personal projects, which was a nice change of pace compared to the problem-solving.
I started with an internal recruiter reach-out and it quickly turned into a hiring push for a very senior trade support type of role. My first call was with HR and it felt like it went well, and then I met the hiring manager. That interview focused mostly on my background and on learning about the team and what the role actually looked like. It felt a little unfocused on their side, but overall it was still a decent conversation.
Candidates typically begin with an online assessment that includes LeetCode-style coding questions, often focusing on algorithms and data structures. The assessments vary in difficulty but are generally seen as a baseline check of coding fluency.
The technical interview rounds often delve into core programming concepts, including C++ specifics, operating systems, and system design. Interviewers emphasize understanding of low-level details and real-world problem-solving rather than just theoretical knowledge.
The interview process is generally structured with a clear progression from online assessments to technical interviews, often culminating in a superday or multiple back-to-back interviews. However, candidates report varying timelines and communication issues that can lead to frustration.
Some candidates experience behavioral interviews that assess cultural fit and interpersonal skills, often mixed with technical discussions. These rounds aim to gauge how well candidates align with team dynamics and company values.
Candidates frequently express concerns about the lack of timely feedback and communication throughout the process, which can lead to uncertainty and frustration. Many report long gaps between interview stages without clear updates.
Rejections often come without detailed feedback, leaving candidates unsure about their performance. Many reflect on the process as rigorous but feel that the final decisions hinge on factors not clearly communicated during the interviews.
