Senior Capture Manager, Federal

We need to output HTML fragment with sections for headings where content exists. Must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, legal, etc. Must include only sections with real specific content. We need to parse the job description and extract sections: About the role? There's a description about the company and role. Could be "About the role" or "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings are appropriate based on content. We have content: Job Description Senior Capture Manager – Federal IT Location: Reston, VA/hybrid. Then description about Hitachi Federal. Then "What You Will Be Doing" (list of duties). Then "Key Responsibilities" with subheadings: Capture Strategy & Execution, Pre-Proposal & Proposal Leadership, Post-Submittal & Customer Engagement, Pipeline & Organizational Leadership. Then "Qualifications & Experience". Then "Preferred Qualifications". Then "Work Environment". Then "Why Hitachi Federal". Then "What We Offer". Then "About Us". Then "Fostering innovation through diverse perspectives". Then "How We Look After You". Then EEO etc (should be removed). Also salary: "$15,000,000 - $15,000,000 USD yearly". That's a specific pay figure (same min and max). According to rules, we should include Pay section only if posting actually states them. It does state salary. So we should include a Pay section with that figure. However note that it's a single number repeated; still it's specific. So include. Schedule? Not mentioned explicitly besides hybrid location. No schedule details. So we should not create Schedule section. Benefits? There's "What We Offer" includes benefits: collaborative culture, professional development, competitive salary and benefits packages. But not specific benefits like health, 401k. The instruction: only create Benefits section if posting actually states them. It mentions "competitive salary and benefits packages" but not specific benefits. Might be considered vague. Better to not create Benefits section unless we have specific benefits listed. There's also "How We Look After You" mentions industry-leading benefits, support, services, life balance, flexible arrangements. Still vague. Probably we should not create Benefits section because no concrete benefits enumerated. However we could include a Benefits section with the generic statements? The rule: 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 "competitive salary and benefits packages" is somewhat vague but still states that there are benefits packages. It's not specific like health insurance, 401k. Might be considered filler? I'd lean to not create Benefits section to avoid risk. Pay: we have specific salary figure, so include Pay. Schedule: none. Now sections: We could have: - About the role (or About the company). The description about Hitachi Federal and the Growth Team could be "About the role". We'll use

About the role

and then paragraphs. - Responsibilities: we have "What You Will Be Doing" and "Key Responsibilities list. Also "Key Responsibilities" with subpoints. We can combine into a Responsibilities section with

