Vannevar builds AI systems for the Department of War's most consequential missions. We have 125 deployments across every branch and combatant command spanning our core platform and five distinct products. An an example of how we work, when major combat operations started with Iran, we fielded a new product supporting 24/7 operations and 9,000+ users in three months.

How we build is our advantage: we deploy forward with the people who own the mission. Our engineers, product team, and CTO deploy forward to the point of friction, including visiting units in Ukraine. We focus on embedding directly with operational units supporting great power competition with China, combat operations with Iran, and counter-narcotics missions.

About the role

Vannevar is entering its next stage: scaling from early mission wins into an AI-native, non-traditional defense technology prime. Getting there means more than growing headcount — it means building new operating systems for how our people work, establishing processes that repeat reliably across accounts, and rethinking engineering delivery from first principles for this next phase of growth.

Vannevar’s Mission teams work directly with national security customers, pairing small-team focus with a shared technology platform. As an Enterprise Technical Lead, you’ll own technical direction and engineering delivery for a portfolio of accounts (representing $10M–$50M in contract value) — organized around a service branch, combatant command, or emerging new mission area.

You’ll guide work across the full customer lifecycle: discovering mission needs, shaping opportunities, testing concepts, and scaling capabilities into sustained operations. Using Vannevar’s Agent Control Plane — shared infrastructure for deploying AI solutions in national security environments — you and your team will prototype and test capabilities in areas like digital sensing, logistics, supply chain security, and defense health, then assess what’s ready to scale or transition to dedicated product teams.

You’ll start as a hands-on technical leader on new accounts, learning the stack through direct engineering work — making architecture decisions, contributing to implementation, and coaching engineers. As your portfolio grows, you’ll build and lead the team behind it, while staying accountable for architecture and delivery.

What you’ll do

Technical leadership & delivery

Set technical strategy across your portfolio, turning mission priorities into architectures, plans, and deployed capabilities
Decide when to configure existing platform tools, build reusable extensions, or write mission-specific software — and push back on commitments that aren’t securely or sustainably deliverable
Manage engineering capacity and priorities across accounts — so commitments never outrun the people available to deliver them

Customer & opportunity work

Work directly with customers and end users to understand mission needs and constraints — so what you build matches how the mission actually operates, not just how it looks from a requirements document
Master each customer’s network topology, enterprise architecture, and mission applications — so you extend what already works instead of building a parallel silo, and design solutions that can mature into a Program of Record
Shape new opportunities with customer success, BD, legal, and contracting — contributing technical content to ROMs and SOWs
Build and validate prototypes with customers and product teams; guide what’s working toward production, scale, and eventual transition to dedicated product teams

Platform contribution

Feed recurring engineering challenges and reusable patterns into quarterly Platform/Product planning — so the platform evolves from what’s actually breaking in the field, not top-down roadmap guesses
Enable FDEs to build improvements directly into the platform from the field — so fixes ship at the speed problems are found, instead of waiting on a centralized release cycle

Execution & governance

Produce architecture artifacts (system context, component, interface, data-flow, deployment diagrams — UML/SysML where useful) and track work in tools like Jira and Notion — so decisions are traceable and a team can pick up the work without you in the room