DRW's Interview Process (2026)

Blog / DRW's Interview Process (2026)
DRW Interview Process
DRW's software engineer interview process is rigorous and highly selective, but it follows a fairly predictable structure that most candidates can prepare for. Here's a general picture of what you can expect:
  • Online Assessment (OA): A timed coding challenge hosted on platforms like Codility or HackerRank, typically featuring 2 to 3 problems of increasing difficulty. Most candidates report a window of around 90 to 150 minutes, with recent reports pointing toward 150 minutes for three questions.
  • Technical Phone Screen: One or two live coding sessions over Zoom, usually around 45 to 60 minutes each, using a shared editor like CoderPad. Expect a medium-difficulty problem followed by deep-dive follow-up questions on language internals, such as JVM behavior or C++ memory management.
  • Onsite Super Day: A half-day of back-to-back interviews, usually 4 to 6 sessions of around 45 minutes each, held at DRW offices or virtually. Rounds typically span whiteboard coding, system design, senior engineer technical discussions, and a behavioral interview.
  • Hiring Committee Decision: After the super day, the hiring committee reviews all feedback before making a final call. Most candidates hear back within 1 to 2 weeks of their onsite.
To prepare effectively, focus your study plan across these key areas that DRW consistently tests:
  • Data Structures & Algorithms (DSA): Algorithmic coding problems tested at every stage, from the OA through to the onsite whiteboard rounds.
  • System Design: High-level architecture questions focused on scalable, low-latency trading systems.
  • Language Internals & Concurrency: Deep questions on Java and C++ internals, memory models, and multi-threading.
  • Take-Home Project: A programming assignment, sometimes a Tetris variant, focused on clean code and handling specific logic constraints.
  • Behavioral: Questions assessing how you handle mistakes, collaborate with others, and approach technical decisions.
1. Data Structures & Algorithms (DSA)DSA is tested at every stage of DRW's process, so it should anchor your preparation. The OA and phone screen lean toward medium-difficulty problems, while the onsite whiteboard rounds can go harder. Focus on arrays, sliding window, greedy, and dynamic programming as your core topics.Recent candidates report problems involving bipartite matching (such as Patient Scheduling), greedy swap logic, and string generation tasks like Generate a String With Characters That Have Odd Counts. These questions test whether you can reason about correctness and complexity, not just produce working code.DRW values bug-free execution above speed. Passing all hidden test cases matters more than finishing early, so take time to think through edge cases before you start typing. Work through our top 100 DSA questions to build the breadth and precision this process demands.
2. System DesignSystem design comes up in the onsite super day, usually framed around trading-adjacent scenarios. Expect questions like designing a high-availability trading database or a real-time data ingestion pipeline, where latency and fault tolerance are the main concerns.Familiarize yourself with the building blocks of low-latency systems before your onsite. Our High-Level Design topic page covers the core concepts you need, and you can also practice with the Stock Exchange (NASDAQ, NYSE) walkthrough, which is directly relevant to DRW's domain.For an interactive way to practice drawing out architectures end-to-end, use our System Design AI Whiteboard to work through designs before your interview.
3. Language Internals & ConcurrencyDRW's engineering teams work in performance-critical environments, so interviewers dig into how well you understand the tools you use. For Java, expect questions on garbage collection, memory models, and concurrency primitives. For C++, topics like virtual memory, address space layout, and lock-free data structures come up regularly.Concurrency is a particular focus. Be ready to explain the difference between lock-based and lock-free approaches, and to discuss real tradeoffs rather than just definitions. Brushing up on operating systems concepts will help you ground these discussions in fundamentals that interviewers expect you to know cold.This is often a differentiating topic at DRW. Candidates who can speak fluently about multi-threading and memory tend to stand out from those who only know the algorithmic side.
4. Take-Home ProjectSome candidates, particularly those interviewing for UK-based roles, report receiving a take-home assignment to build a variant of Tetris. The emphasis is on clean, well-structured code and correctly handling specific physics constraints, such as blocks not falling into empty spaces unless a full line is cleared.Think of this as a code quality exercise as much as a logic puzzle. DRW wants to see how you write production-grade code under realistic conditions, not just whether your solution runs. If you want to sharpen your take-home project skills, our take-home project practice resource is a good place to start.Note that this round is not universal. Not every candidate receives a take-home, so confirm with your recruiter what to expect for your specific team and location.
5. BehavioralDRW's behavioral round is relatively focused, typically assessing humility, ownership, and how you handle technical mistakes. Common questions include describing a time you optimized code for impact, or how you handled a situation where you got something wrong.Use the STAR principle to structure your answers, but put your energy into the Action component. Interviewers want to hear specifically what you did, not just what the team achieved. Vague answers that lean on "we" rather than "I" tend not to land well here.It also helps to know what DRW actually does. Showing awareness of their trading activity across fixed income, equities, and crypto signals genuine interest in the role, which the team values. For broader preparation, the Behavioral Playbook covers the question types and framing strategies that work best in finance-adjacent interviews.
ConclusionDRW's process moves quickly once it starts, often wrapping up within 3 to 5 weeks from application to offer. Start with DSA fundamentals, layer in system design and concurrency, and save behavioral prep for the final stretch before your onsite. Follow the DRW Interview Roadmap for a structured, stage-by-stage plan to get you ready.

About TechPrep

Never walk into a technical interview unprepared again. TechPrep empowers software engineers to stop guessing and start getting offers. We provide the exact questions asked by tech companies across Data Structures & Algorithms, System Design, Low-Level Design & Practical coding rounds. Don't leave your career up to chance. Join thousands of engineers who have successfully navigated the tech hiring maze and landed roles at top tech companies.