Interview Experiences

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

Share yours, earn XP

10 stories

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

Jane StreetSoftware EngineerIntern
Aug 2026

Exchange Arbitrage and Quote Throughput

It was a low-level-design problem. Core problem: An Exchange Arbitrage System for stocks. Assume there are multiple exchanges, each with a market feed continuously publishing bid and ask prices for different instruments or stocks. Design and implement an arbitrage strategy. The example gave AAPL on exchange A a bid of \$1.00 and an ask of \$1.10, while exchange B had a bid of \$0.90 and an ask of…

Technical Screen0
Jane StreetSoftware EngineerIntern
Aug 2026

Recursive Arithmetic with Invalid Intermediate Results

An algorithms/LeetCode-oriented question. Problem description: Given a string expression, evaluate it and output the arithmetic result. Restrictions and constraints: Only positive integers are supported. Intermediate-state validation: At any stage of the calculation, if a negative number appears (for example, an intermediate result below 0) or a non-integer appears (for example, division that pro…

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 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 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 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 StreetSoftware Engineer
Apr 2022

Tripped Up by a Stack Machine's Int vs String Bug

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