Mission Delivery Engineer
Posted Oct 21, 2026
The role in short
Embed with DoD and IC customers to prototype, harden, and deploy production AI agents and applications on air-gapped and classified networks.
Location: Remote with travel required to customer sites · Active TS/SCI required · $150K–$250K+ equity
Kamiwaza builds AI software that runs where the mission is: on-prem, at the edge, and on air-gapped and classified networks. We're already delivering for DoD and IC customers, and we're hiring forward-deployed engineers to take AI from first demo to production in the field.
As a Mission Delivery Engineer, you own the whole arc. You run discovery with the people doing the mission, build a working prototype on real data, and harden it into something that runs reliably on their network. Then you hand it off so their team can own it. You're early on a small, fast-growing federal team, so the way you work becomes the way we work.
What you'll do
- Discover the mission. Sit with DoD and IC users to understand their workflows, data, and operating constraints, including DDIL. Turn that into a clear use case and a measurable plan for what success looks like.
- Build fast and show it working. Prototype custom applications on the Kamiwaza platform using real or representative data, covering RAG, agentic workflows, streaming ingestion, and edge inference. Run demos and hands-on workshops for both operators and senior leaders.
- Take it to production. Harden what you built with testing, CI/CD, containers, Kubernetes, and observability, and integrate it with customer identity, data, and workflow systems so it runs reliably in classified and air-gapped environments.
- Get it accredited. Bring a security-first mindset and work with security and accreditation teams to support an RMF/ATO-ready approach.
- Hand it off cleanly. Deliver architecture diagrams, runbooks, deployment guides, and code, and train customer and partner teams until they can run it themselves.
- Shape the product and the win. Help Sales and Capture build technical win strategies and proposals, and bring what you learn in the field back to Product and Engineering.
Your first 180 days
- Days 0–45: Master the platform and build your toolkit, including a portable demo environment that runs in constrained settings and a starter kit for taking prototypes to production.
- Days 46–120: Own one or two customer engagements end to end, and convert at least one into a production deployment or production-ready pilot.
- Days 121–180: Turn what worked into repeatable playbooks, and enable a partner or customer team to deploy and run Kamiwaza on their own.
What you bring
- U.S. citizenship and an active TS/SCI clearance
- 6+ years in customer-facing technical roles supporting U.S. federal customers, such as solutions, sales, forward-deployed, or delivery engineering
- A track record of carrying engagements from discovery through production and handoff
- Strong hands-on coding skills, with Python preferred
- Experience with Docker, Kubernetes, and CI/CD
- The ability to explain technical work in terms of mission impact, to operators and to senior leaders
If you meet most of these but not every one, we'd still like to hear from you.
Nice to have
- Hands-on experience with LLMs, RAG, vector search, agentic workflows, or AI evaluation and guardrails. If you've shipped in secure environments but are newer to GenAI, we'll get you up to speed.
- Deployments in classified, air-gapped, or DDIL environments, and familiarity with RMF/ATO and NIST 800-53
- Integrations with federal data platforms, streaming systems, or identity and access systems
- Prior military service or direct support of operational mission teams
- Infrastructure as code, open-source contributions, or published demos and reference solutions
Why Kamiwaza
- Work that's in use. Our platform runs in secure government environments today, and what you build will reach real operators, not sit in a slide deck.
- Hard, interesting problems. You'll make modern AI work in places most AI can't go, including disconnected, air-gapped, and classified networks.
- Ground floor of a federal team. You'll help define how we deliver, with direct access to leadership and minimal red tape.
- Your clearance is in good hands. We will hold your TS/SCI clearance
Compensation and benefits
- Base salary of $150,000–$250,000+, depending on experience, impact, and location
- Equity in Kamiwaza
- Low-deductible medical plans
- Flexible time off and supportive family leave
- Remote workspace support
How to apply
Apply here. If you'd like to stand out, add a few sentences about a customer problem you solved end to end. Keep it unclassified or sanitized; we know most of your best work can't be shared.
We're an AI company, so if you used AI to put your application together, tell us how. We're genuinely curious.
Note to recruiters and agencies: Kamiwaza does not accept unsolicited resumes. Candidate information sent without a signed agreement becomes Kamiwaza's property, and no placement fee will be paid.
Prep for this interview
5 questions likely to come up at Kamiwaza AI, each matched to a line in this posting.
- 1LLMs, RAG and agents
They wrote: “Hands-on experience with LLMs, RAG, vector search, agentic workflows, or AI evaluation and guardrails. If you've shipped in secure environments but are newer to GenAI, we'll get you up to speed.”
A customer wants a chatbot over their internal documents. How do you build it?
How to answer
Why they ask: RAG is the most common first project. They want the whole path, from messy files to answers people trust.
- Collect and clean the documents; handle permissions per user
- Split them into chunks, embed, and store with source links
- Retrieve, then answer with citations; say “I don't know” when retrieval is weak
- Build a test set of real questions with expected answers before launch
Tip: Spend more time on the data and on testing than on the model.
- 2Travel
They wrote: “Location: Remote with travel required to customer sites · Active TS/SCI required · $150K–$250K+ equity”
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.
- Your past travel or on-site experience
- How you stay productive away from the team
- What travel level works for you, said plainly
Tip: Be honest about what works for you. A mismatch here hurts both sides later.
- 3Discovery and scoping
They wrote: “A track record of carrying engagements from discovery through production and handoff”
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.
- Map the current process: who touches a claim, in what order, with which systems
- Find the slowest or most error-prone step and ask what it costs them
- Agree on one measurable goal (for example time per claim, or error rate)
- 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.
- 4Integrations and APIs
They wrote: “Integrations with federal data platforms, streaming systems, or identity and access systems”
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.
- Find who owns the system and get read access to a test environment
- Watch real traffic or logs to learn the data shapes
- Build a thin adapter with logging around every call
- 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.
- 5Cloud, deployment and security
They wrote: “Get it accredited. Bring a security-first mindset and work with security and accreditation teams to support an RMF/ATO-ready approach.”
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.
- Start from your company's standard answers (SOC 2 report, past reviews)
- Answer clearly; don't oversell
- Bring in your security team for anything you're unsure of
- 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.
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.

