Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

4 stories

Likes earn the author +10 XP for the first 3 likes each day

Virtu FinancialFull Stack Engineer
Reported Jul 2026

Virtu Financial Full Stack Engineer interview: expected C++ and a JavaScript task

A recruiter contacted me about the role and my background. I appreciated how they handled my frequent job changes caused by layoffs. They described the process as "language agnostic" and said the first round would be DSA in C++. I scheduled the interviews quickly and concentrated on preparing in C++. When the interview began, the engineer asked me to solve a combined DSA and low-level design prob…

Technical Screen0
Virtu FinancialQuantitative Analyst
Reported Jul 2026

Virtu Financial Quantitative Analyst interview experience

The process started with an online assessment that I was told only a small fraction of applicants passed. After I got through it, a recruiter call felt encouraging. The technical screen was unsettling. The interviewer introduced herself, asked me to introduce myself and explain why I wanted the firm, then moved to my research experience. She seemed repeatedly confused about its basis and kept ask…

Online Assessment0
Virtu FinancialQuantitative Analyst
Reported Jul 2026

Virtu Financial Quantitative Analyst Interview Experience: Probability coding before HR

After applying, I started with a HackerRank-style coding round. It combined basic probability with straightforward coding questions, and it felt manageable if I was comfortable with standard programming and probability fundamentals. An HR conversation followed, and that was where my process ended. I felt I had cleared the technical part cleanly, so being screened out after the recruiter call was…

RejectedOnline Assessment0
Virtu FinancialQuantitative Researcher
Jan 2026

Basketball Shot Prediction Design and a Connect Four Round

Timeline: mass-applied -> OA -> HR screen -> Round 1 -> Round 2 The HR round just went over my resume, timeline, and identity/status information. None of the brain teasers people mentioned in earlier interview experience posts. Round 1 was an open-ended ML system design. The question: after a basketball is thrown, it can either go in or miss — how do you model this using information available at…

Technical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP