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 reviewQuestions interviewers often ask for this role, with sample answers.
One 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 security for a cloud infrastructure, running continuous red-team agent simulations to identify and fix vulnerabilities. You will also build real-time detection and response systems while ensuring security measures do not impede development speed.
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 security for a cloud where customers will share our hardware and agents write all of our code. Attacks now move at machine speed: stolen keys can become a full compromise within hours, so our defense has to move faster.
You'll run agents that attack our own infrastructure around the clock, starting in our digital twin (a software replica of a whole site where we can break things safely), and build detection and response that can contain a rehearsed attack in minutes. You'll start with what we run today, from our laptops and the agents on them to the pipeline they ship through, and grow into customer isolation as we build it. The job is to make the secure way the fast way: security that slows the team down has failed.
You're measured on time to contain, time to a verified fix, how little you slow anyone down, and whether our red-team agents can get from one customer to another.
Run a continuous agent red team against our digital twin, from the BMCs up through our APIs. Find what breaks first and get it fixed before it ships.
Keep up with new attacks the week they land, like poisoned packages and stolen CI tokens, and add each one to what the red team tries
Build the find-and-fix loop: every finding is reproduced, given an owner, verified fixed and turned into a detection we test in the twin
Build real-time detection and response, including for our own agents, with pre-approved containment like revoking credentials or isolating a host. You're on call for it.
Keep the laptops our team and its coding agents work on locked down, and replace long-lived keys with short-lived ones, so a lost laptop or a leaked key doesn't turn into a breach
Set the security bar for what our agents can reach and how they ship code, so a stolen token can't push a release
Get critical issues patched in hours, not weeks, and set how fast GPU driver fixes have to roll out
Set the bar for isolating customers on shared GPUs, so no one has to think about who else is on the hardware, and keep attacking it as we build it
Build security into the paved road, so the secure way is the default and the fast one
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 hands-on offensive or defensive experience across Linux, Kubernetes, containers and cloud
Have built detections and led the response to a real incident
Have locked down identity, secrets, devices or CI/CD at a company that ships fast
Have built or run agent systems and know how to evaluate them
Have automated a security workflow end to end and decided where a person stays in the loop
Building a find-and-fix loop or agent-driven vulnerability discovery, like OpenAI's Defense Factory or Cloudflare's vulnerability harness
Detection as code
Defending agents against prompt injection and tool misuse
GPU multi-tenancy: MIG, vGPU and their isolation limits
Bare-metal and BMC security: Redfish, firmware, Secure Boot
Device management and endpoint security on macOS
SOC 2 or similar audits
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,109+ Jobs in Security Engineer
Answer easy questions
222,109+ 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!”