Network Engineer, Supercomputing
Thinking Machines Lab is hiring a Network Engineer, Supercomputing for a remote role open to applicants in United States. It pays $350k-$475k a year and Level rates it ; you can apply on Thinking Machines Lab.
Level's read on this job
- Builds AI ●●●● is how Level rates this role: the job is building AI systems.
- This is listed as a remote role.
- The posting mentions visa sponsorship.
- The posting mentions Rdma, Rocev2 and Nccl among its tools and skills.
- Thinking Machines Lab has 57 other open roles on Level.
AI in this role
Own and optimize the low-level supercomputing network infrastructure and GPU fabrics powering large-scale AI model training and inference.
The mission of Thinking Machines is to build AI that extends human will and judgment. We are training frontier models with Inkling, developing Tinker to let people make models their own, and crafting interfaces that broaden human-AI communication. We believe the future worth building is human, and we're hiring people who want to build it.
About the Role
We're looking for a network engineer to own the lowest layers of the network stack that our large-scale training and inference depend on. A single degraded link or flapping NIC can quietly slow a long training run or take it down outright; you'll be responsible for interconnect reliability at scale, across large GPU fabrics — both the RDMA/RoCE fabric between nodes and the NVLink/NVSwitch domains within them.
This is a hands-on, cross-stack role. You'll debug production collectives down to the NIC, build the instrumentation and tooling that makes the next debugging session dramatically faster, and serve as the technical point of contact who drives issues to resolution with our cloud providers' networking teams. Your goal is for our researchers to trust the fleet without worrying about the fabric underneath.
Note: This is an "evergreen role" that we keep open on an on-going basis to express interest. We receive many applications, and there may not always be an immediate role that aligns perfectly with your experience and skills. Still, we encourage you to apply. We continuously review applications and reach out to applicants as new opportunities open. You are welcome to reapply if you get more experience, but please avoid applying more than once every 6 months. You may also find that we put up postings for singular roles for separate, project or team specific needs. In those cases, you're welcome to apply directly in addition to an evergreen role.
What You’ll Do
Reason about and validate GPU network fabric design across our deployments.
Debug RDMA / RoCEv2 across different NIC vendors. Diagnose collective failures of production NCCL, PFC/ECN tuning, and congestion control behavior.
Own NVLink / NVSwitch interconnect — including fabric manager and IMEX health, link and lane errors, and how the GPU fabric interacts with collectives.
Build host-level network instrumentation and use Linux tooling to build dashboards and alerts, not just the bug report.
Navigate cross-cloud fabric quirks across providers and triage across the NIC, driver, kernel, switch, and workload boundaries.
Drive escalations with cloud-provider networking teams, owning issues end-to-end until they're resolved.
Skills and Qualifications
Minimum qualifications:
Bachelor’s degree or equivalent experience in computer science, engineering, or similar.
Proficiency in at least one backend language (we use Python or Rust).
Experience operating large‑scale clusters and container orchestration systems (e.g. Kubernetes or Slurm).
Comfort operating across the stack and owning projects end-to-end.
Thrive in a highly collaborative environment involving many, different cross-functional partners and subject matter experts.
A bias for action with a mindset to take initiative to work across different stacks and different teams where you spot the opportunity to make sure something ships.
Preferred qualifications — we encourage you to apply if you meet some but not all of these:
Fluency with host-level debugging tools on Linux.
Strong communication skills, internally and with cloud providers.
Extensive experience with at least one of the following:
Familiarity with cloud network primitives across at least two cloud providers.
Hands-on experience with NVLink / NVSwitch, fabric manager, and IMEX.
Statistical rigor in reliability reasoning — comfort reasoning about failure and error rates, distributions, and base rates, and the judgment to separate signal from noise when characterizing a large fabric.
A track record of writing tooling that made the next debugging session meaningfully faster.
Familiarity with CUDA/NCCL and performance profiling for distributed training and inference.
Understanding of deep learning frameworks and their underlying system architectures.
Logistics
Location: This role is based in San Francisco, California.
Compensation: Depending on background, skills and experience, the expected annual salary range for this position is $350,000 - $475,000 USD.
Visa sponsorship: We sponsor visas. While we can't guarantee success for every candidate or role, if you're the right fit, we're committed to working through the visa process together.
Benefits: Thinking Machines offers generous health, dental, and vision benefits, unlimited PTO, paid parental leave, and relocation support as needed.
How we rate this
Network Engineer, Supercomputing at Thinking Machines Lab rates 85 out of 100 for how much of the daily work is AI. That makes it Builds AI (AI Level 4 of 4). The level is about AI in the job, not seniority.
Builds AI. The job is building AI systems.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Questions you could be asked
- Tell me about a project where networking was part of your work. What did you do?
- Tell me about a project where supercomputing was part of your work. What did you do?
- Tell me about a project where distributed systems was part of your work. What did you do?
- Tell me about a project where gpu infrastructure was part of your work. What did you do?
- Walk me through how you've used Rdma in your day-to-day work.
Adapt your resume
- List these exact terms on your resume: Networking, Supercomputing, Distributed Systems, GPU Infrastructure, and Rdma. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
- Lead with what you built, trained or shipped. This role is judged on the AI system itself, not the tools around it.
Get your CV reviewed before you apply
Send your CV and the role you want next. Your review arrives by email within 3 days.
Get new remote software engineering jobs (Builds AI ●●●●) by email
One email a week, each job rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free.
Similar roles
Software Engineering roles that build AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step