Jane Street Interview Questions and Process

Jane Street interviews test collaborative problem solving by role rather than prior finance knowledge or OCaml syntax. According to Jane Street's interviewing pages, Quantitative Trading candidates start with phone interviews and finish with in-person rounds on probability, expected value, and market making, while general Software Engineering candidates complete 1 technical phone screen and 2 to 4 on-site coding rounds with zero math or logic puzzles. Every application is reviewed by a human on a rolling basis, considered across all open roles globally, and answered within about a week.

Updated

How the Jane Street interview process works by role

Cover letters are not required when applying to Jane Street, and applications are reviewed on a rolling basis with no standard deadline. If your background fits another team better than the role you selected, recruiters tell you up front and route you to the right track. You can practice a case free, no sign-up before your first screen to get comfortable thinking out loud under time pressure.

Because each department solves different problems, the stages and question types split by discipline. Quantitative Research overlaps trading and engineering, so its process mixes both tracks. Machine Learning candidates collaborate on realistic modeling problems on market-scale data, and Trading Desk Operations Engineering candidates are evaluated on technical, organizational, and communication skills.

Interviews run Monday through Friday during local business hours, never on weekends. For in-person final rounds in offices such as New York, London, or Hong Kong, Jane Street books and pays for flights and hotels. New York job postings for Software Engineers and recent-graduate Quantitative Traders list a $300,000 base salary plus an annual discretionary bonus, as posted on Jane Street's careers site and reported by Business Insider in May 2026.

Jane Street interview stages and topics by department (Source: Jane Street Interviewing guides, 2026)

Jane Street interview stages and topics by department (Source: Jane Street Interviewing guides, 2026)
DisciplineInitial StagesFinal RoundCore Topics TestedWhat Is Not Required
Quantitative TradingPhone interviews with quantitative tradersIn-person interviews at a Jane Street officeProblem solving, probability, expected value, making markets, adverse selection, coding in any language, data analysisFinance or economics knowledge, advanced college math theorems, 5-second double-digit mental math
Quantitative ResearchMix of Trading and Software Engineering phone interviewsIn-person mix of trading and engineering roundsProbability, expected value, market making, coding, and algorithmsPrior finance background or OCaml experience
Software Engineering1 technical phone or Zoom interview on CoderPad (plus HackerRank first for some London applicants, optional non-technical call for experienced hires)On-site or video round with 2 to 4 technical coding interviewsOpen-ended coding and algorithms in your best real programming language, CS 101 data structures, big O, cache and memory effectsMental math, math olympiad questions, logic puzzles, OCaml, finance, master's or PhD degree
Strategy and ProductOnline assessment and video interviewsA day of in-office qualitative and technical exercisesHypothetical business scenarios, logic puzzles, technical system information flow, updating solutions with new dataPrior finance knowledge, coding syntax, specific major, memorized frameworks
Machine LearningTechnical screeningFinal rounds with ML researchers and engineersCollaborative work on realistic modeling problemsPrior finance knowledge

Quantitative Trading and Research interview questions

Full-time quantitative traders conduct every Quantitative Trading interview, starting with phone screens and finishing with in-person rounds. Jane Street states on its trading interviews page that sessions feel like a conversation rather than a quiz. Getting a wrong answer does not automatically fail you because interviewers test how you take hints and correct mistakes. Both Jane Street's prep guide and Business Insider's May 2026 report note that rapid mental math is not a deciding bar, and candidates are not judged harshly for not multiplying double-digit numbers mentally in 5 seconds.

