Articles · DRW

DRW SWE Intern OA 2027: Question Types, Deadlines, and What Comes Next

DRW SWE Intern OA 2027 guide: Codility question types, deadline conflicts, a three-problem practice plan, hidden tests, and what happens after the OA.

Updated August 15, 2026: DRW's Summer 2027 Software Developer Intern recruiting cycle is active, and candidates are already receiving online assessments. The confusing part is not only the coding: one current applicant reported an initial instruction to finish within three days, followed by a reminder containing a later, exact UTC deadline.

That conflict is a useful warning. The DRW SWE OA is not a test you should prepare for from a single Reddit comment, an old LeetCode post, or a Quant Trading thread. DRW officially confirms a Codility-based coding challenge for Software Developer candidates, but your own invitation controls the timer, deadline, language options, and assessment rules.

The DRW coding challenge rewards correct algorithms that also meet performance constraints. Your invitation remains the source of truth for the exact deadline and format.

DRW SWE Intern OA 2027: Quick Answer

DRW's official preparation guide says Software Developer applicants receive a coding-based technical challenge and links candidates to a Codility sample test. It says tasks can vary in difficulty and scenario, and that solutions are evaluated for both correctness and performance. DRW does not publicly promise one universal 2027 question count or time limit.

Historical DRW Software Developer reports also frequently describe a three-problem Codility test, but this remains a preparation model rather than a guaranteed specification for every 2027 office or candidate.

After the OA, DRW's published engineering process normally moves successful candidates to a roughly 45-minute Zoom interview, followed by a final round with additional coding and technical interviews. DRW also warns that its process can vary, so treat this as the standard path rather than an inflexible contract.

What Is Confirmed, Reported, and Still Unknown?

OA discussions become misleading when official facts and individual experiences are presented with equal certainty. This evidence map shows what you can rely on today.

Claim	Evidence status	How to use it
Software Developer candidates receive a coding challenge	Official DRW guidance	Prepare algorithms and implementation, not probability puzzles from Quant roles.
DRW directs candidates to a Codility sample test	Official DRW guidance	Practice function-based tasks, custom tests, complexity, and hidden-test discipline.
Tasks vary in difficulty and score correctness plus performance	Official DRW guidance	A passing sample is not enough if the solution times out at the maximum constraint.
Three-day completion window	One current 2027 candidate report	Do not generalize it. Follow the deadline in your own invitation.
Exact 2027 cutoff, proctoring configuration, and response time	Not publicly standardized	Read the invitation and avoid claims based on another role or recruiting batch.

Do Not Mix the SWE OA with DRW Quant Assessments

This distinction matters more at DRW than at many companies. The official technical-challenge guide separates Software Developer assessments, which are coding based, from Quantitative Trader and Researcher assessments, which test logical and quantitative skills.

Recent Quant candidates discuss probability questions and, in some cases, recording from a phone. Those reports do not establish the rules for the Software Developer OA. If your invitation says Software Developer Intern, prepare coding fundamentals and follow only the proctoring instructions attached to that assessment.

What Question Types Should You Expect?

DRW describes Codility tasks as scenario-based functions that can range from direct computation to game-like problems. The common thread is not a specific LeetCode tag. It is turning a wordy scenario into a precise invariant, implementing it cleanly, and proving that the complexity survives large inputs.

You do not need to predict which three will appear. You need enough range that none of those styles feels unfamiliar under a timer.

DRW officially emphasizes correctness and performance. The practice categories come from stored DRW questions and historical reports, not a published 2027 syllabus.

Simulation and structural shortcuts

A simulation problem may describe rounds, queues, transfers, or a game. The naive solution often follows every event literally, while the stronger solution notices what state actually changes. Write down the invariant before coding, then ask whether the whole history is necessary or whether a compact summary is enough.

Graphs, grids, and constructive output

One stored DRW problem asks for movement instructions that cover connected floor cells. This is less about memorizing DFS and more about constructing a valid path, proving it stays inside the region, and showing the output length fits the limit. Practice translating a traversal into explicit commands and testing the commands with a small simulator.

Greedy choices, matching, and dynamic programming

Some prompts hide an assignment or optimization problem inside a business story. A two-choice slot problem, for example, can become a graph-component condition rather than an expensive search over every assignment. Look for monotonicity, exchange arguments, component structure, or a state small enough for dynamic programming.

Bitmasks and small-domain compression

When a problem depends on a small fixed universe, such as the ten decimal digits, represent the relevant set with bits. That can turn an impossible pairwise search across hundreds of thousands of values into a scan over at most 1,024 states. State compression is valuable only when you can explain what information the mask preserves and what it intentionally discards.

How to Allocate a 150-Minute Practice Session

If your actual invitation gives a different timer, scale the plan proportionally. For a three-problem, 150-minute mock, spend the first eight to ten minutes reading all prompts and constraints. Choose the problem with the clearest correct path rather than assuming the displayed order matches difficulty.

Budget roughly 30 to 35 minutes for the first complete solution, 40 to 45 minutes for the second, and 45 to 50 minutes for the deepest task. Protect the final 15 minutes for adversarial tests, complexity repairs, and verifying that every required function signature and return type is correct.

