Linux Engineer
Jane Street · New York, NY
—
Jul 22, 2026
New York, NY
Jul 23, 2026
What this job asks for AI summary
A hands-on infrastructure role focused on maintaining and improving Linux-based systems across compute, storage, networking, and cloud — both on-premises and in the cloud. Day-to-day work includes building internal tooling, automating operational tasks, resolving production issues, and carrying out platform changes such as upgrades and migrations. The role suits engineers who enjoy working close to the OS and want to own production infrastructure rather than focus purely on application development.
Mid level · New York-Newark-Jersey City, NY-NJ-PA · Full-time
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $122,015 (middle half $98,091–$145,542).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (10)
Jane Street is headquartered in New York City; no location is stated explicitly in the posting but the firm's primary office is NYC. Remote is not offered.
The role sits at the boundary between infrastructure operations (15-1244) and software development (15-1252). The posting explicitly frames it as 'two ends of a spectrum' and emphasises building in-house tools and systems, relentless automation, and a large body of in-house technology — strong signals toward 15-1252. However, the primary framing is maintaining production Linux infrastructure, owning the OS as the problem space, and spending significant time in a consulting/operations capacity, which tips the primary classification to 15-1244.
No specific years of experience are required; the posting explicitly states 'we don't expect you to come in with deep experience' and welcomes new graduates and career-changers, supporting a Mid band (the role requires genuine engineering competence but no seniority floor).
Nix (the package manager/OS) and RPMs are mentioned as delivery mechanisms for kernels and drivers in the team's stack narrative, not in a formal requirements section — treated as preferred.
Cloud infrastructure and storage systems appear as areas of the team's work (stack context) rather than explicit candidate requirements — treated as preferred.
Networking protocols are called out as a required baseline ('able to understand network protocols at a basic level') and are therefore a hard gate.
Systems programming concepts (sockets, virtual memory, process life cycle) are explicitly listed as required knowledge.
Automation/scripting is strongly gated ('solves problems by writing code') and is a recurring theme throughout the requirements prose.
No compensation range is disclosed.
Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): workload orchestration.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.