Real, anonymous reports from people who interviewed for Software Engineer at Virtu Financial, newest first and distilled into what to expect across the loop.
Get your personalized Virtu Financial Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Before I even spoke to anyone, I was sent an OA full of brainteasers that felt completely disconnected from what the role actually needed. The questions were algorithmic riddles with no obvious link to enterprise development or the day-to-day work in the frameworks the job would involve.
The whole thing gave me the sense that the assessment wasn’t measuring the skills that matter for the position. I didn’t progress, and honestly the disconnect left a sour impression right from the start.
6 months ago
Difficult Negative Austin, TX
My process started with a technical discussion that went deep into low-level systems topics like memory allocation, fragmentation and alignment, lock-free programming, and the kinds of internals you’d associate with mmap/malloc and allocator design. It sounded like the interviewer wanted to probe understanding beyond just surface-level coding.
What surprised me was how adversarial the session felt. I would start answering and then get interrupted repeatedly with “why?” follow-ups, often without enough time to finish my explanation or build toward a complete answer. Even though it was billed as a coding interview, the coding portion got pushed to the last 10–15 minutes, which made the evaluation feel rushed and lopsided.
6 months ago
Average Neutral United States
The process felt pretty structured at first: I’d do an OA coding assessment, then talk to a recruiter about what the rounds would look like, then have…
> 1 year
Easy Positive United States
I applied through their website and then got pulled into a fairly straightforward coding assessment. It was five questions on a coding platform, with …
> 1 year
Average Negative United Kingdom
After I completed the coding stage, I ran into HR screening issues that colored the whole experience. I was contacted to schedule, and when the HR cal…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Online Assessment (OA)
Candidates typically start with an online coding assessment that includes multiple LeetCode-style questions, often with a high passing threshold. The assessment can feel fast-paced and may include hidden test cases that complicate understanding of performance.
LeetCodeHigh thresholdHidden test cases
Technical Interviews
Subsequent technical interviews often blend coding questions with low-level systems discussions, including topics like memory management and algorithm efficiency. Candidates report a mix of straightforward problem-solving and more adversarial questioning styles that can feel rushed.
DSALow-level systemsAdversarial questioning
Behavioral and HR Rounds
The HR interviews tend to focus on resume discussions and behavioral questions, but candidates often find these sessions unhelpful or dismissive, leading to a frustrating experience. Poor communication and scheduling issues are common complaints.
BehavioralHR issuesPoor communication
Interview Structure and Flow
The interview process is structured but can feel chaotic, with varying formats and unexpected changes in question types across rounds. Candidates note that the scheduling can be irregular, leading to a sense of disorganization.
Interviews often emphasize the demanding nature of the work environment, with multiple candidates noting discussions about long hours and high expectations. This focus on cultural fit can overshadow technical evaluations.
Cultural fitHigh expectationsLong hours
Overall Experience and Feedback
Candidates frequently report a lack of clear feedback throughout the process, leading to uncertainty about their performance. Many express disappointment with the overall experience, particularly regarding the disconnect between assessments and actual job requirements.