Jane Street offers internships in trading, quantitative research, machine learning, software engineering, and strategy and product. This guide covers programme length, current rolling listings, path selection, and the reasoning-based interview process.
Quick Facts: Jane Street internships
| Item | Detail (verify on live posting) |
|---|---|
| Apply | janestreet.com internships hub |
| Trackr US (as of 18 Aug 2026) | Quantitative Trader/Researcher Internship: opened ~28 Dec 2025, close none listed |
| Trackr UK (as of 18 Aug 2026) | Quantitative Trading Intern Summer 2027: opened ~3 Aug 2026, rolling |
| Duration | 10–12 weeks, typically May to September |
| Hubs | New York, London, Hong Kong |
| Paths | Trading, quantitative research, machine learning, software engineering |
Jane Street does not run one global deadline. The current Trackr rows above support a rolling London listing and a New York listing with no close shown. Treat Trackr as a timing guide and confirm the status of each live requisition before planning your application cycle.
Jane Street is a proprietary trading firm and liquidity provider, not an investment bank. Its internships are built for students who enjoy solving unfamiliar problems collaboratively, including applicants without a finance background. According to Jane Street's programme page, its 2025 summer class included students from more than 103 colleges and universities across 24+ countries. That figure describes the 2025 cohort, not 2027 hiring.
The interview process reflects the work. Jane Street's public interview materials use trading games to illustrate reasoning under changing information, while engineering preparation should include coding and systems questions relevant to the role. Pick the path your CV can support, then practise explaining your reasoning clearly enough for an interviewer to follow and challenge it.
What Jane Street internships actually are
Jane Street calls its approach "learning by doing": short classes and discussions, then straight into real problems alongside a mentor. A striking number of full-time traders and researchers did not study finance at all. The firm is explicit that it hires for curiosity and collaborative problem-solving first, then teaches markets context once you are inside the building.
That plays out differently depending on the path you pick. Trading interns sit closest to live decision-making under uncertainty, where the job is calm, fast judgement rather than a polished pitch. Quantitative research leans on structured reasoning and coding, building and testing models with a research team rather than working alone.
Machine learning interns move between problems on opposite ends of the clock, from sub-microsecond trading systems to longer-horizon inefficiencies, and need markets curiosity alongside genuine ML depth. Software engineers build the in-house systems that make all of that possible, with a production mindset and enough comfort with the firm's engineering culture, including its heavy use of OCaml, to debug under real constraints. Strategy and product roles sit further out, working cross-team commercial problems that still demand the same rigour as everything else.
Summer programmes typically run 10 to 12 weeks between May and September, with off-cycle options for students on non-standard academic calendars. The core internship hubs are New York, London, and Hong Kong. A typical week blends project work with your mentor, classes on topics like performance-sensitive code, heuristics and biases, and even poker as a decision-making framework, plus team events. The format suits students who enjoy working through difficult problems with other people.
These roles are not client M&A or general investment banking internships. Make sure the evidence on your CV and any application answers connect to the trading, research, engineering, or product path you selected.
Applying to the right path and hub
Start at the internships hub and go straight to the path page that matches your background, for example trading if that is your target. Pick one primary path and make the relevant evidence easy to find. A second path can make sense when your experience supports a distinct application and interview narrative for it. Follow the live form and do not assume every role includes an essay.
Filter by office and confirm your eligibility, including graduation year and work authorisation, before you go further. Your CV should show outcomes rather than adjectives: contest maths results, coding projects with real metrics attached, a research write-up, or a markets project built around a specific question you tried to answer. Once your materials are genuinely ready, save the job ID and block out interview prep time before you click submit, not after.
For CV formatting, our finance CV template ATS guide covers the basics. If you are running Jane Street alongside bank deadlines, the finance internship deadlines rolling guide helps you sequence both without dropping a ball.
Jane Street does not publish one global deadline. The current Trackr rows show London quantitative trading as rolling and New York quantitative trader/researcher with no listed close, but that does not establish the same policy for every internship. Check each live requisition and submit reasonably soon once your materials are ready.
London and Hong Kong applicants should double-check local eligibility requirements rather than assuming the US timeline applies. Keep other live applications moving as well. Starting probability or coding practice early gives you time to build fluency without relying on a rushed final week.
What to expect from the interviews
Jane Street's public interview materials emphasise interactive problem-solving, but exact stages vary by path and office. Pick your question bank from the live job title, not the firm logo:
| Path | Interview centre | Not this |
|---|---|---|
| Trading | Probability, estimation, calm updates | IB deal walk-through |
| Quant research | Models, stats intuition, coding where listed | Generic "markets passion" |
| Software engineering | Coding, systems, failure modes | LBO mechanics |
| ML | ML depth plus markets curiosity | Hand-wavy AI buzzwords |
| Strategy / product | Structured commercial reasoning | Forced trading brain teasers |
Trading preparation commonly includes probability, mental arithmetic, and estimation. Engineering preparation should include coding and systems reasoning. In either case, explain the structure of your approach rather than giving an unsupported answer.
How to answer trading questions aloud
Use a fixed habit on probability and estimation prompts:
- Restate the question in one sentence
- State assumptions before calculating
- Compute in small steps the interviewer can interrupt
- Sanity-check the magnitude
- Invite pushback ("If the fee were higher, I would…")
Interviewers often change a parameter mid-question. Name what changed, update your calculation, and explain the revision calmly. Silent correct answers help less than visible thinking.
| Practice shape | What it trains |
|---|---|
| Expected value | Fair game with a fee; should you play? |
| Conditional probability | Draw without replacement; update odds after one reveal |
| Estimation | Fermi-style prompt; state assumptions first |
| Rule change | Same game, new payout; how does your decision flip? |
Work each shape aloud twice. First take finds structure. Second take finds cleaner speech. Fifteen minutes of probability plus five minutes talking through a made-up problem beats an hour of silent puzzle grinding.
Follow-ups that trip candidates
| Interviewer move | Strong response |
|---|---|
| Changes a number mid-question | Name the change, update calculation |
| Asks "are you sure?" | Re-check largest assumption first |
| Gives a faster method hint | Adopt hint, explain why it works |
| Pushes on edge case | State boundary condition plainly |
Later technical conversations may add constraints or ask you to revisit an assumption. Treat that as part of the discussion: state what changed, update your approach, and explain the correction calmly.
Many questions are open-ended and allow more than one reasonable approach. Thinking aloud helps the interviewer follow your assumptions and gives you room to correct an error. Clear reasoning and a sensible revision are more useful than trying to make every answer look effortless.
Phone screen versus on-site
Early conversations often stay narrow: one probability thread or one coding problem with follow-ups. Later rounds add interaction depth and sometimes collaboration with another candidate.
| Stage | Usually tests | Prep shift |
|---|---|---|
| First screen | One core skill for the path | Daily short practice |
| Mid rounds | Harder variants, faster pushback | Mock with interruptions |
| Final | Fit plus hardest technical mix | Rest voice; review one project story |
Update your tracker stage when the format changes so you are not practising hour-long superday packs for a twenty-minute phone screen.
That is why the single highest-leverage habit, months before any interview invite, is daily probability and mental arithmetic practice: expected value, conditional probability, a little Bayes intuition. Pair that with deliberately thinking aloud for five to ten minutes on made-up problems, because the interview format rewards visible reasoning far more than silent correctness.
Build one markets or research example you can explain in ninety seconds, including the specific evidence that would change your view. If engineering is your path, prepare a project walkthrough that covers latency, correctness, likely failure modes, and technical trade-offs. Jane Street is known for using OCaml, but prepare around the requirements of the live role rather than assuming one language defines the whole interview.
Record timed takes in Finbound's Video Interview Prep for fit questions and pacing, not as a substitute for live math with an interviewer.
Investment banking valuation practice, useful as it is for Goldman or Evercore, simply does not transfer here. If you are running both processes, keep two separate story banks and split prep blocks on the calendar; our hedge fund vs investment banking career guide breaks down why the motivation language does not travel between the two worlds.
How Jane Street compares to the other quant shops
Jane Street's public materials place unusual emphasis on probabilistic decision-making, collaborative problems, mental maths, and coding by path. Its closest peers publish different role descriptions and interview guidance, so separate your preparation according to the live listing.
| Firm | Public application and preparation focus |
|---|---|
| Jane Street | Path pages emphasise probabilistic decision-making, collaborative problems, mental maths, and coding by role |
| D.E. Shaw | Research, trading, systematic, and systems paths call for different preparation |
| Citadel | Citadel and Citadel Securities use distinct role pages; focus can include investing, quant, engineering, or market structure |
| Renaissance Technologies | Sparse Rentec listings provide limited process detail; prepare around the live research or engineering role |
Track each of these separately rather than combining them into one general quant study block. Use the role description and the firm's public interview guidance to decide what to study each week.
A practical run-up to the application
Start by matching your CV and any required application answers to the chosen path. Trading, research, and engineering roles call for different evidence, so identify the strongest relevant project, result, or experience for each application. If the form does not request an essay, focus on accurate materials rather than creating one.
Use janestreet.com and the live requisition for pay, timing, and eligibility details. Forum posts can provide personal experiences, but they may describe another year, office, or path. Once your materials are accurate and ready, submit according to the current listing and continue practising while you wait.
A realistic run-up looks like this. Twelve to ten weeks out, decide your path, rebuild your CV, and start daily probability practice. Nine to seven weeks out, move to harder puzzles and prepare one project or markets talk you can defend under pushback.
Six to four weeks out, run timed mock interviews, adding coding depth if you are targeting engineering. Three to two weeks out, turn on hub alerts and sharpen your "why Jane Street, why this path" answer. In the final week, proofread everything, submit in the first wave once your listing opens, and keep practising right up to the interview.
What to do after reading this
Applying to Jane Street this cycle? Pick one path, trading, quant, ML, or engineering, and commit your CV and story to it before you touch the online form. Start daily probability practice now, well before an invite lands, and confirm every date and pay figure on janestreet.com rather than a forum thread.
Compare with our Susquehanna internship guide and Jump Trading internship guide.
