FewerJobs.
All jobs

Platform Security Engineer

Fly.io - Remote

Posted Nov 5, 2026

Benefits

Parental leave
Not verified
Non-birth-parent leave
Not verified
Family-building benefits
  • Fertility benefits: Not verified
  • Adoption assistance: Not verified
  • Surrogacy assistance: Not verified
Mental health support
Not verified
Relocation assistance
Not verified
Childcare support
Not verified
Learning budget
Not verified
Verification
Not verified
Salary
Not verified

Was this benefit information wrong? Tell us.

Role

Role function
Security From the posting source checked Nov 18, 2026
Seniority
Mid From the posting source checked Nov 18, 2026
Work mode
Remote From the posting source checked Nov 18, 2026
In-office days
0 days From the posting source checked Nov 18, 2026

Schedule

Shift type
Not verified
Weekend work
Not verified

Company

Equity
Offered From the posting source checked Nov 18, 2026

Application

Cover letter
Not verified
Assessment
Not verified
Deadline
Not stated

Where they hire

State eligibility is not yet verified.

About this role

Platform Security Engineer Remote About Fly.io We're building a public cloud that runs on our own hardware all over the world. Customers hand us containers; we convert them into micro-VMs under hardware virtualization, each with its own kernel, on thousands of bare-metal hosts we operate ourselves. A growing share of those workloads are AI agents and inference, which means a growing share of the people attacking cloud platforms are interested in us. Isolation is the product. The boundary between one customer's workload and the next, and between any workload and our own control plane, is a stack of things we build and run: the VMMs and their jailers, seccomp filters, host networking rules, the identity each host presents to the rest of the fleet, and the custom kernel underneath all of it. When that boundary holds, nobody notices. That's the job. The Role We have a security team. It covers application security, trust boundaries and auth, vulnerability research against our own hypervisor stack, corporate security, compliance, and disclosure. What it doesn't have is someone who works alongside the platform team hacking on the platform itself: the kernel, the hypervisor jailers, the syscall filters, host network isolation, and the trust relationships between hosts. That's the gap this role closes. The work has two halves, and you will own both: Keep the guest in the VM. Harden the per-workload boundary on every host. Plan for the worst. Limit the blast radius for when the next horrible KVM guest-to-host escape drops. You will

Read the full description at jobs.lever.co. FewerJobs shows a preview and links to the original posting.

Apply at jobs.lever.co

Apply link verified; last checked Nov 20, 2026.

What verified means

Verified means a displayed claim has field-level provenance to a source FewerJobs pulled: a government or employer source, or the original job posting. Posting-sourced facts are employer-stated and are labeled separately from government records.

Related jobs