Linux Engineer

We're looking for Linux Engineers to join theteam that maintains the critical infrastructure underlying the rest of Jane Street'stechnology. It's a broad role, and no two Linux Engineers look exactly alike. Our work spanson-prem and cloud infrastructure, every major pillar (compute, storage, networking), and every layer of the stack from the physical hardware to workload orchestration. You should expect to workin some (but not necessarily all) of these areas,and to go genuinely deep in a few.

That might mean:

• Building the in-house tools and systems that make up our platform, or integrating mainstream (often open-source) technologies sothey feel native to our infrastructure
• Acting as one of the firm's Linux experts, and teaching other engineers specialist skills like systems debugging
• Automating our own work, because it makesus faster and more reliable (and we think it'sfun)
• Diagnosing and resolving production issues in real time, often under time pressure
• Carrying out scheduled changes to the platform, like upgrades, migrations, capacity changes, and rollouts, planned meticulously and executed carefully

The problem space runs from the physical to the abstract: datacenter provisioning and orchestration, kernels and drivers delivered through Nix and RPMs, production and research storage at scale, cloud that integrates cleanly with our on-prem platform, and, in partnership with our IT and Network Engineering colleagues,Linux desktops and how our hosts participate inthe network.

We see Linux Engineering and Software Engineering as two ends of a spectrum, and plentyof people could do either job well. Linux Engineering is likely the better fit if you treat

Linux itself as your problem space: you like working close to the operating system, you want tolook after production infrastructure, andyou're happy spending more of your time in aconsulting capacity than a typical developer would. (Compared with kernel development, the emphasis flips: you'd rarely develop thekernel itself, though targeted patches happen, andyou'd spend far more time running production infrastructure.) We're hiring for both rolesand are happy to advise you on which might fitbest.

We don't expect you to come in with deep experience; we're happy to hire smart problem-solvers and teach them what they need toknow. But the job leans much more toward engineering than a traditional operations role:relentless automation instead of manual toil, anda large body of in-house technology rather thanonly off-the-shelf tools. You'll build systems, not just operate them.

We don't expect you to have a background infinance or any other specific field — we'relooking for smart people who enjoy solving interesting problems. We're more interested inhow you think and learn than what you currently know. You should be:

• Knowledgeable about operating system fundamentals, computer architecture, and systems programming concepts like sockets, virtual memory,and the process life cycle
• Able to understand network protocols at abasic level
• Comfortable at the command line of aLinux machine (whether from coursework, side projects, or time spent administering a campus computer lab) and fluent in basic introspection and troubleshooting: system health, individual processes, logs
• Someone who solves problems by writing code (in any language) and cares about robust software engineering
• Intellectually curious, collaborative,humble, and eager to learn (including from mistakes)

Agricultural, Forestry & Food Sciences,Architecture, Urban & Environmental Planning,Computer Science, Data, AI,Economics & Management,Engineering & Technology,Life and Health Sciences, Medicine,Natural Sciences & Mathematics,Society, Politics & Interdisciplinary Studies