Jane Street Software Engineer Interview Guide

Dan Lee's profile image
Dan LeeData & AI Lead
Last update
Jane Street Software Engineer Interview Guide

The short answer: Jane Street's software engineer interview is coding from start to finish. Its prep page and 2020 blog post describe a remote technical interview, then a final round of 2 to 4 coding interviews, now held in person at an office. Jane Street says the rounds include no mental math, logic puzzles or probability questions, and writing OCaml earns no bonus. Each round is one open-ended problem that grows in parts, and interviewers care more about how you work through it than whether you finish. Last reviewed October 2026.

Jane Street Software Engineer at a Glance

Base Salary (US postings)

$300k - $300k/yr

Interview Rounds

4 to 6 rounds

Levels

New grad - Software Engineer

OCaml Python C C++ TypeScriptTrading systemsOCamlLow-latency tradingCompilers and programming languagesFront-end trading tools

Jane Street software engineer interview: quick answers

QuestionShort answer
How many interview rounds?Jane Street's 2020 blog post describes one technical phone interview, then an on-site with 2 to 4 technical rounds, each with 1 or 2 engineers. Candidate reports add a short recruiter call first and a project discussion for experienced hires.
What do the rounds test?Coding problems. Jane Street says you collaborate on a series of programming problems, and interviewers ask themselves whether you are someone they want to work with. How you reach the answer counts more than the final code.
Are there math or puzzle questions?No. Jane Street says software engineer interviews have no mental math, math olympiad problems, logic puzzles or probability questions. Those belong to its trading interviews.
Can I use AI tools?Jane Street does not publish a rule on AI use in interviews; ask your recruiter.
Which language should I use?The one you know best, written as real code. Jane Street gives no extra credit for OCaml or other functional languages and says not to use OCaml unless it is your strongest language.
How long does it take?Jane Street aims to reply within about a week after each step. Candidate reports put the whole process at about 3 to 4 weeks, with team matching after the on-site.

The Jane Street software engineer role

What Jane Street engineers work on, the skills its job postings ask for, and what a normal week looks like.

Primary Focus

Trading systemsOCamlLow-latency tradingCompilers and programming languagesFront-end trading tools

What You Need

  • Designing and building systems that run the firm, from trading desk code to core infrastructure
  • Working with traders to specify features and build tools (desk developers)
  • Planning team work over weeks and years
  • Supporting your own tools when they break in production
  • Reading and reviewing colleagues' code
  • Python for data analysis, visualization and machine learning work

Nice to Have

  • C and C++ for small parts of low-latency work
  • Kernel-bypass and fast-packet tools such as OpenOnload, TCPDirect, ef_vi and DPDK (low-latency roles)
  • TypeScript, Elm, ReasonML or PureScript (front-end roles)
  • A high bar for user experience when building tools for expert users (front-end roles)

Languages

OCamlPythonCC++TypeScript

Tools & Technologies

IronDuneBonsaiHardcamlMemtracemagic-traceOxCamlMercurialDPDK

Want to ace the interview?

Practice with real questions.

Start Mock Interview

A Week in the Life of a Jane Street Software Engineer

Illustrative mid-level week · Jane Street

An illustrative week for a mid-level engineer, built from practices Jane Street describes in its own publications and job postings. Real weeks vary a lot by team.

Culture notes

  • Every change is read in full by at least one other person, so reviewing code is a large part of the job.
  • Desk developers sit next to the traders who use their tools and often see a tool used the day it ships.
  • Team boundaries are porous, and new engineers learn OCaml and markets on the job.

Key takeaway: Expect a week split between reading and reviewing code, building tools with the people who use them, and supporting those tools.

Jane Street software engineer levels and pay

Your level sets the bar you are interviewed against and the pay band of the offer.

Jane Street Software Engineer Levels

Each level has different expectations, compensation, and interview focus.

What This Level Looks Like

Joins through the new grad program and starts with an OCaml bootcamp before real projects.

Interview Focus at This Level

The same coding interviews as everyone else: open-ended problems in your strongest language.

Find your level

Practice with questions tailored to your target level.

Start Practicing

Jane Street does not publish an engineering ladder. It posts one Software Engineer title for new grads and experienced hires at the same New York base, and staff describe a flat hierarchy. Candidate guides use level labels such as L1, which Jane Street itself does not use, so the table below uses posting titles.

Pay in Jane Street's US job postings

Most of Jane Street's New York engineering postings print a single fixed base of $300,000, not a range. Each says total pay also includes an annual discretionary bonus. No equity is mentioned.

