Account Executive - Defense

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Code Metal" description, then "What You'll Do", "What We're Looking For", "Benefits". Also maybe "Pay" but they mention "Pay depends on experience, but we strive to be at the upper end of the salary range". That's vague; they say "Pay depends on experience, but we strive to be at the upper end of the salary range". That's not a specific number, but it's still a statement about pay. According to rules: 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. The phrase "Pay depends on experience, but we strive to be at the upper end of the salary range" is somewhat vague but still states something about pay. However it's not a specific range; it's like "depends on experience". The rule says avoid filler like "commensurate with experience". That is similar. So we should not create a Pay section because it's not specific. Benefits: they list benefits: health care plan, 401k, PTO, flexible hybrid/remote, relocation assistance. That's specific enough. So include Benefits section. Schedule: not mentioned. So no Schedule. We need headings: About the role? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we should use appropriate headings based on content. The posting includes: "About Code Metal" (company overview). Then "What You'll Do" (responsibilities). Then "What We're Looking For" (requirements/qualifications). Then "Benefits". Also maybe "About the role" could be the company overview? But they said do NOT repeat the job title as a heading (the page already shows it). So we can have sections: About the company? But they gave example "About the role". However we can use "About the role" for the description of the role? The posting includes "What You'll Do" which is responsibilities. Could also have "About the role" summarizing the role. But we must not invent filler. We have substantive content: the initial paragraph about Code Metal and the role description (ownership of portfolio, reporting to Director of Defense Growth, etc). That could be under "About the role". Then responsibilities under "What You'll Do" -> maybe "Responsibilities". Then requirements under "What We're Looking For" -> maybe "Requirements" or "Qualifications". Then benefits. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can reorganize into sections. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is EEO statement, US Citizenship may be required, San Francisco Fair Chance Ordinance. Those are boilerplate; remove them. Also "Wage Transparency - The salary range for this role is not a guarantee..." is also boilerplate? It's about pay but it's a disclaimer; maybe we should remove because it's not substantive content about pay. The rule says remove EEO/equal-opportunity/scam-warning boilerplate. The wage transparency is similar; we can remove. Also "Learn more at codemetal.ai." is part of About Code Metal; keep. We need to keep all substantive info: company description, mission, customers, founding, funding, sales focus, team description, role specifics: ownership of portfolio, reporting to Director of Defense Growth, help shape sales motion, etc. Then responsibilities: own the deal, build the map, earn expansion, sell to outcome, structure funding path, partner effectively (list of partners), maintain forecast. Then What We're Looking For: values, trust (5+ years selling into defense primes, trusted relationships, fluent in complex org dynamics, forecast holds up, need active US security clearance or eligibility), passion, humility, curiosity, nice to have (active relationships inside defense primes, familiarity with embedded systems, safety-critical software, code modernization, developer tooling, CRM discipline, experience using tools for market/account research). Then Benefits: list. We must not include Pay section. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to output only HTML fragment, no /, no markdown. Let's craft. First section: About the role (or About the company?). The initial paragraph about Code Metal is more about company. Could be "About the role" but maybe better "About the role" includes description of role and company context. We'll put that as

  About the role

  then

  with the company description and role overview. But we need to ensure we don't duplicate content. Let's extract the prose: "About Code Metal Code Metal is the leader in automated software engineering you can trust. As AI writes more of the world's code, the bottleneck in software has shifted from writing code to verifying it works, and AI cannot verify its own work with certainty. Code Metal takes a fundamentally different approach: constrain AI to what it does reliably, verify every step independently of the model using formal methods, and keep engineers in the loop on the decisions that matter. The result isn't code that probably works — it's code that is provably correct, with auditable proof. Customers including the U.S. Air Force, L3Harris, RTX, and Toshiba use Code Metal to modernize legacy code, optimize performance on real hardware, and move prototypes to production, fast. Founded in 2023 with offices in Boston and San Francisco, Code Metal is funded by Accel, Salesforce Ventures, B Capital, Smith Point Capital, J2 Ventures, Shield Capital, Overmatch, RTX, and others. Learn more at codemetal.ai. We sell into the hardest requirements environment there is: primarily the major U.S. defense primes, alongside the venture-backed companies reshaping the industry, on programs where the software cannot be wrong. We are a small, fast-moving team that owns problems end to end, and our work in defense today is building the platform that regulated industries everywhere will run on tomorrow. You will take ownership of a portfolio of accounts and their existing pipeline, reporting to the Director of Defense Growth, and you will help shape how Code Metal sells as the motion takes form. The playbook is being written now, and you will help write it." That's a big paragraph. We'll keep as

  . Then responsibilities: "What You'll Do:" followed by bullet-like sentences. We'll convert each sentence into

