Please mention DailyRemote when applying
See how much of this job your resume covers, and what’s missing.
Want a recruiter to go through it line by line?
Get professional reviewOne click makes a copy of your resume for this role, scores it against the posting, and proposes edits line by line. Your default resume is never changed.
Upload your resume and we draft a letter for this exact role, tailored to what it asks for.
You will own the design system in code, creating components and rules that enable AI agents to build consistent product interfaces. You will also design and refine user interfaces for both human users and AI agents across marketing sites, internal tools, and customer-facing consoles.
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.
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.
You'll own our design system, and most of the builders using it are agents. Agents write every interface we ship, so the system has to live where they can use it: the components, tokens, rules and skills they load before they build a screen, and the checks that catch drift. The goal is that everything we ship feels like one product, whoever or whatever built it.
You'll prove the system on real launches, designing and building each new product's interface alongside the engineer launching it and the person who will own it, then folding what you learn back in. You'll also design for the agents on the other side: the ones acting for our customers, reading our API responses, CLI output, docs and errors.
You're measured on how much of what agents build passes review without a design fix, and whether people and agents can do what they came to do without help.
Own the design system in code: the components, tokens and rules every interface is built from
Write the design skills our agents load before they build a screen, and test them on real tasks: does what an agent builds look and work like the rest of the product?
Turn the rules that matter into checks, like the one that already fails a raw color, so drift gets caught before review
Prove it on real launches. As of November 2026 that's our marketing site and the internal tools the company runs on; next is the console customers will use to rent GPUs.
Take a rough UI and keep working it until it actually doesn't suck, down to the states demos skip: empty, loading, failed, out of capacity, a GPU going bad mid-job
Make dense data easy to read, from GPU health to a bill a customer can check line by line
Design for the agents acting for our customers as carefully as for the people: the API responses, CLI output, docs and error messages they read, so an agent can do the same job a person does in the console
Watch people use what you ship and read agent transcripts the same way, then fold whatever trips them up back into the system
Have designed and shipped software products that people actually use, whether that took you two years or ten
Have built or run a design system in code that other teams shipped on
Have written rules, prompts or skills that got agents to build UI that matched a design system, and can show where it broke
Read React, TypeScript and CSS well enough to see where an agent cut corners
Have made a technical, data-heavy product easier to use without taking control away from experts
Can walk us through work you shipped: what you decided, what you built and what you changed after watching people use it
Building with HeroUI, Tailwind and React Aria
Designing products where people work alongside agents: handing off a task, seeing what an agent did and stepping in
Designing for agents as users: the tool descriptions, CLIs, APIs and docs agents read
Design tokens and theming that span several products
Designing cloud consoles, developer tools, observability or billing products
Data visualization for metrics and time series
Hands-on time with GPUs, inference APIs or ML tooling
Fully remote in the US. We aren't able to sponsor visas at this time.
Health, dental and vision insurance
Unlimited PTO
A $500 home office stipend
A top-spec MacBook
Unlimited tokens
Don't meet every bullet? Apply anyway. We care more about what you've built and how you think than about checking every box.
Please write your answers to the application questions yourself, without AI. After you apply, we'll tell you how to use AI in each interview round.
We accept applications for this role on an ongoing basis.
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 careers@perimetercompute.com.
Stop the endless job search. Our AI finds and applies to the best jobs for you.
Featuring 222,035+ Jobs in Software Development
Answer easy questions
222,035+ jobs across 15+ categories
Get your best job matches
Only hand-screened, legit jobs
Find a remote job faster
No ads, scams, or junk
“I was the first applicant for a remote marketing position that got listed on the company website the same day I applied. Had an interview within 48 hours!”