Swarm Aero
Swarm Aero2 open roles

Staff Forward Deployed Engineer

$220–300kRemote (US)RemoteSeniorFull-time

Posted 4 days ago

The role in short

Lead technical initiatives and mentor engineers while writing and debugging production C2 and autonomy software for swarming UAVs in field deployments with government customers.

Swarm Aero is redefining air power, building the largest swarming UAV and the most versatile swarming aircraft network in the world. The company is moving quickly to launch the first aircraft designed specifically for swarming, as well as the Command & Control software to mobilize swarms of thousands of heterogeneous autonomous assets and empower human operators to achieve superhuman results.

The team has created and exited multiple startups, negotiated defense deals worth billions of dollars, and designed and built 30+ novel aircraft, with aerospace experience from Scaled Composites, Airbus, Archer Aviation, Blue Origin, and Boom Supersonic.

About the Role

Most software engineers never see their code tested against reality. At Swarm Aero, that's the baseline.

We are looking for a Staff Forward Deployed Engineer to own multiple initiatives across our customer programs and lead the forward deployed engineers working on them. You will work directly with U.S. government and military customers to understand the mission, decide what our C2 and onboard autonomy software can deliver, and set the technical plan to get it into the field. You will make the feasibility calls, keep everyone involved working from the same plan, and make sure your initiatives are ready for the releases that put new capability in operators' hands.

This is a hands-on technical leadership role. You will still write code, debug systems in the field, and be on site when the work goes live.

What You'll Do

  • Own multiple initiatives within a customer program, from early requirements through deployment. Turn mission needs into a technical roadmap for each one, and make the feasibility and tradeoff calls across them.
  • Lead the forward deployed engineers working on your initiatives by setting technical direction, breaking down the work, and clearing blockers.
  • Write and integrate C2 and onboard autonomy software for unmanned air and sea vehicles, and debug it in the field when something breaks.
  • Participate in and lead design reviews for your initiatives before work starts.
  • Run post-incident reviews after field issues, find the root cause, and put fixes in place so the same problem does not happen again.
  • Bring field data and lessons learned back to the core product team.
  • Work with partner teams to align on priorities and timelines, gather their feedback, and run internal testing before every deployment.
  • Plan how your initiatives fit into each contract release alongside core product work, and make sure they are tested and ready before the release ships.
  • Serve as the main technical contact for vehicle and sensor vendors, and lead the integration of their systems with ours.
  • Define success criteria with customers for each event, run the readiness review for your initiatives beforehand, and give the go/no-go recommendation.
  • Mentor forward deployed engineers and help with technical assessments of potential candidates.
  • Support deployments outside normal hours, including on-call response and rotational coverage aligned to mission tempo.
  • Travel domestically and internationally (up to 50%) to test sites and customer locations, and lead the team on site.

This Role Is For You If

  • You have shipped software to the field and want to own a bigger share of the outcome.
  • You like making technical calls under pressure and explaining them to people who need a straight answer.
  • You enjoy helping other engineers grow while staying hands-on yourself.
  • You can turn an ambiguous customer request into a plan a team can execute.

This Role Is NOT

  • A people management role away from the code
  • A program or project management role
  • A pilot position or vehicle operator role
  • Primarily hands-on hardware work (electronics, wiring, mechanical assembly)

Basic Qualifications

  • Bachelor's degree in Computer Science, Software Engineering, or related technical field
  • 7+ years of professional software engineering experience, or equivalent demonstrated ability
  • Experience leading a small team, feature crew, or sub-program through design and delivery
  • Experience building and deploying software for unmanned systems (UAS, USVs, or UUVs), including C2 or onboard autonomy
  • Experience working directly with government or military customers to turn mission needs into technical requirements
  • Experience supporting live exercises, test events, or field deployments
  • Experience shipping work as part of larger releases that combine contributions from several teams
  • Strong proficiency in at least one systems language (Golang, Rust, or C/C++)
  • Solid understanding of networking fundamentals: NAT, DNS/mDNS, UDP/TCP protocols, multicast, and firewall configuration
  • Experience with Linux system administration and shell scripting
  • Excellent communication skills for engaging with U.S. government and military customers, vendors, and internal engineering teams
  • Willingness and ability to travel up to 50% of the time, both domestically and internationally, including to remote or restricted-access locations
  • Must be eligible to obtain and maintain a U.S. Secret security clearance

