Fly.io
Tailor my application

Platform Security Engineer

United StatesFull-timePosted

Role
Software Engineering
Level
Mid
IST hours
No overlap with IST

Apply on Jobspresso (opens in a new tab)

Not listed

Our reading of the listing. No overlap with IST. This is a guess from the text, so check the original post.

Listing check. Checked 22 Nov 2026: no sign it has closed

We opened the apply link and looked for signs that the job had closed. Finding no sign of closure does not confirm that the role is still open or that the employer is hiring.

Why we show this

We work these out from the words of the listing, so they can be wrong. Check the original post before you apply.

India eligibility

Not marked as open to India Inferred by us

The listing puts the role in another country or region, and nothing in it says people in India can apply.

From the location: “United States”

Whether a job is open to India is a separate question from its working hours.

Working hours

No overlap with IST Inferred by us

The listing names a place but no time zone, so we assumed that place’s usual 9-to-5 day.

From the location: “United States”

Overlap counts the hours of a 9-to-5 day in the job’s time zone that fall between 9:00 and 19:00 IST.

Hours that suit IST do not mean the employer hires in India. See India eligibility above.

Pay in rupees

No salary listed Not stated

The listing does not state a salary, so there is no rupee estimate.

Read the original listing ↗

About the role

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 report to the Head of Security, who will set your priorities and review your work, but you will spend most of your day with the Platform team, who own the systems you will be changing. Coordination and communication will be just as important as raw technical skills.

What You’ll Be Doing

Isolation and sandboxing. We run two VMMs, Firecracker and Cloud Hypervisor, with jailers around them. You will own the syscall filtering, the process-level confinement, the network confinement around the jailers, and the violation telemetry that feeds our detection pipeline, across both VMMs and the host services that make up the platform.

Host network isolation. A lot of our fleet’s isolation rests on nftables and friends. You will own what each host is allowed to talk to, by role, and the health checks and killswitches that tell us the rules in force are the ones we intended.

Blast radius and control-plane trust. The second half of the job. You will own the trust model between hosts and the control plane: how a host identifies itself and how its actions are attributed, how host-to-host operations such as machine migration are authorized, which services run on hosts that also run customer workloads, and what credentials live on a host and what each one can reach. You will design this with the Platform and Networking teams, build the host-local pieces yourself, and verify the rest.

The kernel. We build and patch our own host kernel. You will own the patching cadence and its SLA, keep kernel expertise spread across the fleet team rather than concentrated in one person, and own live kernel patching for the fixes that cannot wait for a reboot cycle.

Agent workloads. The platform increasingly runs agents, including a sandbox product for them. You will take the isolation half of that design seat: VMM confinement, worker-side controls, and what the platform can honestly guarantee an agent workload. This may even include compute where we no longer own the metal, and we will need to design for a fleet that spans trust levels.

When it breaks. A suspected guest escape, a host behaving strangely, weird kernel behavior: these need someone who can lead the technical investigation on the host, not just coordinate it. You will be one of the names we call, and you will help strengthen our forensics playbook.

You will want to be comfortable working with coding agents. We lean on them hard, and the honest truth of low-level security work is that an agent will confidently hand you a kernel patch that is subtly wrong. You will need to be the person who catches it.

Who We’re Looking For

  • You’ve shipped non-trivial Linux kernel, KVM or hypervisor, or BPF security work in production.
  • You have production experience with seccomp filters, jailer or sandbox configuration, or VM isolation hardening.
  • You have one anchoring domain (kernel and sandboxing, or host networking) with credible reach into the others. You will ramp across the rest over 6 to 12 months.
  • You’ve run hardware virtualization on hardware you didn’t control: bare-metal cloud instances, nested virtualization, or hosts in a customer’s account. Not required, but definitely nice-to-have.
  • You’ve been the platform-security specialist on a security team before, and you’ve shipped security work in a matrixed org by collaboration rather than authority.
  • You’re comfortable being the technical authority on low-level work without a more senior security engineer above you.
  • You write well asynchronously. Most of Fly happens in Slack threads and written design discussions.

This is not an application-security role. If your background is primarily SAST, code review, or web app pentesting, we already have that lane covered.

Other Important Things to Know

We don’t want to sell you a bill of goods. A few things about this role are genuinely hard:

  • You will be the depth. Nobody in the security function can backstop you on kernel, syscalls, BPF, or network isolation. Your technical sparring partners are our vulnerability researcher and the Platform and Networking teams, and those are relationships you will build.
  • Much of the work lives in systems other teams own. You will change code in the platform and networking repositories, and those teams are busy. Getting things shipped depends on collaboration and clear writing more than on org-chart authority. The reporting line is designed to protect your priorities, not to let you dictate theirs.
  • The scope is real and…

Technologies

The listing doesn’t name specific technologies. Check the original post for requirements.

Match your resume to jobs like this

Details

Salary
Not listed
IST hours
No overlap with IST
Level
Mid
Type
Full-time
Location
United States
Posted
Listed on
Jobspresso

More remote jobs

Browse all remote jobs · More Software Engineering jobs

Applying opens the original listing on Jobspresso.