Time since we first saw it
Day 12
Similar jobs usually come down between day 3 and day 22.
From 472 similar postings that came down. Coming down is not always a hire.
Listed location: RemoteRead the full posting
Employment type: ContractFrom the employer’s posting
Department: EngineeringFrom the employer’s posting
Our reserved customers run large multinode GPU clusters, and when those clusters misbehave the problem is rarely simple.
One thing we will be straight about, because it shapes the job.
Will you now or in the future require sponsorship for employment visa status (e.g., H-1B, TN visa, etc.)?From the employer’s application form
Experience provisioning and operating GPU clusters with Kubernetes, Slurm, or both.
Experience with parallel filesystems (Weka, Lustre, GPFS) and high-performance storage.
Join us in putting the world’s compute behind the people building what comes next.
In the employer’s words · Read in context · Company website ↗
Actively hiringFirst seen by us 12 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 12
Similar jobs usually come down between day 3 and day 22.
From 472 similar postings that came down. Coming down is not always a hire.
3 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- Embedded ownership of named accounts. You are the engineer your customers know by name. You learn their workload, not just their infrastructure, and you tell them what to change before they hit the wall. - Proactive monitoring. Own the monitoring and alerting we put in front of customer clusters (Grafana, Prometheus) so we find faults before the customer reports them. - Tooling and pushing work down. Automate the repeat work and turn your own escalations into runbooks the L1 tier can run. Anything you fix three times should stop reaching you.
- Experience with parallel filesystems (Weka, Lustre, GPFS) and high-performance storage. - Grafana, Prometheus, or similar observability stacks in production. - Prior forward deployed engineer, solutions architect, or technical account manager experience.
- Hardware fault triage on GPU nodes: XID and ECC errors, dmesg, lspci, nvidia-smi, thermal and power faults. - Experience provisioning and operating GPU clusters with Kubernetes, Slurm, or both. - Genuinely comfortable customer-facing, including delivering bad news and saying “this is ours” or “this is the provider’s” with confidence.
- Prior forward deployed engineer, solutions architect, or technical account manager experience. - Infrastructure as code (Terraform, Ansible) and CI for cluster provisioning. - Exposure to model training or inference workloads from the practitioner side.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Join us in putting the world’s compute behind the people building what comes next.
At Hyperbolic, we’re making global AI compute liquid. We bring fragmented, heterogeneous GPU capacity together into one unified, productive platform, making it easier to access, sell, resell, manage, and orchestrate the resources that power AI. For neocloud, we turn GPU capacity into productive infrastructure that delivers lasting value and accelerate their time to market.
We believe bold ideas deserve the computing power to become reality. We’re building toward a future where compute flows as freely as electricity, available when and where it’s needed, so builders everywhere can turn their most ambitious ideas into breakthroughs.
We’re looking for curious, driven people who take ownership, challenge assumptions, and care deeply about what they build. If you’re energized by hard problems and want to help shape how the world accesses AI, we’d love to build with you.
Our reserved customers run large multinode GPU clusters, and when those clusters misbehave the problem is rarely simple. You are the engineer embedded with those customers: you stand their cluster up, you hand it over, and you stay with it.
You do not own tickets. You own environments. Technical Support Engineers own the ticket lifecycle and pull you in when an issue needs real depth: multinode collective performance, hardware faults, fabric problems, or a provider who needs to be told what is wrong with their hardware.
One thing we will be straight about, because it shapes the job. We aggregate capacity from suppliers rather than owning most of the hardware ourselves. That means a real part of this role is technical liaison work: proving where a fault actually lives, taking it to the provider with evidence, and coordinating the fix on the customer's behalf. The engineers who enjoy this role are the ones who find that interesting rather than frustrating.
Who You Are
Cluster stand-up and handoff. Build, validate, and benchmark new customer clusters, then hand them over with documentation the customer's own engineers can work from.
Deep escalations. Multinode and NCCL performance debugging, GPU and hardware faults (XID and ECC errors, lspci, dmesg), driver and fabric issues, container and scheduler problems.
Provider escalation and coordination. Maintenance windows, RMAs, hung nodes, and disputed fault attribution. You bring the evidence that makes the provider act, and you keep the customer informed while it happens.
Embedded ownership of named accounts. You are the engineer your customers know by name. You learn their workload, not just their infrastructure, and you tell them what to change before they hit the wall.
Proactive monitoring. Own the monitoring and alerting we put in front of customer clusters (Grafana, Prometheus) so we find faults before the customer reports them.
Tooling and pushing work down. Automate the repeat work and turn your own escalations into runbooks the L1 tier can run. Anything you fix three times should stop reaching you.
Deep Linux experience and total comfort in the CLI, including in someone else's broken environment.
Hands-on multinode GPU experience: NCCL, InfiniBand or RoCE, collective performance debugging, topology and placement.
Hardware fault triage on GPU nodes: XID and ECC errors, dmesg, lspci, nvidia-smi, thermal and power faults.
Experience provisioning and operating GPU clusters with Kubernetes, Slurm, or both.
Genuinely comfortable customer-facing, including delivering bad news and saying “this is ours” or “this is the provider’s” with confidence.
Sound judgment on when to keep digging and when to escalate.
Preferred Qualifications
Experience with parallel filesystems (Weka, Lustre, GPFS) and high-performance storage.
Grafana, Prometheus, or similar observability stacks in production.
Prior forward deployed engineer, solutions architect, or technical account manager experience.
Infrastructure as code (Terraform, Ansible) and CI for cluster provisioning.
Exposure to model training or inference workloads from the practitioner side.
Hyperbolic is an equal opportunity employer. We celebrate diversity and are committed to creating an inclusive environment for all employees.
We file this job under Forward Deployed Engineer, by the work the posting describes.
Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.
Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.
An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Remote
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.