Preferred Qualifications

  • Active U.S. Secret security clearance or higher
  • Prior defense, intelligence community, or aerospace software experience, especially with the U.S. Navy
  • Experience integrating C2 or autonomy software onto third-party vehicles
  • Familiarity with unmanned systems and C2 interoperability standards (UMAA, MAVLink, STANAG 4586, OMS, UCI, or A-GRA)
  • Background in multi-vehicle C2, track management, sensor fusion, or sensor-to-shooter software
  • Experience with containerization (Docker, Kubernetes) and infrastructure-as-code
  • Experience with robotics middleware (DDS/ROS2, ZeroMQ, gRPC) and Protobuf
  • Comfort operating in non-permissive or resource-constrained environments

ITAR requirement

To conform to U.S. Government export regulations, applicant must be a U.S. citizen, lawful permanent resident of the U.S., protected individual as defined by 8 U.S.C. 1324b(a)(3), or eligible to obtain the required authorizations from the U.S. Department of State.

Swarm Aero is an equal opportunity employer. We value diverse backgrounds and experiences and make employment decisions without regard to race, religion, national origin, gender, sexual orientation, age, veteran status, or disability.

What We Offer

  • Meaningful equity in a high-growth defense technology company
  • Competitive base salary commensurate with experience
  • Medical, dental, vision, and 401k
  • PTO and paid sick leave
  • Monthly wellness stipend
  • Daily catered lunch (office)
  • Paid parental leave
  • Direct impact on a critical national security mission
  • A world-class team of engineers and operators solving genuinely hard problems

Prep for this interview

5 questions likely to come up at Swarm Aero, each matched to a line in this posting.

  1. 1Cloud, deployment and security
    They wrote: “Must be eligible to obtain and maintain a U.S. Secret security clearance”

    The customer's security team sends a 200-question review. How do you handle it?

    How to answer

    Why they ask: Security reviews often block deals. FDEs help get through them.

    1. Start from your company's standard answers (SOC 2 report, past reviews)
    2. Answer clearly; don't oversell
    3. Bring in your security team for anything you're unsure of
    4. Keep the new answers for the next customer

    Tip: Reuse past answers, flag honest gaps, and offer a call for the hard questions.

  2. 2Integrations and APIs
    They wrote: “Serve as the main technical contact for vehicle and sensor vendors, and lead the integration of their systems with ours.”

    Walk me through connecting our product to a customer's internal system that has no documentation.

    How to answer

    Why they ask: This happens weekly in the job. They want a calm, step-by-step method.

    1. Find who owns the system and get read access to a test environment
    2. Watch real traffic or logs to learn the data shapes
    3. Build a thin adapter with logging around every call
    4. Agree on how failures get reported, and who fixes what

    Tip: Talk about finding the owner of the system first. The code is the easy part.

  3. 3Coding
    They wrote: “Define success criteria with customers for each event, run the readiness review for your initiatives beforehand, and give the go/no-go recommendation.”

    Build a small in-memory cache. Then add expiry. Then a size limit.

    How to answer

    Why they ask: Staged exercises show how your code holds up when requirements change mid-interview, like at a customer.

    1. Start with get and set on a dictionary, plus tests
    2. Store an expiry time with each value and check it on read
    3. Track use order and evict the least recently used entry when full
    4. Say what you'd change for many threads or many machines

    Tip: Keep the first version simple and well tested so the next stage is a small change.

  4. 4Ownership and working with customers
    They wrote: “Write and integrate C2 and onboard autonomy software for unmanned air and sea vehicles, and debug it in the field when something breaks.”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

  5. 5Travel
    They wrote: “Travel domestically and internationally (up to 50%) to test sites and customer locations, and lead the team on site.”

    How do you handle being on the road with customers for weeks at a time?

    How to answer

    Why they ask: Many FDE roles involve regular travel. They check you know what you're signing up for.

    1. Your past travel or on-site experience
    2. How you stay productive away from the team
    3. What travel level works for you, said plainly

    Tip: Be honest about what works for you. A mismatch here hurts both sides later.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

More at Swarm Aero

Similar roles at other companies

Swarm Aero

$220–300k · Remote

Apply