Member of Technical Staff

Perimeter Compute Inc; United States; Remote; USD 120,000 - 180,000; Full time

Benefits offered by this job

Health, dental and vision insurance

Unlimited PTO

$500 home office stipend

Top-spec MacBook

Unlimited tokens

Job summary

Perimeter Compute Inc is hiring for a fully remote role in the United States. You will build and operate production software that runs GPU infrastructure across city-scale sites, collaborating with customers and teammates to define and deliver the next generation of infrastructure.

You will own from concept to production, handle on-call pager duties, and document decisions to enable future operators (human or agent) to reproduce successful outcomes.

Qualifications

• Have built and run production software that people depend on.
• Own it when it breaks and fix it, regardless of how long it took.
• Have worked below the app layer: Linux, networking, hardware or distributed systems.

Responsibilities

• Take systems from a rough idea to production and carry the pager for it.
• Work with customers and teammates to determine what to build.
• Write down decisions and rationale so future operators can reproduce results.

Skills

Production software

Linux

Networking

Distributed systems

Billing/Provisioning

Tools

Temporal

Job description

About Perimeter

The limit on superintelligence (SI) is no longer chips. It's power. New data centers wait years for a grid connection, while the office towers, hotels and hospitals of every major city sit on power they were built for and no longer use. Perimeter Compute is on a mission to put that power to work.

We turn basements and mechanical rooms into GPU clusters, and our software links them into one inference network running inside the cities where SI will be used. Building owners earn from space that would otherwise sit idle. Frontier labs and inference providers get capacity without the years-long wait, a few miles from their users instead of a few states away.

Perimeter is a small, highly leveraged team that has worked every layer of this problem: building GPU infrastructure at Lambda and HPE, engineering commercial buildings at Tishman Speyer and Trane, and routing inference at Subquadratic. The power is already there. Come build what runs on it.

How we work

People make the decisions that matter. Agents do everything else.

• Agents write and review all of our code.

• People own the calls that are hard to undo: architecture, product direction, taste, and the frameworks we use to make those calls.

• Most decisions are two-way doors, so you make the call instead of waiting for one.

If you like writing code yourself, you'll hate it here.

One owner per outcome. You build it, you run it, you grow it.

• Roles here are bigger than usual. You'll do work that's normally split across engineering, product, sales and design.

• You'll work directly with customers to figure out what to build.

• You own the outcome, so you decide how to get there.

If you want a clear ticket and someone else owning the result, this isn't the job.

We keep reinventing how software gets built.

• Code is a means to an end, not the end.

• We question every assumption. "Why?" is the most important question you can ask, and a rule nobody can answer it for gets deleted.

• How we build is code too. Every week, agents find what slowed us down and ship the fix.

If you want a process that stays the same, look elsewhere.

We build for agents as much as for people.

• Agents use our tools, APIs, docs and interfaces too. It isn't done until an agent can use it and recover from its errors without help.

• Every public API is defined once in code, and everything people and agents read about it is generated from that, so nothing drifts.

• Agents don't remember rules, so anything that matters is a check that fails, not a line in a doc.

• Because agents do the work, we can be prescriptive: one way to build things, and every agent follows it.

If docs and error messages feel like someone else's job, we're not a fit.

About the role

Our GPUs live in the basements and mechanical rooms of buildings we don't own, with no one from our team on site day to day. No two buildings are the same. Each one has to be found and vetted, and every GPU in it set up, watched, repaired and billed from somewhere else, without customers ever having to think about any of it.

Most of the systems that make that work don't exist yet. You'll build them: pick up whichever one matters most, work out what it needs to do with the people who'll use it, and take it to production, usually alongside the person who will own it. Once it's running and healthy, you either own it or hand it off and start the next one.

You're measured on whether what you launch is still running well 90 days later.

What you'll do

• Pick up whichever launch matters most. As of November 2026, the list includes:

  • Getting managed Kubernetes from its first cluster to its first paying customer

  • Networking that ties every site together, from the fabric inside a building to the links between them

  • Taking provisioning from our digital twin (a software replica of a whole site) to real hardware, so bringing up a new site is a run of software, not a project

  • The loop that catches a failing GPU, pulls the node, gets the part replaced and retests it, without a person driving each step

  • The software that finds buildings with spare power and works out what each one can support

  • The company's memory: a permanent record of our decisions and conversations, and the knowledge graph our agents will build from it

  • Usage metering, billing and the internal tools the company runs on

• Work out what to build by talking to the people who'll use it, customers and teammates alike

• Take each system from a rough idea to production, and carry the pager for it

• Write down what you decided and why, so whoever runs it next, person or agent, can do it without you

Good fit if you

• Have built and run production software that people depend on, and owned it when it broke, whether that took you two years or ten

• Have figured out what to build without a spec, shipped it and carried the pager for it

• Have worked below the app layer: Linux, networking, hardware or distributed systems

• Have built something where real money or hardware was on the line, like billing, provisioning or fleet operations

• Get real results from coding agents and know where to check their work

• Have handed off a system you built, and it kept running well without you

Nice to have

• Bare metal, networking or GPU infrastructure

• Long-running workflows with Temporal or similar

• Power, cooling or building management systems

• Billing, metering or usage-based pricing

• Forward-deployed or solutions engineering work with customers

• Early-stage startup experience

Location

Fully remote in the US. We aren't able to sponsor visas at this time.

Benefits

• Health, dental and vision insurance

• Unlimited PTO

• A $500 home office stipend

• A top-spec MacBook

• Unlimited tokens

Perimeter Compute is an equal opportunity employer. We don't discriminate based on race, color, religion, sex, pregnancy, sexual orientation, gender identity, national origin, age, disability, genetic information, veteran status or any other legally protected status. If you need an accommodation at any point in our hiring process, email [e-mail].