In its official 12-page Probability and Markets PDF, Jane Street outlines the exact concepts and practice questions to review before interviewing:

  • Counting and independence: Calculating outcomes on six-sided dice (d6) and cards. Prompts ask for the probability of rolling a sum of 7 on two distinct d6s (6/36 = 1/6), a sum of 10 on two d6s, drawing 2 face cards with replacement, drawing 2 clubs without replacement, and getting an odd product on 2 or 3 rolls of a d6.
  • Expected value and linearity: Applying E(X + Y) = E(X) + E(Y) (which holds even when X and Y are dependent and ties to the Law of large numbers) and indicator functions where E(1_A) = P(A). Prompts ask for the expected value of a d6 reweighted so 6 occurs half the time, a d6 with the 6 replaced by 12, and two variables where E(X*Y) does not equal E(X)*E(Y).
  • Conditional probability and updating priors: Using P(A given B) = P(A and B) / P(B). Worked examples find the expected value of a d6 given at least 4 (which leaves 4, 5, and 6 at 1/3 each, averaging 5) and the probability of 2 heads on 3 coins given at least 1 tail (3/7). Prompts ask for the expected value and probability of rolling at most 3 on a d6 given a prime roll.
  • Recursion on memoryless games: Conditioning on the first step. Flipping a fair coin until heads takes E(flips) = 1 + (1/2)(0) + (1/2)E(flips), solving to 2 flips (or 1/p for probability p). The guide then asks how many flips are needed to see 3 heads in a row.
  • Confidence intervals and calibration: Giving a continuous range capturing a set share of outcomes, such as a 90% or 95% confidence interval, without being overconfident and making the range too narrow. The guide suggests testing 95% intervals on verifiable facts such as the number of taxis in New York City to check how often your range holds the true number.
  • Making markets and adverse selection: Quoting a bid, offer, and size. To buy 10 widgets at $2 and sell 10 at $4, say 'I'm 2 at 4, 10 up.' A counterparty hits your bid with 'sold,' lifts your offer with 'take 'em,' trades partial size with 'I buy 5' or 'I sell 5,' and you cancel with 'I'm out.' Practice contracts include a 20-sided die (d20), the maximum of 3 d6 rolls, a d6 with one optional reroll, the temperature in an hour, and 1,000,000 times a d6 roll.

Worked solutions to Jane Street's official probability and market-making problems

Jane Street's Probability and Markets guide leaves its practice prompts open for candidates to work through. Below are our team's step-by-step worked solutions to five of those official prompts. You can also practice quick arithmetic in our case math drills and test estimation bounds in our market sizing builder.

1. Sum of 10 on two d6s, and odd product on 2 or 3 rolls: With a red die and a blue die, there are 6 times 6 = 36 equally likely outcomes. The pairs summing to 10 are (4, 6), (5, 5), and (6, 4). Because (5, 5) cannot be flipped by color, there are 3 outcomes out of 36, so P(sum is 10) = 3/36 = 1/12. For a product of rolls to be odd, every roll must be odd (1, 3, or 5, which is 3/6 = 1/2 per die). By independence, the probability is (1/2) times (1/2) = 1/4 on 2 rolls and (1/2) cubed = 1/8 on 3 rolls.

2. Reweighted d6 and modified d6 expected value: Assuming a d6 is reweighted so 6 occurs with probability 1/2 and faces 1 through 5 remain equally likely sharing the other 1/2 (1/10 each), the expected value is (1 + 2 + 3 + 4 + 5) times (1/10) + 6 times (1/2) = 1.5 + 3 = 4.5. If a fair d6 instead has its 6 face replaced by 12, each face keeps probability 1/6, giving (1 + 2 + 3 + 4 + 5 + 12) / 6 = 27/6 = 4.5.

3. Conditional expected value and probability given a prime d6 roll: On a d6, the prime numbers are 2, 3, and 5 (1 is not prime). Conditioning on a prime roll restricts the sample space to {2, 3, 5} at 1/3 probability each. The expected value is (2 + 3 + 5) / 3 = 10/3, or about 3.33, and the probability the roll is at most 3 is 2/3.

4. Expected coin flips to see 3 heads in a row: Solve for 2 heads in a row (E_2) first, using E_1 = 2 flips for 1 head. From 1 head, flip once more: with probability 1/2 you get a second head and stop, and with probability 1/2 you get tails and reset, needing E_2 more flips. That gives E_2 = 2 + 1 + (1/2)E_2, which solves to E_2 = 6. From 2 consecutive heads (taking 6 flips on average), flip once more: with probability 1/2 you land the third head and finish, and with probability 1/2 you land tails and restart, needing E_3 more flips. Thus E_3 = 6 + 1 + (1/2)E_3, solving to 14 flips.

5. Making markets on an optional-reroll d6 and on 1,000,000 times a d6: If the contract holder decides whether to reroll once, they keep 4, 5, or 6 (averaging 5, probability 1/2) because those beat a fresh roll's 3.5 average, and reroll 1, 2, or 3 (averaging 3.5, probability 1/2). Fair value is (1/2)(5) + (1/2)(3.5) = 4.25, so you quote around 4.25 (such as '4 at 4.5'). On 1,000,000 times a d6, expected value is $3,500,000, but buying at $3,500,000 and rolling a 1 loses $2,500,000. When one bad outcome threatens a large share of capital, widen your spread and drop your bid well below expected value to manage risk.

