Business Development Lead - U.S. Government

We need to output HTML fragment with sections: About the role (maybe heading "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to include sections that have real content. We need to parse the posting: It includes "About Nominal" description, then "About The Role" bullet list of responsibilities, then "We’re looking for someone with ..." which are requirements/qualifications, then "Skills That Supercharge Us" which are skills, then "Benefits/Perks" list. We should not repeat job title as heading. No Job ID. Remove boilerplate: EEO, ITAR requirements maybe? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ITAR Requirements might be considered legal? It's about eligibility; maybe we should keep? It says remove legal boilerplate. ITAR is legal requirement; likely remove. Also "All qualified applicants will receive consideration..." is EEO; remove. Also "Learn more about the ITAR here." remove. We need to preserve substantive information: About Nominal description, role responsibilities, qualifications, skills, benefits. We should not create sections for Pay or Schedule if not present. There's no pay or schedule info. So omit those. We need to decide headings: "About the role" maybe corresponds to the bullet list under "About The Role". Could also have "About Nominal" as intro paragraph before heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities...). Likely we should use those exact headings where appropriate. We have content that matches: About the role (the bullet list), Responsibilities (maybe same as About the role?), Requirements, Qualifications, Skills, Benefits. We need to avoid duplicate or thin sections. Let's map: - About the role: could be the paragraph describing role purpose? The posting has "As part of Nominal’s U.S. Government Business Development team, you will drive how we expand across the U.S. Government—owning pipeline creation, customer engagement, and deal execution across key defense accounts. This is a highly strategic, externally-facing role focused on shaping and closing complex opportunities across the U.S. Air Force, U.S. Army, and the broader test enterprise. This role partners closely with Capture Strategy, which owns capture strategy and win positioning, while this role owns customer relationships and deal execution. You will work at the intersection of mission, product, and growth—translating customer needs into enduring programs and positioning Nominal as foundational infrastructure for test and operations." That's a good description. Could be under "About the role". - Responsibilities: the bullet list after "💼 About The Role Apply a strong understanding..." Actually that bullet list seems responsibilities. So we could have Responsibilities heading with that list. - Requirements/Qualifications: The "We’re looking for someone with 5+ years..." etc. Could be Requirements. - Skills: "Skills That Supercharge Us" list. - Benefits: "✨ Benefits/Perks" list. We should not include "About Nominal" as a heading unless we have a section for it; but we could include a brief intro paragraph before any heading. The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid having a paragraph before headings. So we can start with a

containing the About Nominal description. Then

About the role

with a paragraph describing role purpose. Then

Responsibilities

with

• ... from the bullet list. Then

  Requirements

  with
  • ... from the "We’re looking for someone with..." list. Then

    Skills

    with
    • ... from Skills That Supercharge Us. Then

      Benefits

      with
      • ... from Benefits/Perks. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive information: ensure we capture each bullet. Let's extract bullets. From "About The Role" bullet list (the line after the emoji): "Apply a strong understanding of customer priorities, mission environments, and acquisition dynamics to shape and close strategic opportunities by aligning customer mission needs with Nominal’s platform and long-term roadmap Identify, shape, negotiate, and close new market opportunities, aligning account growth with overall business objectives Develop and maintain relationships with key stakeholders across customer organizations, generating buy-in and alignment with end users, program managers, acquisition officials, technical leaders, and industry partners Provide insight into customer priorities, funding dynamics, acquisition pathways, and requirements to inform Nominal’s Federal growth strategy Own the process of qualifying, cultivating, and capturing opportunities in close partnership with growth, mission, legal, and operations teammates Identify and develop strategic partnerships to expand reach and strengthen positioning in key programs Grow early engagements into enduring, impactful programs and set the conditions for Nominal to become foundational digital infrastructure for test data management, analysis, and operations Represent Nominal at customer meetings, industry days, conferences" That's 8 bullets. Now Requirements/Qualifications: The paragraph after the rocket emoji: "We’re looking for someone with 5+ years of experience in business development, growth, capture, program strategy, or related roles supporting or serving U.S. military and civilian organizations, particularly the U.S. Air Force, U.S. Army, and the Test enterprise Deep understanding of U.S. Government/ Defense organizational structures and priorities and experience developing, shaping, or executing complex technical opportunities Excellent communication skills, with the ability to tailor messaging across technical and non-technical audiences Keen awareness of when and how to pull in the right teammates to build targeted demos, perform technical discovery, identify capability gaps, understand integration and deployability options, share compliance and infosec guidance, and more A strong sense of urgency and ownership, with the ability to navigate complex stakeholder environments and drive outcomes in ambiguous settings Experience managing pipelines, forecasting, and consistently hitting growth targets Technical background or degree: Background in computer science, mechanical engineering, or other heavy industry Willing to travel up to 50% This position requires you to currently possess and be able to maintain a U.S. security clearance, in order to meet U.S. regulatory eligibility requirements for the access to classified information associated with this role." We need to decide if some of these are requirements vs qualifications. We can combine into Requirements section. Now Skills: "Skills That Supercharge Us" bullet list: "Experience delivering growth outcomes for defense or dual-use software products and proven success developing and executing go-to-market strategies for emerging defense technologies Familiarity with non-traditional acquisition pathways and commercial product acquisitions Established relationships across relevant U.S. Government stakeholders, prime contractors, and mission partners Background in data systems, data analysis, and/or hardware engineering is a plus Prior U.S. military or government experience is a plus" Now Benefits: "✨ Benefits/Perks" list: "🏥 100% coverage of medical, dental, and vision insurance 🏖️ Unlimited PTO and sick leave 🍽️ Free lunch, snacks, and coffee 🚀 Professional Development Stipend ✈️ Annual company retreat" We need to output HTML fragment only. We should not include the emojis inside the text? Probably keep them as part of the text; they are characters. Could keep but maybe strip? The instruction says preserve ALL substantive information; emojis are part of the posting but not essential. Might keep them but they are not harmful. However they might be considered decorative; but we can keep them. We need to avoid markdown code fences. Let's craft:

        About Nominal Nominal is building the connected test and operations platform powering the world's most advanced hardware systems, from spacecraft and autonomous vehicles to next-generation defense programs. Our platform gives hardware engineering teams a single place to ingest data, analyze performance, automate test execution, and collaborate across every phase of development, so they can move faster without sacrificing safety or precision. We're a fast-moving team that owns problems end-to-end, works across disciplines, and thrives at the intersection of hardware and software. We serve top-tier commercial and defense customers, from autonomy leaders like Anduril and Shield AI to next-generation aerospace teams like Hermeus and REGENT, and performance engineering teams like Pratt Miller Motorsports, alongside mission partners within the U.S. Navy and U.S. Air Force on programs where failure isn’t an option. We’re backed by Sequoia, General Catalyst, Founders Fund, Lux Capital, and Lightspeed. Our team draws from SpaceX, Palantir, Anduril, Applied Intuition, and other leading companies, united by a common mission: giving hardware engineers the tools to build the future with speed, safety, and confidence.

        About the role

        As part of Nominal’s U.S. Government Business Development team, you will drive how we expand across the U.S. Government—owning pipeline creation, customer engagement, and deal execution across key defense accounts. This is a highly strategic, externally-facing role focused on shaping and closing complex opportunities across the U.S. Air Force, U.S. Army, and the broader test enterprise. This role partners closely with Capture Strategy, which owns capture strategy and win positioning, while this role owns customer relationships and deal execution. You will work at the intersection of mission, product, and growth—translating customer needs into enduring programs and positioning Nominal as foundational infrastructure for test and operations.

        Responsibilities

        • Apply a strong understanding of customer priorities, mission environments, and acquisition dynamics to shape and close strategic opportunities by aligning customer mission needs with Nominal’s platform and long-term roadmap
        • Identify, shape, negotiate, and close new market opportunities, aligning account growth with overall business objectives
        • Develop and maintain relationships with key stakeholders across customer organizations, generating buy-in and alignment with end users, program managers, acquisition officials, technical leaders, and industry partners
        • Provide insight into customer priorities, funding dynamics, acquisition pathways, and requirements to inform Nominal’s Federal growth strategy
        • Own the process of qualifying, cultivating, and capturing opportunities in close partnership with growth, mission, legal, and operations teammates
        • Identify and develop strategic partnerships to expand reach and strengthen positioning in key programs
        • Grow early engagements into enduring, impactful programs and set the conditions for Nominal to become foundational digital infrastructure for test data management, analysis, and operations
        • Represent Nominal at customer meetings, industry days, conferences

        Requirements

        • 5+ years of experience in business development, growth, capture, program strategy, or related roles supporting or serving U.S. military and civilian organizations, particularly the U.S. Air Force, U.S. Army, and the Test enterprise
        • Deep understanding of U.S. Government/Defense organizational structures and priorities and experience developing, shaping, or executing complex technical opportunities
        • Excellent communication skills, with the ability to tailor messaging across technical and non-technical audiences
        • Keen awareness of when and how to pull in the right teammates to build targeted demos, perform technical discovery, identify capability gaps, understand integration and deployability options, share compliance and infosec guidance, and more
        • A strong sense of urgency and ownership, with the ability to navigate complex stakeholder environments and drive outcomes in ambiguous settings
        • Experience managing