The new grad and experienced Software Engineer postings print the same base, and none of the postings state a level. Production, Linux, data and hardware engineering postings are left out because they sit outside the general software engineer track. Ranges seen October 27, 2026.

Jane Street software engineer interview process

Jane Street's prep page, interviewing page and blog posts from 2014, 2017 and 2020 describe the coding interviews. The recruiter call, round lengths and the project discussion come from candidate reports.

4 to 6 rounds·~3 to 4 weeks end to end

Screen

2 rounds
1

Recruiter call

30mPhone call

Background, motivation and logistics. The 2020 blog post says experienced candidates may also have a non-technical phone interview.

generalbehavioral

Tips for this round

  • Have a short answer on why Jane Street and what kind of team you want.
  • Ask how many final-round interviews to expect and whether a project discussion is included.

Onsite

2 rounds
3

Final round: coding interviews

75mIn person, 1 or 2 engineers per round

Jane Street says the final round is mostly, if not only, collaborating on a series of coding problems. The 2020 post gives 2 to 4 technical rounds with 1 or 2 engineers in each. Candidate reports say each round extends one solution as new requirements arrive.

coding

Tips for this round

  • Expect one problem to grow, so keep your first version easy to extend.
  • Ask clarifying questions and test your code out loud.
  • Take hints as a colleague would and keep explaining your thinking.

Tips to Stand Out

  • Jane Street says interviewers ask themselves whether you are someone they want to work with, so treat the round as working with a colleague.
  • Write real code, not pseudocode, in the language you know best, and know its standard library and basic data structures.
  • Say "I don't know" instead of guessing, and say so if you spot a fatal flaw in your own approach (2014 blog post).
  • Stick to the plan you agreed with the interviewer, or explain why you are changing it (2014 blog post).
  • Tell the interviewer if you have seen the question before so they can switch problems (2017 blog post).
  • Practice the way Jane Street suggests: use a timer, talk through ideas aloud and write out every part of the code, even the easy parts.

Common Reasons Candidates Don't Pass

  • ✗Jane Street's 2014 blog post lists weak fluency in the chosen language, abandoning a plan without discussion and gaps in computer science fundamentals.
  • ✗The 2017 post says sloppy or buggy code can lose to a careful candidate who gets less far, and that struggling with the first, basic part suggests more preparation is needed.
  • ✗Candidate guides cite code that is hard to verify as correct, missed edge cases and designs that need rewriting as requirements grow.
  • ✗Candidate reports say poor communication and not asking clarifying questions hurt, since collaboration weighs as much as the code.

Based on Jane Street's own pages and candidate reports.

Jane Street aims to reply within about a week of the final interviews and says it does not make exploding offers, so flag any competing deadline early. Candidate reports describe team matching after the on-site. Last reviewed October 2026.

What is different at Jane Street

  • Coding only, with no math. Jane Street says software engineer interviews skip the mental math, logic puzzles and probability questions used in its trading interviews.
  • One problem that keeps growing. The 2017 blog post gives an example: memoize a function, then bound the cache, then add LRU eviction. Jane Street says it avoids trick questions that need a single insight.
  • OCaml earns nothing extra. Jane Street runs almost everything on OCaml, yet its prep page says there is no bonus for functional languages and to avoid OCaml unless it is your strongest language.
  • Finishing is optional. The 2014 and 2017 blog posts say clear communication and careful, correct code count for more than reaching the last part, and a careful candidate who gets less far can beat a sloppy one who finishes.
  • Jane Street publishes its own practice material: a 34-minute mock interview video with two engineers working a retired question, and a worked question in the 2017 blog post.
  • Fixed pay in postings. Most New York software engineer postings print a single $300,000 base, the same for new grads and experienced hires, plus a discretionary bonus.

Jane Street software engineer interview questions

Coding problems from our bank tagged to Jane Street, then design, fundamentals and behavioral prompts we wrote for this guide.

System design practice

Practice prompts we wrote around Jane Street's products. They are not reported interview questions. Each answer is an outline of what a strong answer covers.

Design a code review and release system where every change must be read in full by at least one other engineer before it ships.

MediumSystem design

Sample Answer

Jane Street says its software engineer rounds are coding, so use this to prepare for a project discussion and for extending a design under new requirements. Clarify the unit of review (a feature branch or single change), who must approve, and how releases are cut. Model each feature as a set of diffs with a required-reviewer list, track which lines each reviewer has read, and block release until every line has been read. Discuss how to handle rebases without forcing a full re-read, and how to show a reviewer only what changed since they last looked. A strong answer covers large changes that span many owners and avoids letting one approval stand in for reading the code.

Practice more system design questions

Fundamentals practice