Software Engineering interview questions and the retired 'Memo' problem

Software Engineering applicants typically complete 1 technical phone interview on CoderPad followed by 2 to 4 on-site or video coding interviews with 1 to 2 full-time engineers per round. Some London applicants complete a HackerRank screen first due to interviewer capacity, and experienced candidates may have an extra non-technical call. You write runnable code in your strongest real language rather than pseudocode, and interviewers actively discourage trying OCaml for the first time in an interview.

On the Jane Street blog in 2017, an engineer shared a retired phone screen question called 'Memo' to show how a three-part coding conversation progresses:

  • Part 1 (Basic memoization): Given an expensive pure function f of type int to int, write a memoized function g of the same type so g(x) = f(x) while computing f(x) at most once per input. Passing candidates quickly code a bug-free solution storing results in a hash table.
  • Part 2 (Bounding memory with FIFO eviction): Calling Part 1 on unbounded distinct inputs leaks memory. You must cap the table size and evict entries in first in, first out (FIFO) order in O(1) time by keeping a separate queue of keys to dequeue and delete when full. Most passing candidates complete Part 2.
  • Part 3 (Upgrading to LRU eviction): To keep hot keys cached, you switch to least recently used (LRU) eviction. Linear timestamp scans take O(n) and a min heap takes O(log n), whereas pointing hash table entries to nodes in a doubly linked list achieves O(1) lookups and O(1) evictions. Strong candidates finish Part 3, though falling short does not mean automatic rejection.
What Software Engineering interviewers evaluate

In a 2014 Jane Street engineering blog guide, the firm explains that each one-hour round simulates working together as colleagues. Problems are open-ended enough that even top candidates rarely finish every extension. Focus on six practical habits rather than obscure textbook tricks like 15-line union-find or exact AVL rotations:

  • Master CS 101 building blocks: Write clean code with binary search, sorting, hashing, breadth-first and depth-first search, hash tables, binary trees, heaps, recursion, exhaustive case analysis, and big O CPU and memory estimates including amortized analysis.
  • Account for real hardware: Consider CPU cache effects, I/O patterns, and memory layouts, especially for systems roles.
  • Execute the plan you agreed on: Once you and your interviewer settle on an approach, write that code instead of silently switching midstream. If you spot a flaw, pause and discuss it out loud first.
  • Know your chosen language cold: Handle loops, functions, classes, arrays, lists, maps, and exceptions fluently without needing constant documentation lookups.
  • State your confidence honestly: Say 'I don't know' rather than guessing, and distinguish between high-confidence claims and tentative assumptions.
  • Avoid showy jargon and be pleasant to work with: Plain explanations beat obscure terms like 'hylomorphism,' and courtesy matters directly in hiring decisions.

Strategy and Product (SP) interview stages and questions

Strategy and Product teams tackle operational, business, and growth initiatives across Jane Street. According to the firm's SP interviewing guide, the process requires no prior finance background, coding syntax, or memorized frameworks, though candidates must grasp how information flows across technical systems.

To practice structuring unfamiliar operational scenarios and updating numbers as constraints change, you can see a real sample report or work through consulting case study examples.

  • Stage 2 (Video interviews): 1 or 2 live video sessions with a full-time SP solving hypothetical business scenarios and logic puzzles together.
  • Stage 3 (Final in-office day): A full day of qualitative and technical exercises evaluating how you ask clarifying questions, test natural extensions, and incorporate new information.
How to prepare and practice out loud

