Articles
DV Trading SWE Intern 2027: Coding Assessment, C++, and Trading Systems Interviews
Prepare for the DV Trading SWE Intern 2027 process: coding assessments, C++, Python, low-latency systems, candidate reports, and a focused plan.
A DV Trading software engineering internship is easy to misread as a standard algorithms screen with a finance logo attached. The official Summer 2027 posting points to something more demanding: interns work inside a mature production codebase, build low-latency trading tools, and own the correctness of code accelerated by AI.
That changes how you should prepare. DV Trading does not publicly define one universal 2027 online assessment, provider, timer, or cutoff. Historical candidates have reported coding assessments, TestGorilla, live coding, C++ or Python work, database questions, and project-based problem solving, but those reports span different roles, locations, and recruiting cycles.
Start with software engineering interview questions to diagnose whether your weakest area is coding, C++ concurrency, system design, or debugging. This guide separates official 2027 requirements from candidate reports and turns both into a focused preparation plan.
Quick answer: what should you expect?
| Question | Best current answer | Preparation decision |
|---|---|---|
| Is there a confirmed DV Trading OA format? | No official source publishes one universal 2027 provider, question count, timer, or cutoff. | Use your invitation as the source of truth. |
| Which languages matter? | The official role asks for C++ and/or Python. | Choose one interview language, but review C++ performance concepts even if you code in Python. |
| What is the role really testing? | Correct implementation inside an existing, performance-sensitive production system. | Practice code navigation, tests, debugging, ownership, and clear trade-offs. |
| Do trading concepts matter? | Yes, as engineering context: market data, orders, latency, risk checks, and failure handling. | Learn the system vocabulary without turning SWE prep into a trader math course. |
| Should you expect live coding? | A 2025 software engineer report described a coding assessment followed by live coding, but DV does not guarantee that sequence. | Practice explaining and revising code aloud. |
The safest strategy is to prepare for a production engineering interview, not an alleged fixed OA. You should be able to solve a timed coding problem, explain C++ or Python choices, inspect an unfamiliar codebase, and reason about a low-latency trading component.
What the official Summer 2027 role confirms
DV Trading's New York posting says interns join small groups within development and/or trading teams. They help build low-latency applications, systems, and trading tools, then deliver a well-scoped project that integrates with an established production codebase. That is unusually specific language for an internship.
The posting asks for proficiency in C++ and/or Python, strong quantitative and analytical problem solving, and the ability to work on numerical or performance-sensitive problems. It also explicitly expects candidates to read and navigate existing code rather than assume every task starts from a blank file.
Another current signal is AI-assisted development. DV says interns may use AI coding tools to move faster, but must critically review the output and own its correctness. A strong interview answer therefore cannot end with "the tool generated it." You need to explain the contract, test the edge cases, and defend every important trade-off.
The New York role is onsite five days per week, targets students graduating between Winter 2027 and Summer 2028, and lists compensation of $50 per hour. DV also lists a London version of the internship, so location-specific logistics and interview steps may differ.
Does DV Trading use a coding assessment?
Possibly, but the company has not published a standard 2027 assessment. The official internship description does not name TestGorilla, HackerRank, CodeSignal, Codility, a question count, a time limit, proctoring controls, or a passing score.
A March 2025 Glassdoor report for a DV Trading software engineer described a recruiter screen, a coding assessment, live coding with a team member, and a final problem-solving conversation based on past work. A separate February 2025 London graduate software developer report described a roughly three-hour TestGorilla assessment with the camera on and test-window tracking. That candidate reported two medium-to-hard algorithm questions, one database question, and multiple-choice material on OOP, algorithms, and data structures.
Older Reddit discussions also mention TestGorilla, a custom Python prompt with predefined functions, and a SQL component. These are useful clues about the range of skills DV has tested. They are not evidence that the 2027 SWE intern assessment will repeat the same platform or sections.
When your invitation arrives, record five facts before preparing from rumors: provider, allowed languages, total and per-section time, monitoring rules, and deadline. If the invitation contradicts any public report, the invitation wins.
How to prepare for the coding portion
Build a reliable algorithm baseline
Review arrays, strings, hash maps, sorting, binary search, heaps, graphs, intervals, and stateful simulation. Aim to solve medium-level problems cleanly, but do not measure readiness only by how many patterns you recognize. Hidden tests usually expose incomplete contracts, not a lack of obscure tricks.
Use a repeatable sequence: clarify inputs and constraints, state the invariant, choose the data structure, write the smallest correct version, test edge cases, then discuss complexity. For trading-related prompts, pay particular attention to duplicate messages, ordering, cancellation, partial updates, integer overflow, and timestamp ties.
Write C++ that is safe and explainable
If you choose C++, review value versus reference semantics, object lifetime, RAII, smart pointers, const correctness, templates, container complexity, iterator invalidation, and move semantics. You should recognize where heap allocation, copying, virtual dispatch, cache misses, or lock contention can affect latency.
Do not reach for lock-free code merely because the firm cares about speed. Start with the simplest design that preserves correctness and ordering. Then explain where measurement shows contention, what ownership model makes a lock-free structure safe, and how you would test it under race conditions.
Use Python with production discipline
Python can be a strong interview language when the prompt values clarity, data manipulation, or rapid implementation. Be ready to discuss data-structure costs, mutability, generators, testing, and where Python's runtime may become the bottleneck. If low latency is central, explain what would remain in Python and what might move to C++ or a compiled extension.
Existing-codebase and AI-assisted coding can be decisive
The official posting makes codebase navigation a core requirement, so practice beyond blank-editor LeetCode. Take a small repository and locate the entry point, data model, external boundaries, tests, configuration, and error paths. Before changing code, reproduce the behavior and identify the narrowest safe edit.
A good repository task answer starts with a map: "This request enters here, state changes in this module, and these tests cover the contract." Then form a hypothesis, add or update a focused test, implement the smallest change, and run the relevant suite. Mention backward compatibility, observability, and rollback when the blast radius is meaningful.
For AI-generated code, apply the same standard. Check invented APIs, silent exception handling, concurrency assumptions, input validation, complexity, and test coverage. Speed earns little credit if you cannot establish why the result is correct.
Trading-systems topics worth learning
You do not need to become a commodities trader to interview for software engineering. You do need enough domain language to reason about the systems your code may support. Understand the lifecycle of market data, an order, an acknowledgement, a partial fill, a cancel, and an execution report.
For an order book, explain price-time priority, bids versus asks, and efficient add, match, and cancel operations. For market data, discuss sequence numbers, snapshots plus incremental updates, gap detection, stale feeds, and backpressure. For order entry, discuss validation, pre-trade risk checks, idempotency, deterministic ordering, and recovery after an ambiguous timeout.
Low latency is not simply "use C++." Separate average latency from tail latency, throughput from jitter, and algorithmic complexity from memory behavior. A strong candidate can discuss allocations on the hot path, cache locality, batching, locks, queues, serialization, network I/O, clocks, profiling, and the cost of durability.
Correctness remains non-negotiable. A fast system that duplicates an order, loses a cancel, or replays events in a different order is not a successful trading system. Frame every optimization against invariants and measurable latency budgets.
What later interview rounds may evaluate
The 2025 software engineer report suggests DV may move from an assessment into live coding and project-based problem solving. Prepare to extend a working solution, respond to a changed requirement, and explain what you would measure before optimizing it. Interviewers may care as much about how you revise the code as how quickly you produce version one.
Your project deep dive should cover one technically substantial system. Explain the original constraint, your personal ownership, architecture, hard bug, performance or reliability trade-off, testing strategy, measurable result, and what you would change now. Be ready for follow-ups that challenge a number or assumption.
Behavioral answers should show that you can work closely with developers and traders. Prepare examples about ambiguous requirements, disagreement, production risk, a mistake you owned, and a time you improved a system without over-engineering it. Use behavioral and leadership practice to make those stories concise and evidence-based.
A seven-day DV Trading preparation plan
| Day | Focus | What to do |
|---|---|---|
| Day 1 | Invitation and baseline | Record the exact rules, then complete one timed coding set and log every missed edge case. |
| Day 2 | C++ or Python depth | Review your chosen language's memory, container, error-handling, and testing behavior. |
| Day 3 | Existing repository | Map one unfamiliar codebase, reproduce a bug, make a small patch, and explain the test. |
| Day 4 | Trading systems | Design an order book and trace add, match, partial fill, cancel, duplicate, and restart cases. |
| Day 5 | Performance and concurrency | Profile a small program, identify one bottleneck, optimize it, and verify correctness under load. |
| Day 6 | Live interview | Run a 45-minute coding mock plus a project deep dive with aggressive follow-up questions. |
| Day 7 | Full simulation | Recreate the invitation's timing, review logistics, and stop adding new topics. |
Frequently asked questions
Is the DV Trading SWE Intern OA automatic?
DV Trading does not publicly state that every Summer 2027 applicant receives an automatic assessment. Receiving an invite confirms that you reached that stage, but it does not reveal the final screening threshold or guarantee an interview.
Does DV Trading use TestGorilla?
Some historical candidates reported TestGorilla, including a 2025 London graduate software developer. The current 2027 internship posting does not name an assessment provider, so verify the platform in your own invitation.
Should I use C++ or Python?
Use an allowed language in which you can write, test, and explain correct code quickly. Choose C++ when you can handle ownership and container details confidently; choose Python when it materially improves your implementation reliability. Still prepare to discuss why low-latency components may use C++.
Will the interview include probability or mental math?
DV's official SWE internship asks for quantitative and analytical problem solving, but it does not announce a trader-style mental-math test. Candidate reports from other DV roles include probability and brainteasers, so review fundamentals without letting them replace coding and systems preparation.
How hard is the coding assessment?
One 2025 report described two medium-to-hard algorithm questions plus database and fundamentals sections, while older reports describe custom prompts. Difficulty can vary by role and cycle. Prepare for complete medium-level implementation and the ability to reason through a harder follow-up.
What happens after the assessment?
A historical software engineer report described live coding and a final project-based problem-solving round. DV does not publish a universal 2027 sequence or response time, so continue other applications while tracking your own stage.
Final takeaway
Prepare for DV Trading as a software engineer joining a performance-sensitive production team. Timed algorithms matter, but so do C++ or Python fluency, codebase navigation, tests, concurrency, low-latency trade-offs, and the ability to own AI-assisted code.
Sources and Further Reading
- DV Trading: Software Engineer Intern - Summer 2027, New York
- DV Trading: Software Engineer Intern - Summer 2027, London
- DV Trading current job board
- Reddit: historical DV Trading software development assessment discussion
- Reddit: historical DV Trading TestGorilla discussion
Research note: This guide was checked on August 23, 2026. Assessment providers, monitoring rules, interview stages, and timelines can vary by role, location, and recruiting cycle; your invitation is the source of truth.