Jump Trading hires Software Engineer / Core Dev, Quant Researcher and Quant Trader. Candidates report 3 to 5 interview stages depending on the track (7 distinct rounds across all tracks). Below: what each round tests and how to prepare, the path by track, the timeline, pay and a 4-week prep plan, drawn from candidate reports.
Jump Trading interview: quick answer
- StagesBy track: Software Engineer / Core Dev: 5 · Quant Researcher: 5 · Quant Trader: 3 (7 distinct rounds across all tracks)
- Online assessmentCodility · 2–3 problems · ~80–150 min
- TimelineAbout three to four weeks once interviews start, per one outside guide, with results usually within a week per round; headhunter-led processes can take longer.
- Final roundSuperday of several 45 to 60 minute interviews, usually in Chicago, with behavioural conversations woven through
- Pay (candidate-reported)Software Engineer / Core Dev, New grad: $300k – $500k total comp
- RolesSoftware Engineer / Core Dev, Quant Researcher, Quant Trader
Preparing for Jump Trading? Work the rounds in order in the free Jump Trading interview funnel, or start with the free online-assessment sample (no signup).
The Jump interview process at a glance
| # | Round | Format and length | Who takes it | Prep |
|---|---|---|---|---|
| 1 | HR / Recruiter Call | 30–45 min · phone | All tracks | GuidePractice |
| 2 | Online Assessment | Codility · 2–3 problems · ~80–150 min | Software Engineer / Core Dev | OA guidePractice |
| 3 | Technical Phone Screen | 45–60 min · CoderPad / Zoom | All tracks | GuidePractice |
| 4 | Quant / Math Round | Superday · probability / linear algebra / game theory | Quant Researcher | GuidePractice |
| 5 | Live Data-Science Round | ~60 min · live pandas + ~75 min ML coding | Quant Researcher | GuidePractice |
| 6 | Onsite Coding + System Design | Superday · ~4–7 rounds · C++ + systems | Software Engineer / Core Dev | GuidePractice |
| 7 | Behavioral / Culture | Interspersed · small boss → big boss | All tracks | GuidePractice |
Stages are listed in the order candidates report them. Formats come from candidate reports and change between cycles, offices and teams; the "Who takes it" column shows which track each round belongs to.
How the Jump process differs by track
Jump runs separate loops for different roles. Here is the path each track reports, in order:
- Software Engineer / Core Dev (5 stages): HR / Recruiter Call → Online Assessment → Technical Phone Screen → Onsite Coding + System Design → Behavioral / Culture
- Quant Researcher (5 stages): HR / Recruiter Call → Technical Phone Screen → Quant / Math Round → Live Data-Science Round → Behavioral / Culture
Quant researchers usually skip the online assessment. - Quant Trader (3 stages): HR / Recruiter Call → Technical Phone Screen → Behavioral / Culture
One outside guide describes a trader screen on probability and expected value, then a superday trading round on futures market structure, options and backtesting. QuantVault has fewer reports for this track.
Not sure which track fits you? See quant trader vs quant researcher.
Every Jump round: what it tests and how to prepare
1HR / Recruiter Call
Background, resume, motivation, and English fluency. For SWE: 'why C++', 'why Jump'. Mostly a conversation: you usually pass if communication is solid. HR is responsive and fast (often two recruiters follow up).
How to prepare
- Have a crisp 'why Jump / why C++ (or why research)'. It's mostly fit and communication at this stage.
- Be ready on location/visa. Chicago HQ; strong UIUC pipeline; some roles are office-specific.
- Know your resume cold — the later technical rounds deep-dive it.
2Online Assessment
SWE/Core-Dev gate (QR usually skips it). Codility: 2-3 coding problems, very long prose and heavy string parsing; ~LC easy-medium, yet parsing and a complexity-gated last problem cause timeouts.
Question types: mostly coding, especially complexity analysis, data structures, combinatorics and greedy. Latest candidate report for this round: Mar 2026.
How to prepare
- Read the (long) prose carefully and parse robustly. Half the difficulty is string/format parsing, not the algorithm.
- Watch the complexity-gated last problem. Get the optimal approach before coding — brute force TLEs.
- Practice the recurring ones: RPN/stack calculator with overflow checks,
ls -lparsing, indicator→position vector, knapsack stock-picking, and a ≤3-line binary-search bug fix.
Jump Trading online assessment guide →Practice this round (20 questions) →
3Technical Phone Screen
Split by track. Software candidates get a resume deep-dive, C++ internals and one coding problem, often building a standard container from scratch with attention to memory management and exception safety. Quant research candidates go straight into two or three problems mixing probability, linear algebra and regression.
Question types: mostly coding, brain teasers and expectation, especially data structures, complexity analysis, string algorithms and combinatorics. Latest candidate report for this round: Jun 2026.
How to prepare
- SWE: be able to implement std::vector end-to-end and discuss smart pointers, vtables, RAII, and struct padding.
- Coding is judged on thought process + follow-ups, not speed — narrate, then optimize.
Full Technical Phone Screen guide →Practice this round (32 questions) →
4Quant / Math Round
The quant research maths round: probability, linear algebra, combinatorics, Bayesian reasoning, optimal stopping and game theory, often including a dynamic-programming problem and a game where you reason about other players' strategies.
Question types: mostly probability, expectation and game theory, especially expected value, matrix operations, conditional probability and eigenvalues. Latest candidate report for this round: Jan 2026.
How to prepare
- Drill the recurring set: nested-interval E/Var, equal-pairwise-correlation range, optimal stopping (secretary), and the guess-⅓-mean mixed strategy.
- Linear algebra shows up live — be fluent constructing matrices from properties.
- Variance-minimizing split is a favorite: O(n) with running variance, then the k-group DP generalization.
Full Quant / Math Round guide →Practice this round (37 questions) →
5Live Data-Science Round
Jump's distinctive quant research round: you are given a pandas time-series dataset and build a model end to end in about an hour (train/test split, rolling windows, regularized regression with scikit-learn), with finance-intuition follow-ups. A second session of about 75 minutes asks you to debug and complete a long pre-written ML script. Interviewers are reserved and give few hints.
Question types: mostly machine learning and time series.
How to prepare
- Practice an end-to-end pandas→sklearn pipeline under time pressure — load, time-aware split, rolling features, fit Lasso, evaluate — without fumbling the API.
- Respect time-series structure: no look-ahead, rolling/walk-forward validation, and explain the finance intuition behind features.
- Prep a public dataset you can discuss (summary, plots, a quick model) — it's a real prompt.
Full Live Data-Science Round guide →Practice this round (2 questions) →
6Onsite Coding + System Design
The engineering superday, virtual or in person: two technical coding rounds in C++ and algorithms, often a system-design round, and behavioural rounds with increasingly senior leaders. Candidates report low-level tasks such as writing a memory allocator or an optimized hash map.
Question types: mostly coding and combinatorics, especially complexity analysis, data structures, dynamic programming and sorting and searching. Latest candidate report for this round: Jun 2026.
How to prepare
- Systems depth wins: custom allocators, an in-memory order-book engine, lock-free thinking, and cache/latency reasoning.
- For system design, focus on the network path — TCP vs UDP trade-offs, reliability, and scaling a push system to thousands of clients.
- Expect terse interviewers. Drive the conversation and state your assumptions; they give few hints.
Full Onsite Coding + System Design guide →Practice this round (12 questions) →
7Behavioral / Culture
Behavioral rounds with increasingly senior leaders, woven through the onsite. Standard prompts: a failure and how you recovered, a project explained to a non-technical person, how colleagues would describe you. The vibe is reserved and secretive: read the room and keep answers tight.
- One superday slot covers fit, your projects and what you know about the sector.
How to prepare
- Have 3 STAR stories ready — a technical win, a failure with a lesson, and a teamwork story.
- Match the reserved tone — concise, substantive answers; don't oversell.
- Show genuine interest in low-latency / research — culture fit with a deep-tech, secretive shop.
Practice the Jump rounds in order
Each round in the Jump funnel has its own practice set, with worked solutions and progress tracking. A free account saves your progress across rounds.
Timeline
- One outside guide puts the process at three to four weeks once interviews start; processes run through headhunters can take months.
- Candidates report results within about a week of each round.
Regional differences
Most superdays are held in Chicago. One outside guide reports smaller processes in New York, London, Amsterdam and Singapore.
A 4-week Jump prep plan
Built from the order of Jump Trading's rounds on the Software Engineer / Core Dev path and the topics in each round's practice set. Compress it if your first interview is sooner. Other tracks can swap in their own rounds from the table above.
| When | Focus | What to do |
|---|---|---|
| Week 1 | Foundations | Review coding, probability and expectation, the topics that dominate Jump Trading's practice sets. Start with Quant coding course and Probability course. Work the easy and medium questions in the Jump Trading question set. |
| Week 2 | Early rounds: HR / Recruiter Call, Online Assessment and Technical Phone Screen | Practice coding, brain teasers and expectation under time pressure, and take the free OA sample (format notes in the OA guide). Talk every answer through out loud; interviewers score the reasoning. |
| Week 3 | Later rounds: Onsite Coding + System Design and Behavioral / Culture | Move to coding and combinatorics. Do timed coding sessions in your interview language. Read how quant superdays work. |
| Week 4 | Rehearse the full loop | Run each practice round in order, redo the questions you missed, and prepare two project stories plus a specific answer to "why Jump Trading?" (see behavioral questions at trading firms). |
Jump pay
| Role | Level | Total comp | Notes |
|---|---|---|---|
| Software Engineer / Core Dev | New grad | $300k – $500k | Top-of-market HFT engineering comp; C++ low-latency roles. Heavily bonus-driven. |
| Quant Researcher | New grad / PhD | $350k – $600k | PhD-skewed research track; comp scales fast with performance. |
Total compensation means base salary plus bonus and any sign-on, as candidates self-report it. Job postings usually show base salary only, so posted figures and outside salary pages often look lower. Rough ranges, NOT offers. Jump pays at the very top of the HFT market, heavily bonus-driven; figures are opaque due to the firm's secrecy. Source: Candidate self-reports (levels.fyi, Glassdoor, and candidate forums) — not employer-verified. Last updated May 29, 2026.
Jump teams and what their interviews test
Jump hires Software Engineers / Core Devs (C++ low-latency), Quant Researchers, and Quant Traders. SWE runs a Codility OA → C++ tech screen → coding + systems-design onsite. QR usually skips the OA: a probability/linear-algebra phone screen → a superday with a math round, a live data-science round, and a coding round. No market-making game is reported for SWE or QR; quant trader candidates report a superday trading round on futures, options and backtesting.
| Tracks | What it does | What its interviews test |
|---|---|---|
| Software Engineer / Core Dev Software Engineer | Low-latency C++ trading systems, exchange connectivity, performance. | See the round-by-round section above. |
| Quant Researcher Quant Researcher | Signal research and modeling. Top-10 PhD skew. | Phone: probability + linear algebra + 1 coding → superday: math (probability/linalg/game theory), a live ~60-min pandas modeling round, and an ML-script coding round. |
| Quant Trader Quant Trader | Algorithmic / systematic trading. | Probability and expected-value screen, then a superday trading round on futures market structure, options and backtesting (candidate-reported). Reports differ on whether a mock trading game is included; coding and brain-teasers also come up. |
About Jump
| Firm type | Proprietary HFT / algorithmic trading |
|---|---|
| Trading style | C++ low-latency + quant research · Ultra-low-latency / high-frequency |
| Founded | 1999 |
| Headquarters | Chicago, IL |
| Other offices | New York, London, Singapore, Shanghai, Hong Kong |
| Capital | Proprietary (private) |
| Employees | ~1,900 |
| Reported performance | ~$6-8B/yr (est.); recent years softer |
Founded 1999 in Chicago
Jump Trading was founded in 1999 by two former floor traders and grew into one of the most secretive and technically formidable HFT firms, with a heavy investment in low-latency engineering, microwave networks, and research. It trades its own capital and is famously tight-lipped about its strategies and even its org structure.
Culture
Secretive and NDA-heavy — titles and teams are deliberately opaque. Target-school skewed (UIUC/CMU for dev, top-10 PhDs for QR). The process is lean and fast (results in ~1 week per round) but interviewers are reserved and give few hints (the experience varies a lot by interviewer).
What the interviews feel like
Engineering- and research-deep: software and quant research candidates report no market-making or betting round, while quant trader reports differ on whether a game comes up.
Highly siloed
Jump is very siloed: your day-to-day and growth depend almost entirely on which group you land in. Diligence the specific team, not just the brand.
Practice for Jump on QuantVault
Practice
Courses
Further reading
- How quant superdays work
- Behavioral questions at trading firms
- C++ and low-latency interview questions
- Market-making game interview guide
- The quant interview process, explained
Similar firms to compare
Firms with a similar business and interview style. Many candidates interview at several of them in the same cycle.
Sources and how this guide is built
- Updated October 20, 2026; firm data last reviewed May 29, 2026; pay last updated May 29, 2026.
- Round detail draws on 81 questions candidates report from Jump Trading interviews (the most recent report across all rounds is from Jul 2026). A separate curated Jump question set of 95 problems collects the most useful practice for this firm.
- Public candidate reports and outside interview guides are cross-checked against each other. Where they disagree the page says "reports differ"; details from a single source are marked as candidate reports.
- No actual interview questions are reproduced on this page. The questions, with worked solutions, are in the practice rounds.
Jump interview FAQ
How many rounds are in the Jump Trading interview?
It depends on the track: Software Engineer / Core Dev: 5; Quant Researcher: 5; Quant Trader: 3 stages. Across all tracks candidates report 7 distinct rounds: HR / Recruiter Call, Online Assessment, Technical Phone Screen, Quant / Math Round, Live Data-Science Round, Onsite Coding + System Design, Behavioral / Culture.
How long does the Jump Trading interview process take?
About three to four weeks once interviews start, per one outside guide, with results usually within a week per round; headhunter-led processes can take longer.
Does the Jump Trading process differ by role?
Yes. Software Engineer / Core Dev: HR / Recruiter Call, Online Assessment, Technical Phone Screen, Onsite Coding + System Design, Behavioral / Culture. Quant Researcher: HR / Recruiter Call, Technical Phone Screen, Quant / Math Round, Live Data-Science Round, Behavioral / Culture. Quant Trader: HR / Recruiter Call, Technical Phone Screen, Behavioral / Culture.
How much does Jump Trading pay?
Candidate-reported total compensation: Software Engineer / Core Dev (New grad) $300k – $500k; Quant Researcher (New grad / PhD) $350k – $600k. These are self-reported totals including bonus, not offers; job postings usually list base salary only.
How should I prepare for the Jump Trading interview?
Prepare round by round over about four weeks: foundations first, then the early rounds (HR / Recruiter Call, Online Assessment, Technical Phone Screen), then the later rounds, then a full rehearsal. Each round has its own practice set on QuantVault, and the online assessment has a dedicated guide.
What does Jump Trading do?
Jump Trading is a proprietary HFT / algorithmic trading firm headquartered in Chicago, IL. Jump Trading was founded in 1999 by two former floor traders and grew into one of the most secretive and technically formidable HFT firms, with a heavy investment in low-latency engineering, microwave networks, and research.
Is there a trading game in the Jump interview?
It depends on the track, and reports differ. QuantVault candidate reports describe no market-making game for software and quant research candidates. One outside guide describes a dedicated trading round for quant trader candidates on futures, options and backtesting, and another says trader interviews may include a mock trading game.
Is there an online assessment for quant roles at Jump?
Reports differ. Software candidates take a Codility test, and some crypto trading and SRE tracks report coding or shell tests. One outside guide says there is generally no mass maths test, while another lists an OA for every track.
Where is the Jump Trading superday?
Usually in Chicago, according to one outside guide; some processes run in other offices.
Which programming language should I use at Jump?
C++ for engineering roles. Quant and trader coding rounds use Python with pandas and NumPy, according to an outside guide and QuantVault candidate reports.
Start preparing for Jump Trading
Open the interactive Jump Trading interview funnel: every stage with its practice set, from the first screen to the final round. Create a free account to save your progress.