Platform Engineer

Examples of key problems the team is working on

• You're securing the frontier of AI. The model weights training on our infrastructure are the most valuable and most targeted artifacts in technology, and we're standing up the compute to hold them faster than anyone ever has. A breach isn't a leak, it's the frontier walking out the door.

• Build the entire security program from scratch. Most leaders inherit someone else's system and spend a career patching it. Here you own it end to end, bare metal to boardroom, as we scale across continents.

• The industry's playbook was written for one building at a time. Vendor-managed appliances, manual process, and standards that assume a security team walks the floor. None of that survives contact with what we're building, so we build what should exist rather than buying what does.

• Your threat surface is measured in gigawatts. The customers running on our infrastructure are building the most consequential technology in human history, and being responsible for the physical and logical security of that work makes everything else feel small.

Role Scope

• Build the infrastructure as code that stands up a site's entire security platform, so bringing on a campus is a pipeline run rather than a project.

• Own CI/CD and the release path for the security stack, so every change reaches production tested, versioned, and reversible.

• Automate the remediation the team would otherwise do by hand, and hold the line that anything done twice becomes code.

• Build the package and patch pipeline that keeps a growing fleet current without a person touching a single host.

• Get the automation in place ahead of the platform it serves, so on-call stays something a small team can carry as campuses multiply.

What We're Looking For

The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would.

• You've built infrastructure as code that other people deploy from, and the systems that exist because your pipeline created them outnumber the ones someone built by following a runbook.

• You've automated yourself out of work you used to do by hand, and you can name what the team stopped doing as a result.

• You've owned CI/CD for infrastructure rather than applications, including how a bad change gets caught and rolled back.

• You've automated Windows fleets, where the tooling is thinner and the ecosystem less forgiving than it is on Linux.

• You've kept an on-call rotation survivable by removing causes rather than by writing more runbooks.

• You write production code and you review other people's.

• You've built tooling for people who aren't engineers, and they actually use it instead of working around it.

• Bonus: Infrastructure as code (Terraform, Ansible, PowerShell DSC). CI/CD for infrastructure (GitHub Actions, GitLab CI). Windows package and patch automation (Chocolatey, WSUS, Intune). Observability and alerting (Prometheus, Grafana). Physical security or building systems platforms (Genetec Security Center, access control, IoT device fleets).

We are committed to pay equity and transparency.

Fluidstack is an Equal Employment Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, national origin, sexual orientation, gender identity, disability and protected veterans’ status, or any other characteristic protected by law. Fluidstack will consider for employment qualified applicants with arrest and conviction records pursuant to applicable law.

Applicant Privacy Notice
AI Screening Notice
Ashby Bias Audit

You will receive a confirmation email once your application has successfully been accepted. If there is an error with your submission and you did not receive a confirmation email, please email [email removed] with your resume/CV, the role you've applied for, and the date you submitted your application-- someone from our recruiting team will be in touch.