Interview Experiences

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

Share yours, earn XP

21 stories

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

Jane StreetQuantitative Analyst
Reported Jul 2026

Jane Street Quantitative Analyst interview: probability games before superday

I had several Zoom interviews, with three technical rounds before a superday. The questions were built around games presented by the interviewers and relied heavily on probability and game thinking. The early games were more straightforward and closer to deterministic setups. Later rounds brought more randomness and more game theory. In the more open-ended game rounds, I needed to optimize outcom…

RejectedTechnical Screen0
Jane StreetQuantitative Analyst
Reported Jul 2026

Jane Street Quantitative Analyst interview: probability rounds and nerves

After applying online, I had a resume screen and a first technical round. It was my first quant interview, and I was nervous enough that I did not answer as smoothly as I wanted. I did not move past that round. I later entered through a program that sent me directly to interviews. There were two 45-minute Zoom technical rounds. The first was clearly easier than the second, and the interviewers we…

Technical Screen0
Jane StreetSoftware Engineer
Reported Jul 2026

Jane Street Software Engineer interview: final onsite mattered most

I started with a virtual round and then moved to an onsite. The questions blended coding with system-design-style work, but they emphasized real-world systems more than academic exercises. By the onsite, it was clear that this was the most important stage and that the bar was highest there. I did not perform well enough in that final stage to move forward. The process was intense, and my main tak…

Onsite0
Jane StreetSoftware Engineer
Jun 2026

Rejected After a Bracket-Collapsing Code Editor Screen

A premium story — unlock it to read the full loop.

RejectedTechnical ScreenPremium0
Jane StreetQuantitative Analyst
Reported Jun 2026

Jane Street Quantitative Analyst interview experience: probability progression

I went through math-focused interviews that started with easier questions and became harder. The rounds centered on probability. Early questions established the fundamentals, then the difficulty increased. Each round also began with a behavioral check-in, which set expectations before the technical work. In a similar run, I had three phone interviews along the same probability track. The first co…

0
Jane StreetSoftware Engineer
Feb 2026

Two Onsite Rounds and a Coding Trap

Locked — open it to unlock the full story with XP.

RejectedOnsiteXP0
Jane StreetSoftware EngineerNew Grad
Feb 2026

A Stream-Transformer Coding Question from the Phone Screen

This is an old one — sharing a question from my campus recruiting interview back in the day. Given a set of M codes and N timestamps, the ideal shape for the data is an N x M matrix, where the rows are sorted by time and the columns are sorted by the code's lexicographic order. But not every code has data at every timestamp. You're given a stream of std::vector<std::tuple<int, std::string, int>>,…

Technical Screen0
Jane StreetMachine Learning Engineer
Dec 2025

Passed the Coding Screen, Failed the ML System Round

A premium story — unlock it to read the full loop.

RejectedTechnical ScreenPremium0
Jane StreetSoftware Engineer
Dec 2025

Onsite System Design on Orderbooks, Rejected Before the Coding Round

Real-time report from the London office. The OA and first-round phone interview are already covered elsewhere on the forum, so this is just filling in the details on R2 and the onsite. R2: a coding interview (sort trade) — this one's also up on Glassdoor. Compared to a typical algorithm question, the setup was closer to "how would you implement this feature in a trading system," testing your logi…

RejectedOnsite0
Jane StreetQuantitative TradingIntern
Dec 2025

Three Phone Rounds, All Game Theory

I'll share my experience with the three phone-interview rounds for a quant trading internship at Jane Street's NYC office. Jane Street likes to test with games — no math brainteasers, no algorithms, none of that standard stuff. You don't need to answer fast either; taking a minute or two to think or calculate before giving an answer is completely fine. Round 1: two questions, both original questi…

Technical Screen0
Jane StreetQuantitative ResearcherIntern
Nov 2025

A Custom Board-Game Coding Puzzle Instead of LeetCode

A premium story — unlock it to read the full loop.

In progressTechnical ScreenPremium0
Jane StreetSales and Trading
Oct 2025

Excel Take-home Then a Challenging Phone Screen

Locked — open it to unlock the full story with XP.

Technical ScreenXP0
Jane StreetFullstack/Frontend Engineer
Sep 2025

Passed the Calculator Screen, Failed the Backend Algo Round

A premium story — unlock it to read the full loop.

RejectedTechnical ScreenPremium0
Jane StreetQuantitative TraderIntern
Sep 2025

A Coin-Flipping Magic Wand and a Rainy Weekend

A premium story — unlock it to read the full loop.

Technical ScreenPremium0
Jane StreetSoftware Engineer
Sep 2025

Maximizing Reward as Pixels Reveal One Row at a Time

The interview was about solving an actual problem. The setup was an image classification problem using the FashionMNIST dataset. The model (a plain CNN) and the training code were already written, and the task was to modify it question by question from there; the environment they gave me was a Jupyter notebook (.ipynb). There were mainly two parts. After understanding the code (there wasn't much…

Technical Screen0
Jane StreetSoftware Engineer
Sep 2025

OA Then a Phone Screen With Palindrome and Dice-Game Brain Teasers

I submitted my resume and got the OA email the next day. The problem was one that's already floating around the forum: using Excel to calculate a haircut, plus general Excel formula usage. Same numbers as the version posted on the forum, nothing changed. My suggestion if you're filling in the spreadsheet and need to use data from the problem's own table: use a reference, not copy-paste. The probl…

Technical Screen0
Jane StreetML Perf EngineerNew Grad
Aug 2025

A Two-Part Marketplace API Coding Question

A premium story — unlock it to read the full loop.

In progressTechnical ScreenPremium0
Jane StreetData ScientistIntern
Jul 2025

A Coin-Flip Probability Puzzle and a Cyclic Game-Theory Question

A premium story — unlock it to read the full loop.

Technical ScreenPremium0
Jane StreetData Scientist
Feb 2025

One Box-Pricing Question That Kept Adding Twists

A premium story — unlock it to read the full loop.

Technical ScreenPremium0
Jane StreetQuantitative Research InternIntern
Oct 2022

Answered Every Question, Still Rejected

A premium story — unlock it to read the full loop.

RejectedTechnical ScreenPremium0

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