Cyber Manpower and Workforce Analysis Subject Matter Expert

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Why Join ASI Government?" maybe considered a section? Could be considered "Benefits"? Actually they have a "Why Join ASI Government?" paragraph with bullet points? It's a list of reasons. Could be considered "Benefits" or "About the role"? The posting includes a "Why Join ASI Government?" with bullet points: Help a newly elevated cyber command..., Connect manpower recommendations..., Work across..., Create a repeatable model..., Competitive compensation and comprehensive benefits package available on our careers site. That's more like benefits/why join. Then there is a separate BENEFITS section: "ASI Government offers a comprehensive benefit package to our employees. Benefits can be viewed on our careers site." That's vague; we should not create Benefits section unless posting actually states them. It says "Benefits can be viewed on our careers site." That's not specific; we should not include Benefits section because it's not substantive detail. Similarly Pay: they mention "Competitive compensation" but not specific numbers; we should not create Pay section unless posting actually states them. It says "Competitive compensation and comprehensive benefits package available on our careers site." That's not specific; we should not create Pay or Benefits sections. Schedule: not mentioned. So we may have sections: About the role (maybe the introductory paragraph?), Responsibilities, Requirements, Qualifications (maybe combine with Required?), Skills? The posting includes "Required" and "Preferred". Could treat "Required" as Requirements/Qualifications. "Preferred" as Preferred Experience. Could also have "Skills" maybe from "Strong quantitative, facilitation, and executive-writing skills". That's part of Required. We'll decide. We need to preserve all substantive information. So we need to include the introductory description about ASI Government, the role description, responsibilities list, required qualifications, preferred experience, and maybe "Why Join ASI Government?" as a section like "Why Join ASI Government?" but heading must be from allowed list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join ASI Government?" is not in list; we could map to About the role? Or we could omit that section if not matching allowed headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we could use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should restrict to those. So we need to map content to those headings. We have: - About the role: could include the introductory paragraphs describing ASI Government, the role purpose, six-month engagement, etc. - Responsibilities: the list under "Key Responsibilities". - Requirements: could include the "Required" bullet points (education, experience, clearance). Also maybe "Active Department of Defense Secret clearance..." etc. - Qualifications: maybe the "Preferred" section? Or we could treat Required as Requirements and Preferred as Qualifications. Or we could have both Requirements and Qualifications sections. - Skills: maybe the "Strong quantitative, facilitation, and executive-writing skills" etc. Could be part of Requirements. But we must not create thin sections. We need to ensure each section has substantive content. Let's extract substantive content: Introductory paragraphs: "ASI Government provides government leaders with the expertise they need to navigate acquisition and organizational challenges so they can make an impact and achieve their goals. For over 30 years, ASI has transformed the way government does business, impacting over 70 government agencies across the civilian, defense, and intelligence communities. Do you thrive on creating unique and impactful value for Federal clients? Are you passionate about partnering with clients and collaborating to create solutions? Do you enjoy the opportunity to drive change that impacts our nation? We are looking for smart, curious, driven individuals to join us in partnering with our client to help them solve some of the nation’s most challenging problems. ASI Government serves as a trusted adviser to government leaders seeking improved performance, enhanced organization effectiveness, and strategic change. ASI Government is seeking a senior Cyber Manpower and Workforce Analysis Subject Matter Expert to support the Department of Defense Cyber Defense Command. The six-month engagement will establish an independent, defensible baseline for the workforce required to execute the command's mission. You will help catalog missions, functions, and tasks; identify workload drivers; build workload-to-FTE estimates; assess current and future manpower gaps; and recommend the appropriate military, civilian, and contractor mix. You will work with command leaders, J-Directorate personnel, cyber mission specialists, manpower and personnel staff, and data owners to separate current mission demand from legacy organizational assumptions. Ideal candidates combine DoD manpower-analysis experience, quantitative workforce modeling, structured interviewing, and the judgment to connect staffing decisions to operational risk." That's substantive. Responsibilities list (Key Responsibilities): - Develop a mutually exclusive and collectively exhaustive taxonomy of the command's missions, functions, and tasks, with clear ownership boundaries, outputs, dependencies, complexity tiers, authorities, and completion criteria. - Define workload-driver trees and success measures that connect mission demand to measurable volume, complexity, service-level, coverage, compliance, and risk factors. - Document the data source, owner, collection cadence, known quality issues, and validation method for each key workload driver and performance measure. - Build a J-Directorate-aligned interview architecture, data inventory, extraction plan, and mission-function-task-to-role crosswalk that supports complete and non-duplicative analysis. - Conduct structured, artifact-based interviews using recent incidents, exercises, patch cycles, recurring reporting, and other representative work to validate task definitions, workload, constraints, and handoffs. - Organize needs by mission set, characterize required versus authorized versus on-hand gaps, and express operational consequences through specific mission-impact statements. - Develop a transparent workload-to-FTE model using demand drivers, time standards, complexity and variability factors, quality requirements, and explicit assumptions for 24/7 coverage, relief, surge, and major-incident conditions. - Forecast workload over three to five years and use scenario and sensitivity analysis to identify the assumptions that drive the greatest variance in manpower requirements. - Assess military, civilian, and contractor workforce options using mission authority, inherently governmental considerations, readiness, continuity, security, access, retention, and oversight requirements. - Identify critical dependencies and produce decision-ready reports, executive briefings, an implementation roadmap, and a repeatable manpower-refresh toolkit. Required: - Bachelor's degree and eight or more years of relevant Department of Defense experience in manpower analysis, workforce planning, organizational analysis, force management, personnel policy, operations research, or a related field. - Direct experience conducting or supporting a DoD manpower study, manpower requirements determination, organizational assessment, or mission-function-task analysis. - Demonstrated ability to translate mission demand into workload drivers, time standards, coverage factors, and traceable FTE requirements. - Experience modeling persistent or 24/7 operations, including shift coverage, relief factors, surge posture, variability, and operational-risk assumptions. - Experience reconciling required, authorized, assigned, and on-hand staffing and identifying the operational causes and effects of manpower gaps. - Knowledge of military, civilian, and contractor workforce-mix decisions, including inherently governmental considerations, continuity, access, readiness, and oversight trade-offs. - Strong quantitative, facilitation, and executive-writing skills, with the ability to explain assumptions, uncertainty, and mission impact to senior leaders. - Active Department of Defense Secret clearance and the ability to satisfy all customer security, suitability, and installation-access requirements. Preferred: - Experience supporting the Department of Defense Cyber Defense Command, Joint Force Headquarters-Department of Defense Information Network, Defense Information Systems Agency, U.S. Cyber Command, or a comparable joint cyber organization. - Working knowledge of DoDIN operations and defense, threat-informed risk reduction, incident response, adversary response generation, and support to combatant-command priorities. - Experience with J-Directorate structures, the DoD Cyber Workforce Framework, cyber work-role families, skill bands, or comparable workforce taxonomies. - Experience applying DOTmLPF-P analysis, scenario planning, sensitivity analysis, assumption registers, and options analysis to manpower or force-design decisions. - Advanced experience building auditable workforce models in Excel or a comparable quantitative-analysis environment. - Active TS/SCI clearance. Why Join ASI Government? (list): - Help a newly elevated cyber command establish a defensible workforce baseline without carrying forward unsupported legacy assumptions. - Connect manpower recommendations directly to mission delivery, operational risk, and higher-headquarters resourcing decisions. - Work across cyber mission sets and organizational boundaries with command leaders, operators, workforce specialists, and data owners. - Create a repeatable model and refresh toolkit the command can use to sustain its manpower fact base over time. - Competitive compensation and comprehensive benefits package available on our careers site. We could map "Why Join ASI Government?" to "About the role" maybe as part of role description. Or we could create a separate section "About the role" that includes the introductory paragraphs and the "Why Join" bullet points. That seems okay. We must not include Benefits, Pay, Schedule sections because they are not substantive (just mention benefits available on careers site). So we will omit those. Thus we will output:

