Forward Deployed Engineer
Courses for this role
Foundations
Software fundamentals plus the customer-facing and offline-tooling skills that distinguish FDE work from regular SWE work. The job is part SWE, part solutions architect, part technical diplomat.
Field problems are solved with quick scripts under a clock, not month-long projects.
Anduril Lattice is heavy C++; newer Anduril and DoD-adjacent platforms use Go. Python alone is the SWE archetype, not the FDE one.
Most defense field systems run RHEL/Ubuntu. Knowing it cold — without Google — is non-negotiable.
The hardest skill — translating engineering for operators who do not care about it, in environments where the operator is wearing gloves and the timeline is hostile.
When the customer site has no internet, git bundle / sneakernet / offline mirrors are the only way to ship code.
The closest thing to an FDE textbook that exists — small-team, customer-adjacent, pragmatism over purity.
Build the stack
Integration scripting, container-based deployment, and the legacy-system glue work that defines the role day-to-day. In defense you are rarely greenfield — you are making a 20-year-old database talk to a modern AI platform.
The most common FDE deliverable is a custom pipeline integrating a customer's data into a modern platform.
COBOL, Oracle, MIL-STD-1553, NIEM XML, fixed-width files — the real interfaces FDEs spend most of their time bridging.
Modern defense platforms (Palantir Apollo, Anduril Lattice, BigBear.ai) deploy via containers to the edge. Troubleshooting a failing pod without steady internet is the FDE superpower.
When something does not work on a range, you cannot push a fix and re-run CI. You read logs, you bisect, you fix it on the box.
Every customer site is different. The FDE writes the integrations between platform and whatever was there before.
The reference text for anyone shipping data pipelines that survive in production.
Field experience
Government-cleared work, air-gapped deployment, and the SCIF/hangar protocols that gate access to the highest-leverage work. Phase length is dictated more by the clearance process than by skill acquisition.
Deploying into environments with no internet — offline package mirrors, software-bill-of-materials transfers, hardware tokens. The skill that separates senior FDEs from juniors.
Knowing how to behave inside a SCIF, on a flight line, or at a forward operating base. Different rules than a downtown office.
Half of FDE field problems are not code — satellite link latency, 20% packet loss, a flaky radio, antenna pointing. Recognizing this from telemetry is the senior move.
In practice this is the gatekeeper, not a skill. You can be a brilliant coder but you cannot forward-deploy to many sites until the government grants TS/SCI — a 6–18 month bureaucratic process the candidate cannot speed up.
IL2 is public-ish; IL6 is classified. Knowing which IL the customer's environment requires shapes every architecture decision.
Defense software is export-controlled. FDEs interact with this constantly — every code review, every laptop crossing a border.
Common entry credential for cleared work. Many defense companies cover the exam fee.