Across every discipline, Jane Street emphasizes clear communication, intellectual humility, and responsiveness to hints. Use our team's six-step checklist built from Jane Street's official guides before your first round:

  • Study your track's official prep material: Work through the 12-page Probability and Markets PDF for Trading and Research, or the 'Memo' post and mock interview videos on Jane Street's site for Software Engineering.
  • Speak your reasoning and quotes out loud: State why you chose an assumption or data structure, practice saying two-way markets ('I'm X at Y, 10 up'), and recalculate expected value conditional on being filled.
  • Test extreme edge cases: Check 0, 1, negative inputs, and infinity, and shrink 100-player games down to 2 or 3 players first to spot patterns.
  • Build and rebuild a complete project (for SWE): Code an entire project in your strongest language without skipping hard sections, get smart peer feedback, tear it down, and write it again.
  • Share competing offer deadlines early: Because Jane Street reviews rolling applications and does not give exploding offers, alert your recruiter early if another firm sets a tight deadline so they can speed up scheduling.
  • Flag familiar questions and keep prompts private: Tell your interviewer immediately if you have seen a question before so they can switch prompts, and never post or share interview questions afterward.

From Jane Street Interviewing Overview and FAQs, Jane Street Trading Interviews, Jane Street Probability and Markets Guide PDF, Jane Street Preparing for a Software Engineering Interview, Jane Street Blog The Jane Street Interview Process 2020 Edition, Jane Street Blog What a Jane Street Software Engineering Interview is Like, Jane Street Blog Interviewing at Jane Street, Jane Street Strategy and Product Interviewing, Jane Street Internships, Jane Street Software Engineer Job Posting New York and Business Insider Report on Jane Street Interviews May 2026.

1 practice question and sample answer

Say your answer out loud first, then read the sample answer.

Practice question

  1. Make a market on a contract that pays out the maximum of three rolls of a standard six-sided die (3d6), where each pip is worth $1. Then explain how you would update your market if the interviewer immediately lifts your offer.

    Sample answer. Example answer written by our team. The applicant is invented. 'First, I want the expected value of the maximum of three six-sided dice. There are 6 cubed, or 216, equally likely outcomes. Rather than counting each maximum directly, the maximum is 6 unless all three dice land on 1 through 5, which happens 5 cubed, or 125, times. So the maximum is 6 in 216 minus 125, or 91 outcomes. By the same complement logic, there are 125 minus 64, or 61 ways for a maximum of 5, 64 minus 27, or 37 ways for 4, 27 minus 8, or 19 ways for 3, 8 minus 1, or 7 ways for 2, and 1 way for 1. Multiplying each value by its count gives 546 plus 305 plus 148 plus 57 plus 14 plus 1, which sums to 1,071 over 216. Since 216 times 5 is 1,080, that simplifies to 5 minus 9/216, or about $4.96. Because the worst-case loss on one roll is under $4, I will quote a tight market around $4.96: I'm 4.80 at 5.10, 10 up. If you say take 'em and lift my 5.10 offer, I know 3d6 has an objective distribution, so once I verify my math, I shift my next quote slightly higher to 4.90 at 5.20 to manage my short inventory.'

    It talks through the math methodically out loud, uses a clean counting shortcut (complement of cumulative cubes) instead of guessing, checks the order of magnitude against 5, uses Jane Street's exact market-making phrasing ('4.80 at 5.10, 10 up'), and addresses adverse selection and inventory when filled. When you are ready to rehearse speaking your math and logic under real-time follow-up questions, practice a case free, no sign-up with Soreno's AI interviewer.

Practice your interview answers out loud

Soreno's AI interviewer asks behavioral and case questions out loud, follows up like a real interviewer, and scores every answer, quoting your own words.

Questions people ask

Do I need a finance background or OCaml experience to interview at Jane Street?

No. Jane Street does not test finance or economics in interviews, and you can code in whichever programming language you know best. The firm discourages using OCaml for the first time in an interview and notes that most hired software engineers start with no OCaml or functional programming background.

Does Jane Street ask math or probability puzzles in Software Engineering interviews?

No. Quantitative Trading, Quantitative Research, and Strategy and Product rounds include probability or logic problems, whereas general Software Engineering interviews test programming and algorithms only.

What are the GPA or degree requirements for Jane Street?

Jane Street has no GPA or degree requirement, and the vast majority of software engineers hired do not hold a master's degree or PhD. Over 70 universities were represented in a recent global internship program, and 10 to 12 week summer internships between May and September drew students from over 103 colleges and over 24 countries in the 2025 summer class.

How long does it take to hear back after a Jane Street interview?

Recruiters typically answer applications within a few days to a week, and you should hear back about interview outcomes within a week whether or not you advance. If you have not heard back after a week, or after 10 days during busy periods, Jane Street recommends following up with your recruiter.

Can I reapply to Jane Street if I am rejected?

Yes, and many current Jane Street employees were hired on their second or third try. The firm suggests waiting about a year if you are a student, or until your professional experience has meaningfully changed if you are an experienced hire.

Keep going