About the role

... (intro paragraphs + Why Join bullet points as

• ... )
  maybe we need to keep bullet list as
  • . The instruction: Use
    • for any list of duties/requirements/benefits, and

      for prose. So for the "Why Join" bullet list we should use

      • . The introductory prose can be

        . Thus About the role section will have

        for the descriptive paragraphs, then

        • for the Why Join bullet points. Next

          Responsibilities

          with
          • for each responsibility. Next

            Requirements

            with
            • for each required bullet. Next

              Qualifications

              with
              • for each preferred bullet. We could also include Skills as a separate section but we already covered skills in Requirements. Could we split out Skills? The instruction says prefer a few substantive sections over many thin ones. So we keep as is. We must not repeat job title as heading. We are not. We must not include Job ID etc. Not present. We must preserve ALL substantive information; we are including all bullet points and paragraphs. We must not invent or summarize away detail. We are preserving. We must remove boilerplate: EEO, E-Verify, reasonable accommodations, etc. We removed those. Check for any duplicated lines: none. Now format HTML fragment. We need to ensure proper nesting: each section:

                Heading

                then content. For About the role: we have prose paragraphs (maybe multiple

                ). We'll combine into one

                with line breaks? Better to keep separate

                for each paragraph for readability but still okay. We'll output multiple

                tags. Then

                • for Why Join bullet points. Proceed similarly. Let's craft. About the role prose: Paragraph 1: "ASI Government provides government leaders with the expertise they need to navigate acquisition and organizational challenges so they can make an impact and achieve their goals. For over 30 years, ASI has transformed the way government does business, impacting over 70 government agencies across the civilian, defense,