Staff Systems Engineer Low Latency & Networking

Other Jobs To Apply

No other job posts for this day.

Jito Labs is architecting the future of high-performance distributed systems on Solana. We’re the team behind Jito-Solana, the leading MEV Solana client, and the Jito Block Engine, which has generated roughly 4.5 million SOL for validators and stakers over the past year. Our latest product, BAM, reimagines Solana market structure and the transaction supply chain with a heavy emphasis on performance, reliability, and transaction privacy. We are building systems that operate at the edge of what modern hardware and networks can sustain. We're looking for a senior engineer who is comfortable working across application code, operating systems, hardware behavior, and network protocols — someone who enjoys debugging the kinds of problems where the root cause might live anywhere in the stack. About the Position: We build latency-sensitive infrastructure where microseconds matter and root causes are rarely obvious. This role is for someone who can move comfortably between application code, kernel internals, hardware behavior, and network protocols — debugging a TCP retransmission anomaly one day and reasoning about memory contention the next. You should be as comfortable reading kernel source and packet captures as you are writing production Rust. Much of the work involves ambiguous, cross-layer problems where existing tools and playbooks are insufficient and new ones must be created. This is a senior role for someone who has previously been the person others escalate to when nobody else can find the root cause. You'll work across: n Networking Debug and optimize network performance end-to-end: NIC tuning, congestion control, packet pacing, queueing disciplines Analyze traffic using tcpdump, Wireshark, and custom tooling; reason about protocol behavior under load Work with protocols beyond TCP/UDP when required (e.g., ICMP, IGMP, multicast) Experience with high-performance I/O and kernel-bypass techniques such as DPDK, XDP, io_uring, or similar Linux Systems Read and reason about Linux kernel source when debugging requires it Understand networking stack internals (socket buffers, congestion control, netfilter, scheduling interactions) Build bespoke tooling when existing observability is insufficient Work fluently with kernel interfaces used by performance-sensitive systems Hardware & Performance Use hardware performance counters, perf, eBPF, and flamegraphs to locate real bottlenecks Reason about practical CPU behavior: cacheline contention, branch misprediction, NUMA effects, memory ordering Understand IRQ affinity, scheduling behavior, paging, and TLB effects under real workloads Willing to read assembly when the situation calls for it Software Development Strong low-level systems programming background We work primarily in Rust, but strong experience in C or C++ is equally relevant Solid understanding of algorithms, data structures, and writing correct concurrent code Contribute to infrastructure, tooling, and occasionally upstream projects Requirements 10+ years of experience in systems programming, networking, or performance-critical infrastructure Deep Linux expertise, including kernel behavior, networking internals, and performance tuning Proficiency with packet analysis and network debugging tools Experience with performance profiling and tracing (perf, eBPF, flamegraphs, etc.) Strong programming fundamentals; depth matters more than language Track record of diagnosing complex issues spanning application, OS, and hardware layers Clear, direct communication Strong Plus Experience in domains where latency and performance are first-order constraints (e.g., HFT, real-time systems, low-latency networking, kernel-adjacent infrastructure, high-performance distributed systems) Custom memory allocators or deep memory subsystem optimization Virtualization internals and passthrough networking (SR-IOV, vDPA, etc.) Kernel-adjacent work (eBPF programs, driver debugging, custom modules) olana or blockchain infrastructure experience n $220,000 - $275,000 a year -Salary based on experience -Above-market total compensation and multiple forms of equity -100% employer-paid health benefits -All-expenses-paid team retreats and conferences -Weekly meal voucher n Why Jito We’re a small, profitable company with real product-market fit. That means: -High ownership: you drive major technical decisions and shape the direction of the system -Fast execution: we ship quickly and iterate on real-world behavior -Technical depth: the problems are real, complex, and intellectually demanding -Sustainable: strong financials allow us to focus on long-term impact, not runway Please mention the word **PROSPERITY** and tag RMjYwNzo1MzAwOjIwZDo3ZDAwOjo= when applying to show you read the job post completely (#RMjYwNzo1MzAwOjIwZDo3ZDAwOjo=). This is a beta feature to avoid spam applicants. Companies can search these words to find applicants that read this and see they're human.

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...