Use a switch rule: if you have spent six focused minutes without a viable invariant or state definition, move to another problem. A complete, tested solution plus a credible second solution usually creates more evidence than three half-built implementations.

How Codility Hidden Tests Change Your Strategy

Codility-style tasks commonly evaluate more than the examples you can see. DRW explicitly says performance matters, so a correct quadratic solution may still score poorly on large cases. Read the maximum input size before choosing a data structure and estimate the number of operations before writing the full implementation.

For each problem, create a compact test set: the smallest legal input, a normal case, duplicates or ties, an ordering reversal, a boundary value, and one case near the performance limit. If multiple outputs are valid, test validity rather than comparing against one exact expected string.

Do not optimize blindly. First make the baseline correct on tiny cases, then replace the bottleneck while keeping the same invariant. This gives you a reference implementation for differential testing and reduces the risk of introducing a fast but subtly wrong solution.

DRW OA Deadlines: What If the Emails Conflict?

A July 2026 applicant reported that the initial DRW SWE OA email required completion within three days, while a later reminder listed a specific August 7 deadline in UTC. One report cannot establish DRW's universal policy, but it shows why candidates should not rely on a remembered number of days.

Use the most recent, most specific timestamp shown in your assessment portal and email. If two instructions genuinely conflict, screenshot both without exposing assessment content, contact the recruiter or support address, and plan as though the earlier deadline applies until you receive written clarification. Never assume that a reminder silently extends the original window.

Resolve the deadline before optimizing your study schedule. After submission, shift immediately toward the technical and behavioral Zoom interview.

Does Everyone Get a DRW OA?

DRW does not publicly say that every Software Developer applicant receives an assessment. A recent Montréal applicant asked whether the invite was automatic, while another applicant in the discussion reported a rejection without receiving one. That small sample suggests an OA is not guaranteed, but it cannot reveal how strict the screen is.

Treat the invitation as an opportunity to compete, not proof that the rest of your application has already been approved. Historical candidates have reported strong or even perfect OA performance without advancing, which suggests resume fit, office needs, and the overall applicant pool may still matter after the test.

What Happens After the DRW SWE OA?

DRW's published software-developer process says candidates who pass the coding challenge are typically invited to a 45-minute Zoom interview. DRW's phone-interview guidance says this conversation includes technical and behavioral questions, explores your work, coursework, and research in depth, and may include coding, so have a computer ready.

The standard final stage is an onsite or final-round interview with another coding challenge and deeper technical conversations. DRW recommends reviewing advanced computer science concepts for developer roles. The current Summer 2027 internship listing highlights object-oriented design, data structures, algorithms, multithreading, computational intelligence, real-time programming, and clear communication.

While waiting, prepare two tracks. Keep solving company-specific coding questions, but also rehearse concise explanations of your projects: the architecture, your personal contribution, the hardest bug, one trade-off, and what you would change.

A Five-Day DRW OA Preparation Plan

Day 1: Run a 90-minute diagnostic across three different patterns. Review every failed test and classify the cause. Day 2: Drill simulation, arrays, and strings, with a complexity estimate before every implementation.

Day 3: Practice graphs, grids, matching, and one bitmask problem. Build small brute-force oracles for comparison.

Day 5: Review mistakes rather than learning a new advanced topic. Verify the invitation deadline and time zone, test your device and network, read the permitted-resource rules, and begin early enough to handle a platform issue without racing the cutoff.

DRW SWE Intern OA 2027 FAQ

Is the DRW Software Developer OA on Codility?

DRW's official technical-challenge guide links Software Developer candidates to a Codility sample test and describes the coding tasks they should expect. Your invitation should still be checked for the current platform and rules because recruiting configurations can change.

How many questions are on the DRW SWE OA?

DRW does not publish one universal 2027 count.

How long is the DRW coding assessment?

DRW officially says the required duration will be provided in the introduction email. Use the timer in your own invitation as the source of truth.

What score do you need to pass?

DRW does not publish a universal cutoff. Correctness and performance both matter, but a perfect score is not a public guarantee of advancement. Optimize for complete, efficient, well-tested solutions and continue preparing for the next round after submission.

Is the DRW SWE OA proctored?

No single public DRW source specifies one proctoring setup for every 2027 Software Developer assessment. Do not import camera or phone-recording claims from Quant roles. Follow the consent screen and instructions attached to your own Codility invitation.

How long does DRW take to respond after the OA?

DRW does not publish a fixed OA-to-interview turnaround. Candidate reports range from quick rejections to waits of days or weeks. Monitor email and the application portal, but prepare for the 45-minute Zoom and keep applying elsewhere rather than pausing your search.

Final Takeaway

The DRW SWE Intern OA 2027 is best understood as a performance-aware Codility coding challenge, not a Quant probability test and not a fixed set of leaked prompts. The strongest preparation combines broad algorithm coverage with disciplined constraint reading, self-designed tests, and a firm deadline plan.

Then prepare your resume deep dive, object-oriented design, fundamental computer science, and behavioral evidence for the Zoom round that may follow.

Sources and Further Reading

Research note: This guide was checked on August 15, 2026. DRW can vary assessment settings by office, role, and recruiting batch. Follow the instructions in your current invitation and do not treat candidate reports as official policy.