Mission Lead - SOF (Clearance Required)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We have salary range: $150,000-$170,000 + equity + 401K match. That's pay info. Should we include a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range, equity, 401K match. So we can include a Pay section. Benefits section also present: health, dental, vision, 100% remote first culture, WeWork access, unlimited PTO, lifestyle stipends, salary top-up during military reserve duty, fully paid parental leave, child and pet care reimbursement during travel. So we can include Benefits.
Schedule? Not mentioned explicitly; maybe not include Schedule.
Qualifications? Could combine Requirements and Qualifications? The posting has "What we're looking for" which is requirements. Could treat that as Requirements. Could also have Skills? Not separate.
We need to avoid duplication: The posting repeats "This is a customer-facing role required to be based on the East Coast." etc. We'll include that info in a short paragraph maybe under About the role or a meta paragraph.
We must not include boilerplate like EEO, scam warning, equal opportunity, etc. Also remove duplicated lines.
We need to preserve all substantive information: mission description, about the role, responsibilities list, requirements list, benefits, pay.
Let's extract:
Company intro: 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 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: Mission Leads are customer-facing owners of mission outcomes. You will lead engagements with government stakeholders to identify high-value mission problems, shape pilots and deployments, and turn demonstrated mission value into durable, funded programs. This role blends mission credibility with strong execution and technical intuition. You will operate with high autonomy in ambiguous environments, translate mission needs into clear technical narratives, and coordinate across functional teams (Product, Engineering, Mission, Security, and Operations) to deliver and scale. This is a customer-facing role required to be based on the East Coast (preferably Washington D.C.). Candidates should have experience in the SOF community or PSYOPs/IO community, and work will require time in secure or classified environments and frequent travel. U.S. Persons status with at least a current Top Secret US DoD or IC clearance is required. This is a customer-facing role required to be based on the East Coast. Work will require time in secure or classified environments and periodic travel.
What you'll do (Responsibilities):
- Lead mission engagements. Build trusted relationships with operational, technical, and leadership stakeholders to understand mission needs, constraints, and success criteria.
- Translate mission problems into plans. Turn mission needs into clear problem statements, requirements, milestones, and measurable outcomes.
- Shape pilots and pathways to scale. Define objectives, timelines, and adoption plans that convert early wins into sustained programs.
- Communicate the “why” and the “how.” Create crisp technical narratives that map our agent-based capabilities to mission requirements and operational constraints.
- Run the operating cadence. Lead weekly customer syncs, internal standups, executive updates/QBRs, action-item tracking, and risk reviews, as applicable.
- Coordinate cross-functional delivery. Partner closely with Product and Engineering to ensure mission context is reflected in scope, tradeoffs, and delivery plans.
- Navigate program realities. Help stakeholders work through requirements development, budgeting cycles, contracting pathways, and coordination across organizations.
- Enable adoption. Coordinate onboarding, training, and customer success so the customer can use and sustain the capability.
- Maintain durable account knowledge. Keep high-signal documentation in Notion: stakeholders, org charts, use cases, timelines, deliverables, decisions, and lessons learned.
- Support expansion. Identify adjacent use cases and partner with Account teams where applicable.
What we're looking for (Requirements):
- 6+ years owning outcomes in complex customer environments (preferably in the SOF or PSYOPs/IO community)
- Demonstrated ability to lead cross-functionally without consistent guidance
- Strong written and verbal communication; able to synthesize ambiguity into clear plans and execution
- Ability to scope and articulate a solution credibly: connect mission problems to software capabilities and measurable outcomes
- Sufficient technical fluency to partner effectively with Product and Engineering and translate complex concepts into mission-relevant narratives
- Strong operational skills: planning, prioritization, stakeholder management, and follow-through
Nice to have (could be optional but we could include as part of Requirements or separate Skills? The instruction says prefer few substantive sections over many thin ones. Could combine Nice to have into Requirements or maybe a Skills section. But we have to preserve all substantive information. We could include a "Nice to have" subsection under Requirements, but that would be a list inside the same section. However we need to use
- for any list. Could have a single list that includes both required and nice-to-have? Might be confusing. Better to have a Requirements section for required, and a Skills section for nice-to-have? The instruction says use headings like Skills, Benefits, Pay, Schedule. So we could have a Skills section for nice-to-have. That seems appropriate.
Thus sections: About the role (maybe as a paragraph), Responsibilities, Requirements, Skills (nice-to-have), Benefits, Pay.
We also need to include location/clearance etc. That could be part of About the role paragraph or a separate short paragraph. Since we already have About the role heading, we can put the prose there.
We must not repeat the job title as heading. We don't have job title given explicitly; it's "Mission Lead". We'll not add heading for that.
We must not include duplicated lines: The posting repeats "This is a customer-facing role required to be based on the East Coast." etc. We'll include once.
We must remove boilerplate: EEO, scam warning, equal opportunity, etc. Also remove "IMPORTANT NOTICE" etc.
Now craft HTML.
We'll output:
About the role
Vannevar builds AI systems for the Department of War's most consequential missions, with 125 deployments across every branch and combatant command spanning its core platform and five distinct products. For example, when major combat operations started with Iran, the company fielded a new product supporting 24/7 operations and 9,000+ users in three months. The team deploys forward with mission owners—engineers, product, and CTO—to the point of friction, including visits to units in Ukraine, focusing on embedding with operational units supporting great‑power competition with China, combat operations with Iran, and counter‑narcotics missions. As a Mission Lead, you will be a customer‑facing owner of mission outcomes, leading engagements with government stakeholders to identify high‑value mission problems, shape pilots and deployments, and turn demonstrated mission value into durable, funded programs. This role blends mission credibility with strong execution and technical intuition, operating with high autonomy in ambiguous environments, translating mission needs into clear technical narratives, and coordinating across Product, Engineering, Mission, Security, and Operations to deliver and scale. The position is based on the East Coast (preferably Washington, D.C.), requires experience in the SOF or PSYOPs/IO community, entails time in secure or classified environments and periodic travel, and mandates U.S. Persons status with a current Top Secret US DoD or IC clearance.
Responsibilities
- Lead mission engagements. Build trusted relationships with operational, technical, and leadership stakeholders to understand mission needs, constraints, and success criteria.
- Translate mission problems into plans. Turn mission needs into clear problem statements, requirements, milestones, and measurable outcomes.
- Shape pilots and pathways to scale. Define objectives, timelines, and adoption plans that convert early wins into sustained programs.
- Communicate the “why” and the “how.” Create crisp technical narratives that map our agent‑based capabilities to mission requirements and operational constraints.
- Run the operating cadence. Lead weekly customer syncs, internal standups, executive updates/QBRs, action‑item tracking, and risk reviews, as applicable.
- Coordinate cross‑functional delivery. Partner closely with Product and Engineering to ensure mission context is reflected in scope, tradeoffs, and delivery plans.
- Navigate program realities. Help stakeholders work through requirements development, budgeting cycles, contracting pathways, and coordination across organizations.
- Enable adoption. Coordinate onboarding, training, and customer success so the customer can use and sustain the capability.
- Maintain durable account knowledge. Keep high‑signal documentation in Notion: stakeholders, org charts, use cases, timelines, deliverables, decisions, and lessons learned.
- Support expansion. Identify adjacent use cases and partner with Account teams where applicable.
Requirements
- 6+ years owning outcomes in complex customer environments (preferably in the SOF or PSYOPs/IO community)
- Demonstrated ability to lead cross‑functionally without consistent guidance
- Strong written and verbal communication; able to synthesize ambiguity into clear plans and execution
- Ability to scope and articulate a solution credibly: connect mission problems to software capabilities and measurable outcomes
- Sufficient technical fluency to partner effectively with Product and Engineering and translate complex concepts into mission‑relevant narratives
- Strong operational skills: planning, prioritization, stakeholder management, and follow‑through
Skills
- Experience with deployments or fielding in secure/regulated environments (e.g., ATO/IL environments, classified workflows, compliance constraints)
- Experience navigating within programs (requirements, budgets, authorities, timelines, contracting pathways)
- Deep expertise in a specific mission or technical domain (e.g., cyber, information warfare, ISR, networks, operations, warfare systems/command and control)
- Experience running executive‑level customer updates (QBRs, steering committees)
Benefits
- Health, dental, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We have salary range: $150,000-$170,000 + equity + 401K match. That's pay info. Should we include a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state salary range, equity, 401K match. So we can include a Pay section. Benefits section also present: health, dental, vision, 100% remote first culture, WeWork access, unlimited PTO, lifestyle stipends, salary top-up during military reserve duty, fully paid parental leave, child and pet care reimbursement during travel. So we can include Benefits. Schedule? Not mentioned explicitly; maybe not include Schedule. Qualifications? Could combine Requirements and Qualifications? The posting has "What we're looking for" which is requirements. Could treat that as Requirements. Could also have Skills? Not separate. We need to avoid duplication: The posting repeats "This is a customer-facing role required to be based on the East Coast." etc. We'll include that info in a short paragraph maybe under About the role or a meta paragraph. We must not include boilerplate like EEO, scam warning, equal opportunity, etc. Also remove duplicated lines. We need to preserve all substantive information: mission description, about the role, responsibilities list, requirements list, benefits, pay. Let's extract: Company intro: 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 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: Mission Leads are customer-facing owners of mission outcomes. You will lead engagements with government stakeholders to identify high-value mission problems, shape pilots and deployments, and turn demonstrated mission value into durable, funded programs. This role blends mission credibility with strong execution and technical intuition. You will operate with high autonomy in ambiguous environments, translate mission needs into clear technical narratives, and coordinate across functional teams (Product, Engineering, Mission, Security, and Operations) to deliver and scale. This is a customer-facing role required to be based on the East Coast (preferably Washington D.C.). Candidates should have experience in the SOF community or PSYOPs/IO community, and work will require time in secure or classified environments and frequent travel. U.S. Persons status with at least a current Top Secret US DoD or IC clearance is required. This is a customer-facing role required to be based on the East Coast. Work will require time in secure or classified environments and periodic travel. What you'll do (Responsibilities): - Lead mission engagements. Build trusted relationships with operational, technical, and leadership stakeholders to understand mission needs, constraints, and success criteria. - Translate mission problems into plans. Turn mission needs into clear problem statements, requirements, milestones, and measurable outcomes. - Shape pilots and pathways to scale. Define objectives, timelines, and adoption plans that convert early wins into sustained programs. - Communicate the “why” and the “how.” Create crisp technical narratives that map our agent-based capabilities to mission requirements and operational constraints. - Run the operating cadence. Lead weekly customer syncs, internal standups, executive updates/QBRs, action-item tracking, and risk reviews, as applicable. - Coordinate cross-functional delivery. Partner closely with Product and Engineering to ensure mission context is reflected in scope, tradeoffs, and delivery plans. - Navigate program realities. Help stakeholders work through requirements development, budgeting cycles, contracting pathways, and coordination across organizations. - Enable adoption. Coordinate onboarding, training, and customer success so the customer can use and sustain the capability. - Maintain durable account knowledge. Keep high-signal documentation in Notion: stakeholders, org charts, use cases, timelines, deliverables, decisions, and lessons learned. - Support expansion. Identify adjacent use cases and partner with Account teams where applicable. What we're looking for (Requirements): - 6+ years owning outcomes in complex customer environments (preferably in the SOF or PSYOPs/IO community) - Demonstrated ability to lead cross-functionally without consistent guidance - Strong written and verbal communication; able to synthesize ambiguity into clear plans and execution - Ability to scope and articulate a solution credibly: connect mission problems to software capabilities and measurable outcomes - Sufficient technical fluency to partner effectively with Product and Engineering and translate complex concepts into mission-relevant narratives - Strong operational skills: planning, prioritization, stakeholder management, and follow-through Nice to have (could be optional but we could include as part of Requirements or separate Skills? The instruction says prefer few substantive sections over many thin ones. Could combine Nice to have into Requirements or maybe a Skills section. But we have to preserve all substantive information. We could include a "Nice to have" subsection under Requirements, but that would be a list inside the same section. However we need to use
- for any list. Could have a single list that includes both required and nice-to-have? Might be confusing. Better to have a Requirements section for required, and a Skills section for nice-to-have? The instruction says use headings like Skills, Benefits, Pay, Schedule. So we could have a Skills section for nice-to-have. That seems appropriate.
Thus sections: About the role (maybe as a paragraph), Responsibilities, Requirements, Skills (nice-to-have), Benefits, Pay.
We also need to include location/clearance etc. That could be part of About the role paragraph or a separate short paragraph. Since we already have About the role heading, we can put the prose there.
We must not repeat the job title as heading. We don't have job title given explicitly; it's "Mission Lead". We'll not add heading for that.
We must not include duplicated lines: The posting repeats "This is a customer-facing role required to be based on the East Coast." etc. We'll include once.
We must remove boilerplate: EEO, scam warning, equal opportunity, etc. Also remove "IMPORTANT NOTICE" etc.
Now craft HTML.
We'll output:
About the role
Vannevar builds AI systems for the Department of War's most consequential missions, with 125 deployments across every branch and combatant command spanning its core platform and five distinct products. For example, when major combat operations started with Iran, the company fielded a new product supporting 24/7 operations and 9,000+ users in three months. The team deploys forward with mission owners—engineers, product, and CTO—to the point of friction, including visits to units in Ukraine, focusing on embedding with operational units supporting great‑power competition with China, combat operations with Iran, and counter‑narcotics missions. As a Mission Lead, you will be a customer‑facing owner of mission outcomes, leading engagements with government stakeholders to identify high‑value mission problems, shape pilots and deployments, and turn demonstrated mission value into durable, funded programs. This role blends mission credibility with strong execution and technical intuition, operating with high autonomy in ambiguous environments, translating mission needs into clear technical narratives, and coordinating across Product, Engineering, Mission, Security, and Operations to deliver and scale. The position is based on the East Coast (preferably Washington, D.C.), requires experience in the SOF or PSYOPs/IO community, entails time in secure or classified environments and periodic travel, and mandates U.S. Persons status with a current Top Secret US DoD or IC clearance.
Responsibilities
- Lead mission engagements. Build trusted relationships with operational, technical, and leadership stakeholders to understand mission needs, constraints, and success criteria.
- Translate mission problems into plans. Turn mission needs into clear problem statements, requirements, milestones, and measurable outcomes.
- Shape pilots and pathways to scale. Define objectives, timelines, and adoption plans that convert early wins into sustained programs.
- Communicate the “why” and the “how.” Create crisp technical narratives that map our agent‑based capabilities to mission requirements and operational constraints.
- Run the operating cadence. Lead weekly customer syncs, internal standups, executive updates/QBRs, action‑item tracking, and risk reviews, as applicable.
- Coordinate cross‑functional delivery. Partner closely with Product and Engineering to ensure mission context is reflected in scope, tradeoffs, and delivery plans.
- Navigate program realities. Help stakeholders work through requirements development, budgeting cycles, contracting pathways, and coordination across organizations.
- Enable adoption. Coordinate onboarding, training, and customer success so the customer can use and sustain the capability.
- Maintain durable account knowledge. Keep high‑signal documentation in Notion: stakeholders, org charts, use cases, timelines, deliverables, decisions, and lessons learned.
- Support expansion. Identify adjacent use cases and partner with Account teams where applicable.
Requirements
- 6+ years owning outcomes in complex customer environments (preferably in the SOF or PSYOPs/IO community)
- Demonstrated ability to lead cross‑functionally without consistent guidance
- Strong written and verbal communication; able to synthesize ambiguity into clear plans and execution
- Ability to scope and articulate a solution credibly: connect mission problems to software capabilities and measurable outcomes
- Sufficient technical fluency to partner effectively with Product and Engineering and translate complex concepts into mission‑relevant narratives
- Strong operational skills: planning, prioritization, stakeholder management, and follow‑through
Skills
- Experience with deployments or fielding in secure/regulated environments (e.g., ATO/IL environments, classified workflows, compliance constraints)
- Experience navigating within programs (requirements, budgets, authorities, timelines, contracting pathways)
- Deep expertise in a specific mission or technical domain (e.g., cyber, information warfare, ISR, networks, operations, warfare systems/command and control)
- Experience running executive‑level customer updates (QBRs, steering committees)
Benefits
- Health, dental, and