# AI-Native Detection and Triage Engineer at Fly.io

Fly.io is hiring an AI-Native Detection and Triage Engineer for a remote role open to applicants in United States. It pays $180k-$225k a year and Level rates it Works on AI ●●●○; you can [apply on Fly.io](https://jobsbylevel.com/go/f7c087f0-3f25-4361-a2f3-433873145522?utm_medium=ai-agent).

AI Level 3, AI centrality 67 out of 100. Remote (Remote).

## Details

- Company: [Fly.io](https://jobsbylevel.com/companies/fly)
- AI level: AI Level 3 (score 67 out of 100)
- Location: Remote (Remote)
- Salary: $180k-$225k
- Posted: November 5, 2026
- Apply: https://jobsbylevel.com/go/f7c087f0-3f25-4361-a2f3-433873145522?utm_medium=ai-agent
- Free CV review for this job: https://jobsbylevel.com/cv-review?job=ai-native-detection-and-triage-engineer-at-fly-1c9ce5

## Prepare for this job

The job page lists 3 likely interview questions for this offer, with a CV checklist: https://jobsbylevel.com/jobs/ai-native-detection-and-triage-engineer-at-fly-1c9ce5

## Description

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. We put a lot of work into the isolation boundary. This role is about everything that tells us whether it is holding: knowing, in near-real-time, when something has crossed it in production, finding the bug in the code before anyone gets the chance, and running every one of those signals to ground. This Role Fly's Head of Security covers application security, trust boundaries, and the compliance program. A vulnerability researcher spends their time breaking our own hypervisor and kernel stack. A Platform Security Engineer, hiring in parallel with this role, will own isolation on the hosts. The seat we are adding will own the signal: from the fleet and from the code, through one triage pipeline, to a fixed root cause. That will be you. Two sources will feed that pipeline. The first will be signal from the running platform: eBPF sensors on every host, the SIEM they land in, and the detections that fire on it. The second will be the code: agents that review every merged PR, dependency and image scanning across our repositories, and a full local replica of the platform where we scan, fuzz, and test the whole stack. Both feeds will land in one triage tool, and you will own what reaches it, how it is enriched and prioritized, and what happens next. AI-native means two things here. You will build with coding agents as a matter of course. And the pipeline itself will be agentic: agents will safely triage, correlate, and enrich findings before a human sees them. You will design and operate those agents and you will be the person who can tell when one of them is wrong. What You'll Be Doing Signal from the fleet. We run eBPF sensors across the hosts, feeding a SIEM. You will own what the sensors watch, their lifecycle across our kernel versions, and their path into the pipeline. You will own detection coverage for the scenarios that matter most on a platform like ours: spotting a compromised host and the lateral movement that follows, noticing control-plane access patterns, operator access to customer machines, secrets access, and abuse of AI workloads and the credentials inside them. Signal from the code. Agents already review every merged PR for security issues; you will own them, their prompts, which repositories they watch, and so forth. You will own dependency, image, and SBOM scanning across the codebase. And you will help build out our local replica of the platform: QEMU/KVM Fly hosts running nested Firecracker, with the real control plane running as machines inside the cluster. You will help build its CI and its fuzzing and testing harness, so that isolation regressions, scanner findings, and new attack surface are properly exercised against a full stack in a sandbox before they reach a customer. The triage pipeline. You will also own one prioritized inbox over SIEM alerts, scan findings, vulnerabilities, failing checks, and inbound disclosures, with the dispatch and closure workflow behind it. You will own what feeds it and the contract each producer writes against. You will build the agents that triage, deduplicate, correlate, and enrich findings before a human deals with them. Running things to ground. A finding is not done when it is filed. You will funnel alerts and scan results to the teams that own the code or the hosts, work with them to a root cause if needed, and see the fix land and the detection or scanner confirm it. Much of this job will be that loop: a dozen owning teams, a steady stream of signal, and one person making sure nothing stalls between "fired" and "fixed." Hunting and incidents. You will

The description is cut here. Read the full offer: https://jobsbylevel.com/jobs/ai-native-detection-and-triage-engineer-at-fly-1c9ce5

Source: https://jobsbylevel.com/jobs/ai-native-detection-and-triage-engineer-at-fly-1c9ce5

## Cite this page

Level. https://jobsbylevel.com/jobs/ai-native-detection-and-triage-engineer-at-fly-1c9ce5.

Get job alerts: https://jobsbylevel.com/newsletter
