Defence veteran to FDE: field discipline meets software delivery

Decide your starting track first

Use this table honestly. It is about your actual exposure, not your rank or trade name.

If you are unsure which row you are in, run your resume through the free skill check. It will show which technical skills your record already evidences.

What an FDE actually does that looks familiar

A forward deployed engineer sits with a client, understands a messy real-world workflow, and builds and deploys software — increasingly including AI components — that works in that environment rather than in a demo. The FDE hub explains the role in more detail. Several parts will feel familiar:

• Situation reports and after-action reviews map onto incident write-ups and post-deployment reviews: what happened, what we did, what we change.
• SOPs and checklists map onto runbooks and deployment checklists. Most software teams write these badly; you will not.
• Equipment maintenance logs map onto system logs: timestamps, states, faults, actions taken.
• Briefing up the chain maps onto explaining a technical risk to a client's decision maker in plain language.
• Working at an unfamiliar site with incomplete information is close to the core of the job.

What does not transfer: programming, version control, databases, APIs, cloud deployment and how language models behave. Those are learned from scratch, and that takes months of steady work, not weeks.

A first project built on a maintenance log

Pick something you understand operationally. A small Python tool that reads a synthetic equipment maintenance log, flags overdue servicing and writes a status report is a good first build: it has inputs, rules, edge cases and a user.

import csv
import io
from datetime import date, timedelta

# Synthetic maintenance log. interval_days = required servicing interval.
LOG = """asset_id,asset_type,last_serviced,interval_days,status
GEN-01,generator,2026-07-01,90,operational
GEN-02,generator,2026-05-15,90,operational
VEH-11,vehicle,2026-08-20,60,operational
VEH-12,vehicle,,60,operational
RAD-07,radio set,2026-03-10,180,under repair
"""

def assess(row, today):
    if not row["last_serviced"]:
        return "DATA MISSING"
    if row["status"] != "operational":
        return "NOT IN SERVICE"
    due = date.fromisoformat(row["last_serviced"]) + timedelta(days=int(row["interval_days"]))
    if due < today:
        return f"OVERDUE by {(today - due).days} days"
    if (due - today).days <= 14:
        return f"DUE in {(due - today).days} days"
    return "OK"

def report(text, today):
    return {row["asset_id"]: assess(row, today) for row in csv.DictReader(io.StringIO(text))}

today = date(2026, 9, 27)
for asset, verdict in report(LOG, today).items():
    print(f"{asset:<8} {verdict}")

# Minimal checks: the tool must handle a missing date without crashing
result = report(LOG, today)
assert result["VEH-12"] == "DATA MISSING"
assert result["GEN-02"].startswith("OVERDUE")
assert result["RAD-07"] == "NOT IN SERVICE"
print("checks passed")

What makes this an FDE project rather than a coding exercise is the work around it. Write a one-page runbook: who runs it, where the input comes from, what happens when a date is missing, and who acts on an "overdue" line. Then extend it step by step — move the log into SQLite, expose the report through a small web API, and later add a language model that drafts the daily summary, with a rule that the model may only restate facts the tool computed. Each extension should come with a note on what could fail.

How to describe the transition

Avoid military jargon and avoid overstating technical depth. A version written for a veteran from a signals or technical trade:

"I served fifteen years, most of it maintaining communication equipment at field locations where the fault had to be found with what we had on hand. I've spent the last year learning Python, SQL and deployment basics, and my first project is a maintenance-status tool built on a synthetic log, with a runbook for the person who operates it. Forward deployed engineering appeals to me because it combines the two things I'm good at — working in unfamiliar conditions and following through until the system actually works for the people using it."

Keep one thing in proportion

Service discipline is a real advantage, but it does not substitute for technical evidence. Employers will want to see code you wrote, a repository with a sensible history and a project you can explain line by line. Plan for that before you plan the job search.

The FDE for Freshers programme starts from software foundations and assumes no prior coding, which suits the first two rows of the table above; if you are in the last row, compare it with the professional track first.