Staff Capture Manager

We need to output HTML fragment with sections: h3 for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections where posting has real specific content. The posting includes many responsibilities, qualifications, etc. It includes Benefits and Salary (Pay). No schedule info. So we should not include Schedule heading. Also maybe "About the role" could be a brief intro paragraph summarizing role? The posting starts with "Expertise And Functions Capture Leadership Lead assigned Federal Government capture opportunities..." That's basically description of role. We can put that under

About the role

with

containing that description. Responsibilities: many bullet points. We'll list them as

• . Requirements: maybe separate from Qualifications? The posting has "Requirements Qualifications:" then lists Education/Training, Experience, Security, Physical Requirements. We could treat "Requirements" as heading and include those items. Or we could split into Qualifications (Education, Experience) and Skills? But we have to follow instruction: use headings for those categories if content exists. We have content for Requirements (education, experience, security, physical). Also we have Skills: maybe communication, presentation, relationship-building, leadership, cross-functional team leadership. Those are listed under Experience section as skills. Could put under Skills heading. Benefits: listed. Pay: salary range. We should not repeat job title as heading. No Job ID. We must remove boilerplate etc. No application instructions. We must preserve all substantive info. So we need to capture all bullet points. Let's extract sections. About the role: The first sentence(s) maybe: "Expertise And Functions Capture Leadership Lead assigned Federal Government capture opportunities from qualification through proposal submission Develop, maintain, and execute comprehensive capture plans for assigned opportunities Establish capture objectives, milestones, action plans, resource requirements, and schedules necessary to position KIHOMAC for successful competition Serve as the primary point of accountability for capture strategy, readiness, and execution for assigned opportunities Coordinate capture activities across Business Development, Operations, Engineering, Contracts, Pricing, Finance, and Proposal organizations Maintain capture momentum and accountability by assigning actions, tracking milestones, identifying risks, and escalating issues requiring leadership attention Assess opportunity maturity and capture readiness and recommend continued investment, corrective actions, or No-Go decisions when appropriate Customer and Competitive Strategy Develop and execute customer engagement strategies designed to improve understanding of customer missions, requirements, priorities, acquisition strategies, and evaluation drivers Research and analyze customers, incumbents, competitors, acquisition history, contract vehicles, budgets, and market conditions Develop competitive assessments identifying competitor strengths, weaknesses, likely strategies, and KIHOMAC positioning Identify customer hot buttons, key requirements, decision drivers, and potential discriminators Develop and maintain opportunity-specific win strategies, win themes, value propositions, and discriminators Translate customer and competitive intelligence into actionable capture strategies Opportunity Qualification and Pipeline Management Research and qualify Federal Government opportunities using SAM.gov, GovWin, agency forecasts, customer engagement, industry sources, and other market intelligence resources Manage an assigned portfolio of strategic capture opportunities within the corporate business-development pipeline Maintain accurate opportunity status, capture milestones, PWIN assessments, customer engagement activities, competitive positioning, teaming status, and resource requirements Participate in pipeline reviews and recommend prioritization of corporate capture resources and investment Support development and execution of corporate and business-area growth plans Teaming and Partnerships Identify capability gaps and determine appropriate Make/Buy/Team strategies for assigned opportunities Identify, evaluate, and recommend potential teammates based on capabilities, past performance, customer relationships, competitive positioning, and strategic value Establish and maintain relationships with prime contractors, subcontractors, technology providers, and other strategic partners Develop opportunity-specific teaming strategies that strengthen KIHOMAC's competitive position Coordinate with Contracts and corporate leadership in the development of NDAs, teaming agreements, and other capture-related agreements Solution and Pricing Strategy Lead cross-functional development of differentiated and executable solutions responsive to customer requirements Coordinate with technical and operational subject matter experts to develop technical, management, staffing, transition, and performance approaches Facilitate solution-development sessions and ensure proposed solutions align with identified customer needs and competitive strategy Coordinate with Pricing, Finance, Operations, and leadership to develop competitive pricing strategies Support development of price-to-win assessments and evaluate competitive pricing considerations when appropriate Ensure capture strategies balance customer value, competitive positioning, execution risk, and KIHOMAC business objectives Gate Reviews and Executive Engagement Prepare and lead executive gate reviews for assigned opportunities Present opportunity assessments, customer intelligence, competitive analysis, teaming strategies, solution concepts, pricing considerations, PWIN assessments, risks, resource requirements, and recommendations to corporate leadership Provide objective Go/No-Go recommendations based on opportunity maturity, competitive position, strategic alignment, resources, and expected return Identify capture deficiencies and establish corrective actions prior to subsequent gate reviews Provide leadership with timely visibility into significant changes affecting opportunity strategy or PWIN Capture-to-Proposal Transition Establish proposal strategy prior to solicitation release to the greatest extent practical Coordinate with Proposal Management to ensure an effective transition from capture to proposal execution Provide the proposal team with documented customer intelligence, competitive assessments, win themes, discriminators, solution strategies, teaming arrangements, pricing strategies, and other capture artifacts Support development of proposal outlines, storyboards, executive summaries, technical and management approaches, and other strategic proposal content Participate in proposal writing, solution reviews, Black Hat reviews, Pink/Red/Gold Team reviews, and other proposal activities as appropriate Maintain continuity of capture strategy throughout proposal development and ensure the final submission reflects the approved win strategy Business Development and Corporate Growth Support Establish and maintain strong relationships with Government customers, industry partners, prime contractors, subcontractors, and other stakeholders Coordinate customer and industry meetings supporting assigned capture opportunities and broader corporate growth objectives Prepare and present KIHOMAC capability and opportunity-specific presentations to customers and potential teammates Support industry days, conferences, site visits, customer meetings, and other Business Development activities when strategically relevant Maintain current knowledge of KIHOMAC capabilities, past performance, technologies, customers, contracts, and strategic growth priorities Collaborate with corporate leadership, directors, managers, and subject matter experts to identify opportunities to expand KIHOMAC capabilities and market position Capture and communicate lessons learned following major proposal submissions and award decisions to continuously improve KIHOMAC capture processes Key Performance Expectations Develop and execute disciplined capture strategies that increase KIHOMAC's probability of win Maintain an actionable and accurately assessed portfolio of qualified capture opportunities Position strategic opportunities before solicitation release Develop meaningful customer and competitive intelligence that influences KIHOMAC's win strategy Build effective cross-functional capture teams and maintain accountability for capture actions and milestones Develop effective teaming, solution, and competitive strategies Deliver high-quality, decision-ready gate reviews to corporate leadership Transition mature capture strategies effectively into proposal development Contribute to improved proposal quality, competitive positioning, win rate, and sustainable corporate growth Other duties as assigned" That is huge. We'll need to break into bullet list under Responsibilities. Probably each sentence or clause is a responsibility. We'll create
  • items for each major bullet. But we must not lose info. Could group similar items but must preserve all substantive info; we can combine but not lose detail. Safer to keep each sentence as separate
  • . That will be many items but okay. Then Requirements: Education/Training, Experience, Security, Physical Requirements. We'll put under

    Requirements

    with
    • each. Skills: maybe communication, presentation, relationship-building, leadership, ability to lead cross-functional teams through influence. We'll put under

      Skills

      with
      . Benefits: list. Pay: salary range. No Schedule. Let's craft HTML. We'll start with

      About the role

      ...

      . The about role paragraph could be a concise summary: maybe first sentence: "Lead assigned Federal Government capture opportunities from qualification through proposal submission; develop, maintain, and execute comprehensive capture plans; establish capture objectives, milestones, action plans, resource requirements, and schedules; serve as primary point of accountability for capture strategy, readiness, and execution; coordinate capture activities across Business Development, Operations, Engineering, Contracts, Pricing, Finance, and Proposal organizations; maintain capture momentum and accountability; assess opportunity maturity and capture readiness; recommend continued investment, corrective actions, or No-Go decisions." That captures many. But we need to preserve ALL substantive information; summarizing may lose detail. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we cannot summarize away detail; we need to keep details. But we can put the long paragraph as is, preserving all details. That's okay: we can put the entire block as a paragraph (

      ) containing all those sentences. That preserves detail. Then we still need Responsibilities section? That would duplicate. Better to treat About the role as a brief overview, and Responsibilities as detailed list. But that would risk losing detail if we omit some details from About the role. However we can keep About the role as a short summary that does not omit any detail that is not elsewhere? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we create a summary that omits details, that's summarizing away detail, which is not allowed. So we must not omit any detail. Therefore we need to include all details somewhere. If we put all details in Responsibilities list, we can have About the role be just a short generic statement that does not contain any substantive info not covered elsewhere? But that would be inventing? Actually About the role could be a short generic description that is not substantive; but we risk violating "Prefer a few substantive sections over many thin ones." But we need to include About the role heading only if posting has real, specific content for it. The posting does have a description of the role at start; that is substantive. So we need to include it. But we can include the full description as the About the role paragraph, and then not have a separate Responsibilities section (or we could still have Responsibilities but then we'd duplicate). The instruction does not forbid duplication, but says preserve all substantive information; duplication is okay as long as we don't lose info. However they might consider duplication as unnecessary but not prohibited. Safer to include About the role paragraph with the full description, and then maybe not have Responsibilities (or we could keep Responsibilities but it's redundant). The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid thin sections. Having both About the role and Responsibilities with overlapping content may be thin. Better to have one section that captures the role description and responsibilities. Could use About the role as heading and put the detailed list inside? But they said use

      for section headings (e.g. About the role, Responsibilities, etc). So we could have About the role heading and then a

      • list of responsibilities. That would be fine: About the role section contains the responsibilities list. That satisfies heading usage and avoids duplication. So we will have

        About the role

        then
        • each responsibility. Thus we don't need separate Responsibilities heading. But the instruction list includes Responsibilities as an example heading; we can still use it if we have content. But we can choose to use About the role only. However they said "Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That's just examples; we can choose which to include. So we will include About the role, Requirements, Qualifications?, Skills, Benefits, Pay. But we have qualifications content overlapping with Requirements. The posting has "Requirements Qualifications:" then lists Education/Training, Experience, Security, Physical Requirements. That's basically qualifications. So we could have a single section "Requirements" containing those. Or we could split into Qualifications (Education/Training, Experience) and Skills (communication etc). But we already have Skills separate. Let's decide: We'll have sections: About the role (list of duties), Requirements (Education/Training, Experience, Security, Physical Requirements), Skills (communication, presentation, relationship-building, leadership, ability to lead cross-functional