Optimise performance of model training and inference
Improve low-latency inference in real-time trading systems
Improve high-throughput inference for research
Improve straightforward CUDA code and whole-system efficiency across storage, networking and GPUs
From the employer’s posting
optimising the performance of our models – both training and inference
low-latency inference in real-time systems
high-throughput inference in research
Part of this is improving straightforward CUDA, but the interesting part needs a whole-systems approach, including storage systems, networking and host- and GPU-level considerations
Open 7 monthsWe first saw this posting 221 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
Status in our records
Live
First seen by us
Apr 14, 2026221 days ago
Recorded sightings
233
Last seen by us
Nov 21, 2026
Apr 14, 2026today
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
How this job compares
Time since we first saw it
Day 221
776
Up longer than most. Similar jobs usually come down between day 7 and day 76.
Well past Jane Street’s usual: its jobs come down by about day 93.
From 6,398 similar postings that came down, and 6 of Jane Street’s. Coming down is not always a hire.
Jane Street is hiring
26 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Check the employer’s posting for the current role and application details.
Applying through Greenhouse
No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.
We are looking for an engineer with experience in low-level systems programming and optimisation to join our growing ML team.
Machine learning is a critical pillar of Jane Street's global business. Our ever-evolving trading environment serves as a unique, rapid-feedback platform for ML experimentation, allowing us to incorporate new ideas with relatively little friction.
Your part here is optimising the performance of our models – both training and inference. We care about efficient large-scale training, low-latency inference in real-time systems and high-throughput inference in research. Part of this is improving straightforward CUDA, but the interesting part needs a whole-systems approach, including storage systems, networking and host- and GPU-level considerations. Zooming in, we also want to ensure our platform makes sense even at the lowest level – is all that throughput actually goodput? Does loading that vector from the L2 cache really take that long?
If you’ve never thought about a career in finance, you’re in good company. Many of us were in the same position before working here. If you have a curious mind and a passion for solving interesting problems, we have a feeling you’ll fit right in.
There’s no fixed set of skills, but here are some of the things we’re looking for:
An understanding of modern ML techniques and toolsets
The experience and systems knowledge required to debug a training run’s performance end to end
Low-level GPU knowledge of PTX, SASS, warps, cooperative groups, Tensor Cores and the memory hierarchy
Debugging and optimisation experience using tools like CUDA GDB, NSight Systems, NSight Computesight-systems and nsight-compute
Library knowledge of Triton, CUTLASS, CUB, Thrust, cuDNN and cuBLAS
Intuition about the latency and throughput characteristics of CUDA graph launch, tensor core arithmetic, warp-level synchronization and asynchronous memory loads
Background in Infiniband, RoCE, GPUDirect, PXN, rail optimisation and NVLink, and how to use these networking technologies to link up GPU clusters
An understanding of the collective algorithms supporting distributed GPU training in NCCL or MPI
An inventive approach and the willingness to ask hard questions about whether we're taking the right approaches and using the right tools
New ML Engineer postings at the employers we follow are down 4% over the last 6 weeks compared with the 6 before.
August 17Last week
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
About the role
We file this job under ML Engineer, by the work the posting describes.
ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.
Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.
A data scientist often works out which model to build; an ML engineer makes it run reliably in production.
US government figures for computer and information research scientists
Median yearly pay, May 2025
$140,300
Expected change, 2025 to 2035
21.8% more jobsagainst 3.5% for all jobs
The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.