• . Should we break into subheadings? Not required; just use
  • . We'll capture all duties. - Qualifications: we have "Qualifications & Experience" and "Preferred Qualifications". Could combine into Qualifications section (required) and maybe a separate "Preferred Qualifications" section? The instruction: use headings from list; Preferred Qualifications not in list but could be under Qualifications? Might be better to have a Qualifications section for required, and maybe a separate "Preferred Qualifications" as a subsection? But only allowed headings are those listed; we could still include a

    Preferred Qualifications

    if we want, but not in the list. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we could still use other headings? Safer to stick to those. So we can put required qualifications under Qualifications, and preferred qualifications maybe under Skills? Or we could add a Skills section for preferred qualifications. The list includes Skills. So we could put preferred qualifications under Skills. Or we could put them under Qualifications as well, but separate with a note. Let's put required qualifications under Qualifications, and preferred qualifications under Skills. - Pay: include Pay section with the salary. - Work Environment: we have a Work Environment section describing office location, hybrid, tools. So we can create a Work Environment heading? Not in list but we could treat as "About the role"? However we have a specific "Work Environment" description. The instruction's examples didn't include Work Environment but we could still use it as a heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect us to use those headings only. But we could also use other headings if they match content? The examples are just examples; they didn't say we cannot use other headings. However to be safe, we could map Work Environment to "About the role" or maybe "Responsibilities"? Not ideal. Perhaps we can create a heading "Work Environment" as it's a natural section; the instruction didn't forbid other headings, just gave examples. I'd include it. But we must not repeat job title as heading. That's fine. We must remove boilerplate: EEO, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Visit us at www.hitachifederal.com", "About Us", "Fostering innovation through diverse perspectives", "How We Look After You" maybe we can keep some content under About the role or Work Environment? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the content from those sections, but we can place them under appropriate headings. For example, "About Us" and "Fostering innovation through diverse perspectives" and "How We Look After You" are substantive about company culture, benefits, etc. We could incorporate them into "About the role" or maybe a separate "Company Overview" heading not in list. But we could create a heading "About the company"? Not in list. However we could put them under "About the role" as part of role description. That might be acceptable. We need to ensure we don't lose any substantive info. Let's extract all substantive paragraphs: From the start: "Hitachi Federal is the trusted leader in mission-centric data solutions for the Federal government. We’re a collaborative, full-service company with longstanding OT/IT roots. We empower data-driven insight with a deep bench of integrated partners — advancing Federal customer missions regardless of their data maturity levels. Hitachi Vantara Federal is a FOCI-mitigated subsidiary of Hitachi. Hitachi Federal will be renamed to Hitachi Federal and aligned under Hitachi Digital effective April 2026. This change will allow the company to provide integrated ONE Hitachi Solutions to the U.S. Federal Government Civilian, Defense & Intelligence Agencies." Then: "Hitachi Federal Team The Growth Team at Hitachi Federal (HF) is seeking a highly qualified Senior Capture Manager to lead strategic capture efforts across new and recompete federal opportunities. This is a senior leadership role reporting directly to the COO and working in close partnership with the CTO, Business Development Executives, Solution Architects, and Proposal Teams. The Senior Capture Manager creates and implements a strategy for searching out promising new business opportunities, primarily through effective teaming strategies, and turning those opportunities into new business for the company. The ideal candidate is a thought leader, able to see the big picture without overlooking the details, and fosters a positive, collaborative, and responsive team environment. This position will be responsible for driving the full capture lifecycle—from early opportunity shaping through proposal submission and post-submittal activities—ensuring strategic alignment, disciplined execution, and a strong probability of win." Then "What You Will Be Doing" bullet list (actually sentences separated by periods). We'll convert to list items. Then "Key Responsibilities" with subheadings and bullet points. Then "Qualifications & Experience" paragraph. Then "Preferred Qualifications" paragraph. Then "Work Environment" paragraph. Then "Why Hitachi Federal" bullet points. Then "What We Offer" bullet points. Then "About Us" paragraph. Then "Fostering innovation through diverse perspectives" paragraph. Then "How We Look After You" paragraph. Then EEO etc (remove). We need to output only HTML fragment. We'll structure:

    About the role

    ... combine the initial company description and team description ...

    Responsibilities

    • ... items from What You Will Be Doing ...
    • ... items from Key Responsibilities (maybe flatten) ...

    Qualifications

    ... required qualifications ...

    Skills

    ... preferred qualifications ...

    Pay

    $15,000,000 USD yearly

    Work Environment

    ... work environment description ...

    Maybe also include a section for "Why Hitachi Federal" and "What We Offer" as part of About the role or separate? Could create a section "Company Culture" but not in list. Could incorporate into About the role as additional paragraphs. We must not create sections with filler text. Ensure each heading has substantive content. Let's draft content. About the role paragraph: combine the first two big paragraphs. Let's write: Hitachi Federal is the trusted leader in mission-centric data solutions for the Federal government. We’re a collaborative, full-service company with longstanding OT/IT roots. We empower data-driven insight with a deep bench of integrated partners — advancing Federal customer missions regardless of their data maturity levels. Hitachi Vantara Federal is a FOCI-mitigated subsidiary of Hitachi. Hitachi Federal will be renamed to Hitachi Federal and aligned under Hitachi Digital effective April 2026. This change will allow the company to provide integrated ONE Hitachi Solutions to the U.S. Federal Government Civilian, Defense & Intelligence Agencies. The Growth Team at Hitachi Federal (HF) is seeking a highly qualified Senior Capture Manager to lead strategic capture efforts across new and recompete federal opportunities. This is a senior leadership role reporting directly to the COO and working in close partnership with the CTO, Business Development Executives, Solution Architects, and Proposal Teams. The Senior Capture Manager creates and implements a strategy for searching out promising new business opportunities, primarily through effective teaming strategies, and turning those opportunities into new business for the company. The ideal candidate is a thought leader, able to see the big picture without overlooking the details, and fosters a positive, collaborative, and responsive team environment. This position will be responsible for driving the full capture lifecycle—from early opportunity shaping through proposal submission and post-submittal activities—ensuring strategic alignment, disciplined execution, and a strong probability of win. That seems good. Now Responsibilities: combine What You Will Be Doing and Key Responsibilities bullet points. What You Will Be Doing list: - Performs and/or leads research efforts to build a deep capture pipeline and continually prioritizes efforts to maximize return. - Lead pre-proposal shaping activities, ensuring opportunities are strategically positioned well in advance of RFP release - Orchestrate all capture executions during the proposal phase, providing clear direction, accountability, and coordination across stakeholders - Manage post-submittal activities to maximize probability of win (PWIN) - Partner closely with Business Development Executives