ConductorAI
ConductorAI

Forward Deployed Software Engineer

$150–220kWashington, DCHybridMidFull-time

Posted Oct 9, 2026

The role in short

Embed with DoD customers to build, deploy, and maintain production AI software and workflows using Python and TypeScript.

Introduction

We value candidates who have significant experience with managing complexity, working independently, and are motivated by hard problems.

What We Offer

  • The ability to have real impact on mission-critical workflows
  • The chance to use state-of-the-art tech to solve novel problems with mission partners
  • The opportunity to define your role through time as we grow
  • Competitive salary and equity upside with annual merit refreshes based on impact

Position Overview

As a Forward Deployed Engineer, you will sit at the intersection of engineering and customer partnership. You will be onsite with customers regularly, building trust, diagnosing needs, and translating user feedback directly into product improvements. You are still fundamentally an engineer: you will write code, debug systems, and help shape the architecture of a platform built to leverage LLMs and modern AI application techniques. But you are equally comfortable in a customer briefing room as you are in a terminal.

This role is for someone who finds it energizing to own the full loop: understand the problem, build the solution, deploy it, and watch it create value for users in real time. You should be comfortable with ambiguity, have a bias for action, and take pride in the quality and reliability of what you ship. You will work on a small, tight-knit team and will be expected to communicate complex technical concepts clearly to users and stakeholders with varying levels of technical fluency.

As an early team member, you will also help shape our culture, processes, and product direction. We expect you to measure your work by impact, not activity.

Location

Washington, DC area. Up to 40% travel domestically and OCONUS.

Key Responsibilities

  • Go onsite to customer environments to configure, optimize, and support ConductorAI software, including customizing workflows for specific customer use cases and troubleshooting the system
  • Write and maintain production-quality code in Python and TypeScript within a small engineering team
  • Work directly with users to gather feedback, understand workflows, and translate insights into actionable product requirements
  • Debug and improve system reliability, performance, and usability based on real-world customer usage
  • Build and deliver technical demonstrations to new and existing customers
  • Collaborate with the product and engineering team to develop new features, with a direct line from customer need to shipped capability
  • Identify opportunities to automate manual processes and improve operational efficiency at customer sites
  • As a core team member, contribute to company strategy, culture, and evolving responsibilities as we grow

Qualifications

  • Active DoD Top Secret/SCI clearance required at time of hire; required due to the classified nature of work performed under US government contracts
  • US citizenship required by applicable federal law and government contract obligations (ITAR/EAR); we are unable to consider green card holders or sponsor visas for this role
  • 2+ years of professional software engineering or forward deployed engineering experience
  • Proficiency in Python and TypeScript
  • Experience working directly with end users or customers in a technical capacity
  • Strong written and verbal communication skills, including the ability to explain technical concepts to non-technical audiences
  • Comfort operating with high autonomy in ambiguous, fast-moving environments
  • Experience with LLMs and modern AI application techniques
  • Ability to travel up to 40% domestically and OCONUS

Desired Qualifications

  • Active TS or TS/SCI clearance
  • Experience in defense, intelligence, or national security environments
  • Experience at an early-stage startup or in fast-moving, ambiguous environments
  • Background in system design or full-stack development
  • Existing relationships with DoD or civil agency stakeholders

Compensation

The base salary range for this role is $150,000-220,000, with the opportunity for meaningful equity commensurate with a Series A stage opportunity. Candidates with an active TS or TS/SCI clearance may be eligible for compensation at the higher end of the range. Starting pay will be based on qualifications, experience, and location. This range reflects base salary only and does not include equity or other compensation components.

ConductorAI is an equal opportunity employer. We do not discriminate on the basis of race, color, religion, sex, national origin, age, disability, veteran status, genetic information, sexual orientation, gender identity, or any other characteristic protected by applicable law.

Prep for this interview

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

  1. 1Coding
    They wrote: “Write and maintain production-quality code in Python and TypeScript within a small engineering team”

    Here's a CSV export from a customer. Write a script that cleans it and loads it into our API.

    How to answer

    Why they ask: Very close to real FDE work. They watch how you handle bad rows and failures.

    1. Read with a proper CSV parser; check the header first
    2. Validate each row and collect errors, not crash on the first one
    3. Send in batches with retries and a clear report at the end
    4. Write one or two quick tests for the parsing

    Tip: Talk through edge cases out loud: encodings, missing fields, duplicates, rate limits.

  2. 2Ownership and working with customers
    They wrote: “Comfort operating with high autonomy in ambiguous, fast-moving environments”

    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.

  3. 3Discovery and scoping
    They wrote: “Work directly with users to gather feedback, understand workflows, and translate insights into actionable product requirements”

    A customer says “we want AI in our claims process.” What do you ask in the first meeting?

    How to answer

    Why they ask: Most FDE work starts this vague. They want to hear you find the real problem before you pick a tool.

    1. Map the current process: who touches a claim, in what order, with which systems
    2. Find the slowest or most error-prone step and ask what it costs them
    3. Agree on one measurable goal (for example time per claim, or error rate)
    4. Ask what data you can access, and who signs off on security

    Tip: Ask about the work, not the technology. Who does it today, how long it takes, what a mistake costs, and how they'd know it got better.

  4. 4LLMs, RAG and agents
    They wrote: “Experience with LLMs and modern AI application techniques”

    How do you know an LLM feature is good enough to ship?

    How to answer

    Why they ask: Evals are what separate a demo from production. Many roles list them by name.

    1. Write 50–200 real examples with expected outcomes, with customer experts
    2. Agree on a pass bar and the errors that are never acceptable
    3. Score automatically where possible; review a sample by hand
    4. Re-run on every prompt or model change, and watch live traffic after launch

    Tip: Describe a test set built with the customer, a pass bar agreed up front, and checks that run on every change.

  5. 5Cloud, deployment and security
    They wrote: “Active DoD Top Secret/SCI clearance required at time of hire; required due to the classified nature of work performed under US government contracts”

    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.

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.

Similar roles at other companies

ConductorAI

$150–220k · Hybrid

Apply