• . Need to preserve all details. Let's list responsibilities: - Own the deal: run the full motion from first conversation through signature: proof of value, paid integration, production. You are accountable for new business, revenue, and expansion across your accounts, and you carry each deal through internal review and approval to get it done. - Build the map: Defense primes are collections of business units and programs, each may have its own budget, priorities, and capture teams within a single account. Learn who owns which problems and how work gets funded, and position Code Metal to be brought into the pursuits our customers are already chasing. - Earn the expansion: start where a first mover is willing to move, deliver, and let trust compound. The relationships you build are what turn a first engagement into a lasting presence in the account. - Sell to an outcome: Learn what each program is being held to, whether that is schedule, cost, performance, or risk, and sell to that outcome. Then bring the engineers, program leadership, the security and compliance gatekeepers, and the budget owner to the same yes, knowing each of them needs a different case. - Structure the funding path: deals here often mix structures; an IRAD-funded proof of value converting into program subcontract dollars for production, for example. The right route depends on the account, and you build it. - Partner effectively: the team you need, from solutions engineering to delivery to capture, are shared across efforts. You’ll primarily work hand in hand with: - Engagement Manager who owns the delivery relationship and surface expansion signal from inside it. - Team of Solutions Architects, Solutions Engineers and Forward Deployed Engineers that support pre-sales through delivery, ensuring the solution is delivered with the needed customization and configuration for the customer’s environment. - An internally-focused Technical Program Manager who owns the delivery plan and execution. - Maintain the forecast: manage a long-lead pipeline against goals with disciplined, accurate forecasting. We need to ensure we keep the sub-bullets under Partner effectively as nested list? The rule: use
  • for any list of duties/requirements/benefits. For nested lists we can have
    • ...
      • ... etc. That's fine. Now requirements: "What We're Looking For:" includes values and details. We'll parse: Values: Trust, Passion, Humility, Curiosity. Under Trust: "defense runs on it. 5+ years selling into, or capturing business within, U.S. defense primes, with the trusted, enduring relationships to show for it. You’re fluent in complex organizational dynamics and structures, and your forecast holds up because your judgment does. You will need an active U.S. security clearance, or eligibility for one." Passion: "you care about the mission and the customer's outcome, not just the close. You go where the action is, on site when a deal needs you, an event to build relationships, dinner with your key stakeholders, etc. and you bring energy that lifts the people around you." Humility: "You win as a team and share credit easily, ask for help early, and take feedback without flinching. You try things, keep what works, drop what does not, and let the playbook get better every quarter because of it." Curiosity: "you dig until you understand: how a program is funded, what your stakeholders actually worry about, and how translation and verification map to a program's outcomes." Nice to have: "active relationships inside one or more major U.S. defense primes; familiarity with embedded systems, safety-critical software, code modernization, or developer tooling; CRM discipline and experience using tools for conducting market and account research." We'll create a

        Requirements

        (or Qualifications). Use
        • for each bullet. For each value we can have a
        • containing the description. Could also separate values as headings but not needed. We'll keep the nice-to-have as separate list maybe under "Nice to have". Could be a subsection but we can just include as
        • with note. Now Benefits: list: - Health care plan with 100% premium coverage, including medical, dental, and vision - 401k with 5% matching - Paid Time Off (uncapped vacation, plus sick and public holidays) - Flexible hybrid or remote work arrangement - Relocation assistance for qualifying employees We'll put under

          Benefits

          . Now ensure we removed boilerplate: EEO, US Citizenship, San Francisco Fair Chance, Wage Transparency. Also removed "Learn more at codemetal.ai."? That's part of About Code Metal; keep. Now produce HTML. Let's craft:

          About the role

          ... (the paragraph)

          Responsibilities

          • Own the deal: run the full motion from first conversation through signature: proof of value, paid integration, production. You are accountable for new business, revenue, and expansion across your accounts, and you carry each deal through internal review and approval to get it done.
          • Build the map: Defense primes are collections of business units and programs, each may have