Jane Street is hiring a Low-Latency Engineer in Software Engineering — New York, New York, United States. The overview below is synthesized from the employer posting on janestreet.com: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
About the Position
Company context from the listing:
The listing frames the Low-Latency Engineer at Jane Street as a hands-on product role. You’ll work closely with our quantitative researchers and developers, taking a holistic approach to design and optimize our fast-trading systems.
We build systems primarily in OCaml with only small amounts of C and C++, but you don’t need any experience with OCaml in particular (we can teach it to you) or knowledge of the financial markets. The most important qualification is experience with low level systems programming and optimization, whether it is in C, C++, or any other language.
About You
Company context from the listing:
- Experience with low level systems programming and optimization, and working on network applications that require extremely low latency and high throughput
- Can understand, interpret, and improve application performance through hardware performance counters and other profiling tools
- Has a thorough understanding of modern computer architecture and can talk to others about it; for example, can you describe modern x86 AMD and Intel cache hierarchies?
- Some experience with fast-packet processing in user space and common kernel-bypass implementations would be ideal (such as Solarflare OpenOnload/TCPDirect/ef_vi, Exablaze, InfiniBand verbs, DPDK)
- Experience working around the performance challenges of languages with a managed runtime (such as Java or C#) and familiarity with a typed functional language are a plus
If you're a recruiting agency and want to partner with us, please reach out to agency-partnerships@janestreet.com.
Build a standout application
For the Low-Latency Engineer at Jane Street, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it. Add links to public work, keep formatting scannable, and close with a clear ask. Hiring managers skim — make impact obvious in the first half-page.
Career growth in Web3 rewards continuous learning. Follow protocol changelogs, practice with testnets, and contribute to open issues. Small, consistent contributions compound into credibility more than one-off credentials.