Prepping for the 2027 recruiting cycle? Use code 2027RC for 10% off, valid until July 31st! Oh, and check out our members-only recruitment services.

Logo

Jane Street Interview Process for Software Engineers

What to expect interviewing at Jane Street as a SWE, contributed by a Jane Street Software Engineer that is part of the getcracked.io community.

Jane Street Interview Process for Software Engineers
By Jane Street SWE

The Jane Street Interview (SWE)

Overview

The following article is based on a discussion with a Jane Street SWE who broke into the space after becoming a getcracked.io member. Two of our members have broken into Jane Street after using getcracked.io to skillup.

Expect a short but dense process, with minimal fluff and heavy signal per round.


Interview Process Breakdown

Stage 1: Technical Phone / Video Screen

Format

  • ~45 minutes

  • 1 core problem with follow-ups.

  • Fully technical (no behavioral)

What to Expect

  • One problem that evolves with constraints

  • Heavy emphasis on reasoning out loud

  • Follow-ups that test:

    • Edge cases

    • Generalization

    • Abstraction

Key Insight

Jane Street is less interested in whether you “get it fast” and more in how you navigate ambiguity and iterate.


Stage 2: Onsite (NYC)

Candidates who pass the first round are typically flown onsite.

Structure

  • Office visit

  • 4 technical interviews (45 min each)

  • Lunch

  • Q&A session with engineers


Stage 2.1: Technical Interviews (x4)

Format

  • 4 × 45-minute interviews

  • Similar style to the first round

  • Increasing depth / difficulty

What to Expect

  • Problem-solving sessions (not LeetCode grind, in fact, our member mentioned they haven't seen a single Jane Street problem on Leetcode)

  • Interactive + collaborative

  • Interviewer nudges / hints

Common Themes

  • Recursion / functional-style thinking

  • State machines / simulation problems

  • Clean abstractions over brute force

  • Mathematical reasoning

Important

These are not typical DSA interviews. They’re closer to “thinking exercises with code.”


Stage 2.2: Lunch

Purpose

  • Informal culture check, and a quasi-interview

  • Evaluate communication + personality

What Matters

  • Curiosity

  • Humility

  • Ability to engage naturally


Stage 2.3: Final Q&A (45 min)

Format

  • Conversation with 1–2 engineers

Goal

  • Assess mutual fit

  • Give you insight into the firm

Tip

  • Ask thoughtful, non-generic questions

  • Show genuine interest in how they think and work


Interns

The process is the same, except there are 3 rounds instead of 4 during the onsite.

Unlock members-only posts

Sign up free to read members-only posts in full.