Senior Engineer, Infrastructure Services
New York, NYFull-timePosted 2mo agoStill listed today
Most applications go out cold — see where you stand first. No sign-up to start.
Watch jobs like this. New roles like this one near New York, NY, by email.
Don't just apply. Show up ready.
Olive works from this exact posting.
At a glance
Olive lists jobs from US employers, including remote roles you can work from the United States.
Job overview
Ornn is building infrastructure for AI compute, and this role will develop and operate the systems underneath its Fabric platform across GPU clusters and datacenters. The engineer will work across Linux, Kubernetes and Slurm, networking, storage, virtualization, and distributed control systems, with ownership spanning infrastructure design, production operations, and debugging across the stack.
Skills & qualifications
Skills
Qualifications
Benefits
Full job description
Silicon Infrastructure Engineer New York
Eng
In office
Full-time
Silicon Infrastructure Engineer
About Ornn
Ornn is building the financial infrastructure for AI compute. Our price indices are live on Bloomberg Terminal. We structure and trade compute hedging instruments. And we're now building a platform that brings exchange-grade mechanics like order management, matching, scheduling, and settlement to how compute capacity gets reserved and allocated. We're a lean team in New York, backed by leading venture and strategic investors.
About the Role
You would be one of the first infrastructure engineers responsible for the systems underneath Ornn Fabric. Fabric spans heterogeneous GPU clusters, datacenter infrastructure, schedulers, virtualization, networking, and the control plane that makes physical compute capacity available as a reliable financial product.
This is not a traditional cloud infrastructure role. You will work across Linux hosts, Kubernetes and Slurm clusters, containers and VMs, bare-metal provisioning, node management, networking, storage, and distributed control systems.
You will work directly with our Head of Engineering and have significant ownership over how Ornn operates infrastructure across multiple datacenters and compute providers. Expect to debug failures across the entire stack, from a process inside a container down to the physical node it is running on.
What You'll Do
-
Build and operate the infrastructure layer powering Ornn Fabric across heterogeneous GPU clusters and datacenters.
-
Design systems for provisioning, scheduling, isolating, monitoring, and managing compute across bare-metal, containerized, and virtualized environments.
-
Build infrastructure software in Rust and Python for node management, orchestration, telemetry, networking, and cluster operations.
-
Operate and extend Kubernetes and Slurm environments, including technologies such as RKE2, Slinky, container runtimes, and GPU scheduling.
-
Design secure multi-tenant compute environments using containers, VMs, hypervisors, Kata Containers, device passthrough, virtio, and related isolation technologies.
-
Debug complex failures across Linux, networking, storage, schedulers, virtualization, GPUs, and distributed systems.
-
Build systems for collecting and querying infrastructure state, telemetry, inventory, health, and utilization data.
-
Automate infrastructure deployment and lifecycle management across clusters rather than relying on one-off operational procedures.
-
Make reliability a feature: design systems that degrade predictably, recover automatically, and expose enough information to understand failures when they occur.
What We're Looking For
-
Strong Linux systems knowledge. You are comfortable debugging processes, networking, memory, filesystems, devices, permissions, namespaces, cgroups, and system-level performance issues.
-
Strong Rust knowledge and experience building production systems software.
-
Working knowledge of SQL and experience designing or interacting with data-intensive backend systems.
-
Experience operating containerized and virtualized workloads in production.
-
Deep familiarity with Kubernetes and/or Slurm and the systems surrounding them. Experience with technologies such as RKE2, Slinky, Docker/containerd, Kata Containers, or similar infrastructure is strongly preferred.
-
Understanding of virtualization fundamentals including hypervisors, KVM/QEMU-style architectures, virtio, device passthrough, and workload isolation.
-
Strong understanding of distributed systems, including failure handling, coordination, state management, idempotency, consistency, and observability.
-
Comfort working across abstraction boundaries. You should be willing to debug an application, kernel interaction, network path, scheduler, hypervisor, or physical server depending on where the problem actually is.
-
Ability to operate independently in a lean engineering team and own systems from design through production.
-
BS, MS, or equivalent experience in computer science, computer engineering, electrical engineering, or a related technical field.
Nice-to-Haves
-
Experience deploying or operating infrastructure inside datacenters, particularly large GPU or HPC clusters.
-
Knowledge of modern GPU architecture, including CUDA execution, GPU memory, kernels, PCIe, NVLink, RDMA, GPUDirect, and multi-GPU communication.
-
Experience debugging GPU workloads and performance at the kernel, runtime, or communication layer.
-
Understanding of server management and node tenancy architectures, including BMCs, IPMI, Redfish, iDRAC/iLO, out-of-band management networks, and secure tenant access.
-
Experience with high-performance networking such as InfiniBand, RoCE, RDMA, BGP, ECMP, or high-bandwidth Ethernet fabrics.
-
Experience with distributed storage systems such as Ceph, WEKA, or other high-performance storage architectures.
-
Experience building infrastructure for cloud providers, neoclouds, HPC environments, exchanges, or other systems where downtime and incorrect state have direct financial consequences.
Why This Role Matters
Ornn Fabric ultimately turns physical compute infrastructure into something that can be scheduled, reserved, financed, and traded reliably.
That abstraction only works if the underlying machines can actually be provisioned, isolated, monitored, recovered, and delivered as promised. A failed node, broken network path, scheduler inconsistency, or tenancy issue is not merely an infrastructure problem when contractual capacity commitments depend on the system being correct.
The infrastructure layer is therefore foundational to everything Ornn is building. The systems you build will determine how reliably Fabric can onboard new datacenters, expose capacity to customers, and scale from individual clusters to a distributed compute market.
Compensation and Benefits
Benefits include competitive salary, meaningful equity, health coverage, free meals, and additional benefits. This is a high-ownership engineering role with significant influence over Ornn's infrastructure architecture and technical direction.
Equal Opportunity Statement
Ornn is committed to building a diverse team. We evaluate candidates based on their ability to do the work, not on pedigree or background. We encourage applications from people of all backgrounds and experiences.
Ready to apply? Powered by
First name *
Last name *
Email *
LinkedIn URL
Resume * Click to upload or drag and drop here
Req ID: R11
How this job compares
Set against the 4,486 open Infrastructure Engineer jobs on Olive Jobs, counted November 2, 2026.
- Pay
- This postingNot listed
- New York median$160–230K/yr218 salary ranges
- US median$50–60/hr93 hourly ranges
- Openings
- Olive Jobs lists 275 open Infrastructure Engineer jobs in New York and 4,486 across the US. 8% of them nationwide are listed as remote or flexible.
- Experience
- Infrastructure Engineer postings that state a minimum ask for 6 years of experience at the median; the middle half ask for 5 to 8 years (3,513 postings).
- Education
- 941 of the 4,486 open Infrastructure Engineer jobs (21%) ask for a bachelor's degree or higher.
Counted across the open, public US postings on Olive Jobs on November 2, 2026. Pay medians are the middle values of the low ends and of the high ends of postings that list both ends of a range in the same cadence (a yearly salary or an hourly rate); a range's midpoint is halfway between its ends. Pay and experience figures resting on fewer than 20 postings are left out.
You've read the whole posting — now see how you match it.