Concept questions on the topics Jane Street's rounds lean on, with short model answers. We wrote these for practice.

How would you add a size bound to a memoized function, and what eviction policy would you pick?

MediumFundamentals

Sample Answer

Wrap the function with a hash map from arguments to results. To bound it, evict an entry when the map is full. Least-recently-used eviction keeps a doubly linked list in access order next to the map, so lookups, inserts and evictions are all O(1). This is the kind of growing problem Jane Street's 2017 blog post describes.

Review the fundamentals course

Behavioral practice

Practice prompts we wrote for the behavioral rounds. They are not reported interview questions.

Tell me about a time you said "I don't know" in front of colleagues. What happened next?

MediumBehavioral

Sample Answer

Jane Street's 2014 blog post asks candidates to admit what they do not know instead of guessing. Show how you found the answer and what the team gained from your honesty.

Practice more behavioral questions

Practice problem: first-in, first-out position and profit tracker

python

You get a list of fills as (symbol, qty, price) tuples in time order. A positive qty is a buy and a negative qty is a sell; prices are whole cents. Match fills against open lots first in, first out: a sell closes the oldest long lots first, and a buy closes the oldest short lots first. Closing a long lot earns (sell price - lot price) per share, and closing a short lot earns (lot price - buy price) per share. If a fill is larger than the open position, the rest opens a new lot in the other direction. Return a dict from each symbol to (net position, realized profit). Example: [('ABC', 10, 100), ('ABC', 5, 110), ('ABC', -12, 120)] returns {'ABC': (3, 220)}: 10 shares at 100 earn 200 and 2 shares at 110 earn 20.

Python
1from typing import Dict, List, Tuple
2
3def track(fills: List[Tuple[str, int, int]]) -> Dict[str, Tuple[int, int]]:
4    """Return {symbol: (net position, realized profit in cents)} using FIFO lot matching."""
5    pass

700+ coding problems with a live code executor.

Practice in the Engine

How to prepare

A plan for the Jane Street loop, most important first:

  1. Practice open-ended problems that grow in parts: solve a first version, then add a new requirement and extend your code without starting over.
  2. Pick the language you know best and drill its standard library and basic data structures, since Jane Street asks for real code and gives no credit for OCaml.
  3. Watch Jane Street's mock interview video and work the retired question from its 2017 blog post under a timer.
  4. Practice talking through every step aloud, agreeing on a plan before you type and saying clearly when you do not know something.
  5. Check your code by hand on small inputs and edge cases, since careful, correct code beats getting further with bugs.
  6. If you have several years of experience, prepare one project you can discuss in depth, and ask your recruiter whether AI tools are allowed in any round.

Practice path

Courses that cover the rounds above:

Are you ready for the Jane Street software engineer interview?

1 / 7
Coding

Can you solve a medium problem (graphs, intervals, heaps or sliding window) in about 25 minutes while explaining your approach?

Frequently Asked Questions

How many rounds is the Jane Street software engineer interview?

Jane Street's 2020 blog post describes one technical phone interview and then an on-site with 2 to 4 technical rounds. Its current prep page says the final round is in person at an office. Candidate reports add a recruiter call at the start and a project discussion for experienced hires.

Do I need to know OCaml for a Jane Street interview?

No. Jane Street says there are no bonus points for OCaml or other functional languages, and asks you not to use OCaml unless it is your strongest language. New developers learn it in an OCaml bootcamp after they join.

Does the Jane Street software engineer interview include math or brainteasers?

No. Jane Street says its software engineer interviews have no mental math, math olympiad problems, logic puzzles or probability questions. Expect open-ended coding problems that grow during the interview.

Can I use AI in a Jane Street interview?

Jane Street does not publish a rule on AI use in interviews; ask your recruiter.

How much do Jane Street software engineers make?

Jane Street's New York postings for Software Engineer, including the new grad posting, print a fixed $300,000 base. Some specialist roles post $250,000 to $300,000. Total pay adds an annual discretionary bonus, and no equity is mentioned.

What are the software engineer levels at Jane Street?

Jane Street does not publish levels. New grads and experienced hires apply to the same Software Engineer title at the same posted base, and staff describe a flat hierarchy.

Can I reapply to Jane Street after a rejection?

Jane Street asks students to wait at least a year before reapplying. Experienced candidates should wait until their experience has changed significantly.

Dan Lee's profile image

Written by

Dan Lee

Data & AI Lead

Dan is a seasoned data scientist and ML coach with 10+ years of experience at Google, PayPal, and startups. He has helped candidates land top-paying roles and offers personalized guidance to accelerate your data career.

Connect on LinkedIn