Program Management Analyst B-2 (WBZ) - 01.6.34

We need to output HTML fragment with sections: Overview? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. The posting includes: - Overview (first paragraph about company) - Position Summary (description of role) - Responsibilities (list of duties) - Requirements (education/experience) - Why This Role Matters (maybe could be part of Overview or separate? It's more like motivation; but we could include as a section maybe "Why This Role Matters" but not in the list of allowed headings? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings when appropriate. Could also use other headings if needed? The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those headings. We have content for: - About the role (maybe Position Summary) - Responsibilities - Requirements (education/experience) - Benefits (listed) - Possibly Qualifications? The Requirements already includes qualifications; but we could separate Qualifications? The posting includes "Requirements" with education/experience. Could also have "Qualifications" but it's same. We'll just use Requirements. - Overview: maybe "About the role" or we could have an introductory paragraph before headings. The instruction: do NOT repeat the job title as a heading (the page already shows it). So we can start with a

  for overview summary. We need to include all substantive information. Let's extract: Overview paragraph: "Join a team where innovation meets mission. Our AI, cloud, cyber, and modernization solutions save agencies thousands of hours, safeguard national security, and strengthen health and humanitarian missions worldwide. With more than 1,700+ team members, 1,500+ AI & data experts, and 100+ prime contracts, we deliver on a scale and with purpose. We've been recognized as a Top Workplace by The Washington Post for six consecutive years and named to the Inc. 5000 list of Fastest-Growing Private Companies in 13 of the past 14 years. Credence is a welcoming environment for those looking to grow and make a meaningful impact. We encourage employees to push boundaries and help solve critical, world-changing federal challenges." Position Summary: "Credence has an immediate opening for a Program Management Analyst B-2 (WBZ) at the senior level to support the B-2 Division AFLCMC/WBZ who is responsible for the modernization, test, production, fielding and sustainment of B-2 aircraft and related systems. The B-2 is a high demand, low density fleet that is 20+ years old, is undergoing numerous concurrent acquisitions to solve obsolescence issues, and delivers critical aerial denial/anti-access and nuclear capabilities at WPAFB, OH." Then responsibilities list: many bullet-like sentences. We'll convert to

  • . Requirements: "Must have an active or current Secret security clearance, Master's or Doctorate Degree in a related field and ten (10) years of experience in the respective technical/professional discipline being performed, five (5) years of which must be in the DoD; OR Bachelor's Degree in a related field and twelve (12) years of experience in the respective technical/professional discipline being performed, five (5) years of which must be in the DoD; OR fifteen (15) years of directly related experience with proper certifications as described in the PWS labor category performance requirements, eight (8) years of which must be in the DoD" Why This Role Matters: includes three bullet points: Real-World Impact, Growth-Oriented Environment, Culture of Empowerment. Could be a section maybe "Why This Role Matters" but not in the list. Could incorporate into Overview or as a separate section with heading "About the role"? Might be okay to add a section "Why This Role Matters" as

    but not in the examples. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say you cannot use other headings, but to be safe we could incorporate those points into a

    under Overview or maybe under a section "About the role". However, the instruction says "Prefer a few substantive sections over many thin ones." So we could have sections: About the role (includes overview + position summary + why this role matters), Responsibilities, Requirements, Benefits. Benefits list: Health Care Plan (Medical, Dental & Vision), Retirement Plan (401k, IRA), Life Insurance (Basic, Voluntary & AD&D), Paid Time Off (Vacation, Sick & Public Holidays), Family Leave (Maternity, Paternity), Short Term & Long Term Disability, Training & Development. We need to output only HTML fragment. Let's structure:

    Overview paragraph

    Position summary paragraph

    About the role

    Why This Role Matters content as prose? Could be

    • but it's not a list of duties; it's more like bullet points. Could still be
      • . The instruction: Use
        • for any list of duties/requirements/benefits. So for Why This Role Matters we could treat as list. But it's not duties/requirements/benefits; it's more like motivation. Could still be

          but we can keep as

          • if we want. However, the instruction says "Use
            • for any list of duties/requirements/benefits". It doesn't forbid using for other lists, but it's safer to use

              for prose. We'll put as

              with sentences. Better: After overview and position summary, we could have a

              About the role

              containing the position summary and why it matters. But we already have position summary as separate

              . Might be redundant. Let's decide: -

              Overview paragraph (company description)

              -

              About the role

              -

              Position summary paragraph

              -

              Why This Role Matters: Real-World Impact — ... Growth-Oriented Environment — ... Culture of Empowerment — ...

              -

              Responsibilities

              -
              • each duty
              -

              Requirements

              -

              Requirements paragraph

              -

              Benefits

              -
              • each benefit
              We must not include Pay or Schedule sections as not specified. Now extract responsibilities list exactly as given, preserving all detail. Responsibilities list from text: "Provide statistical data analysis, modeling, simulation, optimization, and analytical support to assist the Government in developing and implementing standard performance-management measures and metrics, including methodologies to set targets and assess progress against the organization's Strategic Plan, goals, objectives, cost-effectiveness, efficiencies, and other Government-directed areas" "Maintain existing performance measures and metrics and develop, coordinate, and implement new metrics and targets to measure performance across all business areas, including business rules for metrics data collection, metrics, and performance-measurement tools" "Routinely review and analyze business rules to ensure alignment with desired performance targets, including developing performance measures, identifying data sources, determining data-pull frequency and formats, documenting calculations, and analyzing metric data" "Support Acquisition Sustainment Reviews, Congressional inquiries, and CAT activities by performing Action Officer duties, including preparing briefings, developing and coordinating TMT suspense responses, completing required analysis, and recommending courses of action for leadership decisions" "Respond rapidly to taskers using a comprehensive approach that identifies problems, analyzes issues, develops courses of action, and provides recommendations suitable for GOFO-level review" "Assist with manning and screening the RSO workflow and support the overall management of assigned programs and efforts while coordinating with lateral organizations and external agencies as required" "Apply recognized statistical techniques and tools to perform leading-indicator analyses for time series, including predictive forecasting methods such as basic moving average, exponential smoothing, regression analysis, and Box-Jenkins" "Use forecasting techniques and tools to identify confidence levels, margins of error, sensitivity analyses, what-if analyses, hypothesis testing, modeling, and simulation to improve metrics program forecasting and planning efforts" "Support internal and external briefings and reports by preparing, scheduling, and coordinating materials, reviewing correspondence, and producing letters, reports, spreadsheets, database reports, and graphs using standard USAF office automation software" "Assist the RSO PEG suspense and tracking team with TMT suspense tracking, workflow mailbox review, response coordination with two-letter directorates, and assignment of PEG action officers to each TMT task" "Prepare weekly status briefings of late and upcoming TMT suspense's for PEG Chief review, assist with closure of TMT suspense's, and package suspense's for 31+ AFLCMC Program Executive Officers and Functional two-letter offices" "Train RSP PEG and two-letter action officers on the use of TMT and respond to technical system and process-related questions" "Provide direct support to quickly and accurately turn data into usable, actionable output and communicate information efficiently and effectively for AFLCMC senior leaders, higher headquarters, and directorate-level offices" "Assist with updating and retrieving information in the center MS SharePoint document library and compile, format, and store directorate-level inputs to taskings supporting development of center responses" "Use NIPRNET and SIPRNET electronic mail to request and compile responses and transmit approved responses to specified higher headquarters or Congressional inquiries" "Assist in managing and tracking civilian and military decoration programs for the center, including coordinating with the center Directorate of Personnel awards monitor to track awards packages" We need to ensure each is a separate
            • . Some sentences have apostrophe issues like "TMT suspense's". We'll keep as is. Now Requirements paragraph: combine the three options. We'll output as a single

              containing the requirements text. Benefits list items: - Health Care Plan (Medical, Dental & Vision) - Retirement Plan (401k, IRA) - Life Insurance (Basic, Voluntary & AD&D) - Paid Time Off (Vacation, Sick & Public Holidays) - Family Leave (Maternity, Paternity) - Short Term & Long Term Disability - Training & Development Now Overview paragraph: combine the first paragraph(s) before Position Summary. Overview text: "Join a team