Growth Lead- Army Fires

We need to output HTML fragment with sections: About the role, Responsibilities (What You'll Do), Requirements (What We're Looking For), Minimum Qualifications, Preferred Qualifications, Benefits. Also maybe About Forterra? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We should include sections only when posting has real specific content. The posting includes About Forterra (company description) but not required as a section heading? Could include "About the company" but not in list. Probably we can include "About Forterra" as a section? The list of headings includes "About the role". Not "About the company". The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. Likely we should include sections: About the role (maybe combine the "About The Role" paragraph), Responsibilities (What You'll Do), Requirements (What We're Looking For), Minimum Qualifications, Preferred Qualifications, Benefits. Also maybe "Qualifications" could combine Minimum and Preferred? But better separate. We must not include Pay or Schedule unless specified. Not present. Benefits present. We must preserve all substantive info, not invent. Remove boilerplate: EEO, equal-opportunity, scam-warning, legal, navigation, cookie, duplicated lines. Also remove "CLEARANCE ELIGIBILITY" maybe part of Requirements? It's a requirement: must be eligible to obtain and hold a U.S. DoW security clearance. Keep that. We need to format lists with

• . For prose use

  . We need to output only HTML fragment, no /, no markdown. Let's extract content. About Forterra: first paragraph(s) about mission. Could be included as a section "About Forterra"? Not in list but maybe okay. However instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but to be safe we could include "About Forterra" as a

  as well. But they gave examples; maybe they expect only those headings. The posting includes "About Forterra" and "About The Role". The instruction says do NOT repeat the job title as a heading (the page already shows it). It doesn't forbid "About Forterra". I'd include it as a section. But we need to preserve all substantive information. So include About Forterra paragraph. Now "About The Role": includes description of role, two portfolios, location, travel. We'll put that under

  About the role

  . Then Responsibilities: "What You'll Do" bullet points (actually paragraphs with bold headings). We'll convert each bold heading into a list item? The instruction: Use
  • for any list of duties/requirements/benefits. So we need to make a list. The responsibilities are described in paragraphs each starting with a bold phrase. We'll extract each duty as a list item. Let's list them: - Own the portfolio: Carry the growth number for your portfolio. Build and personally drive a pipeline rather than waiting on inbound requirements and own the plan for how that pipeline converts and expands. - Shape demand: Work with operators, requirements owners, capability developers, and program offices to shape requirements and build customer trust before a requirement or solicitation is released so that when it is, Forterra is positioned to win it. - Run capture: Build capture strategies and stakeholder maps, drive customer engagement plans and competitive positioning, and work proposals, solution development, pricing inputs, and win themes. This is both independent contributor capture work and leadership of a cross functional capture team to b else doing it. (some garbled text; we keep as is) - Translate the problem: Meet with operators, understand the tactical and operational problems, and translate it into an acquisition and capture strategy. Then engage program managers or senior stakeholders with enough technical and programmatic depth to shape a real opportunity. - Work with the technical teams: Partner with engineering, product, and program management to turn technical capability into a credible Army solution—identifying where autonomous ground systems create differentiated value inside a broader fires or air defense architecture, rather than positioning autonomy as a standalone capability. - Drive the transition: Move opportunities from experimentation and rapid prototyping into programs of record, production, and scalable fielding—and hand off cleanly to the teams who execute. - Build the business line: As you hit growth milestones, stand up new business areas and grow the team supporting continued expansion across your portfolio. We'll put each as
  • . Now Requirements: "What We're Looking For" bullet list (numbered). We'll convert to list. Items: - 10–20 years of relevant experience across Army operations, requirements, acquisition, program offices, or the defense industry - Deep familiarity with Army capabilities, organizations, requirements processes, acquisition pathways, experimentation, testing, and funding—and how a program moves from operational need to funded program - Demonstrated willingness to personally drive capture: shaping, stakeholder mapping, competitive positioning, proposals, and close - Technical fluency sufficient to engage credibly on autonomy, robotics, vehicle platforms, command and control, sensors, effectors, networking, and system integration. You do not need to be an engineer, but you do need to work effectively with engineering and product teams - The credibility and seniority to represent Forterra independently with senior Army customers - A strong sense of urgency and ownership, and comfort driving outcomes in ambiguous, fast-changing settings - Based in or willing to relocate to Huntsville, AL (Fort Sill, OK also considered), with frequent Huntsville engagement and travel to Washington, DC roughly monthly - Must be eligible to obtain and hold a U.S. DoW security clearance Now Minimum Qualifications: list of items (two sets: one for Fires, one for Air Defense). We'll combine as list. Items: - Field Artillery, Army Fires, long-range precision fires, or closely adjacent operational experience - Acquisition, requirements, capability development, or program office experience supporting Fires, launchers, missiles, or autonomous platforms - Familiarity with Fort Sill, the Fires Center of Excellence, Army Futures Command, PEO/PM organizations, and the Huntsville acquisition ecosystem - Understanding of how mobility, autonomy, launchers, C2, targeting, communications, and effectors come together as an integrated fires architecture - Air Defense Artillery, integrated air and missile defense, counter-UAS, or closely adjacent operational experience - Acquisition, requirements, capability development, or program office experience supporting Air Defense, C-UAS, sensors, effectors, launchers, or C2 systems - Strong familiarity with the Huntsville air and missile defense ecosystem and the Army organizations shaping Air Defense and C-UAS requirements, acquisition, testing, and fielding - Understanding of layered air defense architectures, sensor-to-shooter integration, distributed effectors, autonomous mobility, and the survivability problem posed by modern UAS and missile threats - Ability to work remotely with up to 50% travel Now Preferred Qualifications: list. Items: - An existing network across Huntsville and Fort Sill—particularly in the acquisition, requirements, operational, test, and industry communities relevant to Fires and Air Defense - Private-sector experience in BD, growth, go-to-market, capture, program management, product, or portfolio leadership—especially at a high-growth defense technology company - Experience on both sides of the table: time within Army operational or acquisition communities, followed by industry - Engineering or technical degree—or you nerd out hard on emerging tech Now Benefits: paragraph with list of benefits. We need to use
    • for any list of benefits. So we will make a list. Benefits items: - Premium Healthcare Benefits: Three plan options, including an HSA-eligible plan, with Forterra covering 80% of the plan premium for you and your dependents. - Basic Life/AD&D, short and long-term disability insurance plans 100% covered by Forterra, plus the option to purchase additional life insurance for you and your dependents. - Extremely generous company holiday calendar including a winter break in December. - Competitive paid time off (PTO) offering 20 days accrued per year. - A minimum of 7 weeks fully paid parental leave for birth/adoption. - A $9k annual tuition reimbursement or professional development stipend. - Fully stocked beverage refrigerators with all the Celsius your little heart desires. - 401(k) retirement savings plan, including traditional, Roth 401(k), and after-tax deferral with company match up to 4%. - Your recruiter will be able to share more information about our salary and benefits offering during the hiring process. (maybe not a benefit but we can include as prose? It's more info. Could be a

      .) Also mention equity and salary range: "The salary range for this role is an estimate and is based on a wide variety of compensation factors. The salary offered to candidates will vary based on a variety of factors including (but not limited to) relevant work experience, education, specialized training, critical expertise, training, and more. Equity in Forterra is included in most of our full-time, high-demand roles and is therefore considered part of Forterra’s overall compensation package." We could include that as a

      before benefits list. Now we need to output HTML fragment. Structure:

      About Forterra

      ... (mission paragraph)

      About the role

      ... (description)

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Minimum Qualifications

      • ...
      ...

      Preferred Qualifications

      • ...
      ...

      Benefits

      ... salary/equity paragraph

      • ...
      ...
      We must ensure no duplicate lines, no boilerplate. Remove EEO etc. Now craft the text. About Forterra paragraph: combine first few sentences: "At Forterra, we are unleashing autonomy at scale to transform the battlefield. Our mission is to build the foundational platforms that enable an intelligent ecosystem to coordinate, adapt, and execute with speed and precision even in the uncertainty and disruption of modern conflict. In an era marked by rapid technological change and evolving threats, we design for flexibility, survivability, and operational dominance. Forterra delivers weapons, sensors, and battlefield effects through integrated autonomous networks reaching operational areas faster, safer, and without placing human lives at risk. Our systems operate with distributed control, dynamic routing, and real-time responsiveness, enabling sustained advantage across complex mission environments." That's fine. About the role paragraph: combine the description after "About The Role": "Forterra is a leading provider of autonomous systems for ground-based movement in the working world. Amongst some of the earliest innovators in the field of driverless technology, Forterra is focused on building systems that protect front-line soldiers and enable civilian workers in our industrial base. Forterra is the go-to provider of autonomous mission systems for the U.S. Department of War, providing advantage to the warfighter in all environments We are hiring Growth Leads to own portfolios at the intersection of autonomous mission systems and the Army’s most pressing capability gaps. These are portfolio-owning growth roles, not just account management. You will own the customer strategy, build the pipeline, and personally lea the work of capture; from shaping an operational need into a requirement, through award, and into execution. We are filling two portfolios, and you should apply to the one that matches your background: Army Autonomous Multi-domain Fires: Growth, capture, and customer strategy for