Program Analyst

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. Remove boilerplate. We need to parse the job description. Key content: - Job title: Program Analyst (already shown, not repeated as heading) - About the role: maybe the paragraph after "PROGRAM ANALYST Oversee complex programs...". That is description. Could be "About the role" section. - Responsibilities: list of duties under "Responsibilities Will Include, But Not Limited To:" then bullet points. - Requirements/Qualifications: "WHAT YOU’LL NEED TO SUCCEED:" includes Education, Required Experience, Required Technical Skills, Preferred Technical Skills, Required Skills and Abilities. Could be under "Requirements" or "Qualifications". We need to decide which sections to include. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can include multiple but avoid thin sections. We have content for: About the role (description), Responsibilities (list), Requirements (education, experience, technical skills, skills/abilities). Could combine Requirements and Qualifications? Might have both sections: Requirements (education, experience) and Qualifications (technical skills, skills/abilities). But we need to avoid filler. We also have Benefits: described under "GDIT IS YOUR PLACE" and "Total Rewards At GDIT". That includes benefits: comprehensive benefits and wellness packages, 401K with company match, competitive pay and paid time off, full-flex work week, etc. Also medical, dental, vision, 401k, disability, life insurance, etc. So we can include Benefits section. Pay: "The likely salary range for this position is $64,230 - $78,200." That's specific. So include Pay section. Schedule: "Scheduled Weekly Hours: 40" and "Hybrid" work location, "Telecommuting Options: Hybrid". So schedule info: 40 hours per week, hybrid. So include Schedule section. Skills: Could be a separate section for skills (maybe technical skills). But we already have technical skills under Requirements. Could still have Skills section summarizing required skills: Microsoft Excel, WFM, etc. But to avoid duplication, maybe we just have Skills section listing technical skills: Microsoft Word, Zoom, Excel, formulas, sorting/filtering, charts, pivot tables; NICE, Verint, Calabrio; understanding of call center metrics; forecasting, scheduling, staffing; analytical, problem-solving, organizational, attention-to-detail; communication; multi-task; accuracy. But we already have those in Requirements. However instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications and Skills into one "Requirements" section. But they ask to use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It's okay to include multiple if they have content. But we should avoid thin sections. We have substantive content for About the role, Responsibilities, Requirements (education, experience, technical skills, abilities), Benefits, Pay, Schedule. That's six sections. Could also include Qualifications but maybe redundant with Requirements. Let's decide to include Requirements (covering education, experience, technical skills, skills/abilities). Not include Qualifications separate. Skills maybe covered under Requirements. So we will not include separate Skills heading. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Now we need to format: - About the role:

with prose summarizing the role description. Must preserve all substantive information, not invent or summarize away detail. So we need to include the description exactly as given? We can keep the sentences but not add extra. We'll copy the descriptive paragraphs: "PROGRAM ANALYST Oversee complex programs that drive impactful mission outcomes for our customers as a Program Analyst Associate. Here, you’ll see the bigger picture on mission initiatives and where your program management career can go at GDIT. MEANINGFUL WORK AND PERSONAL IMPACT As a Program Analyst, the work you’ll do at GDIT will be impactful to the mission of the New York State Department of Health (NYSDOH) Medicaid Management Information System program. In this role, you will support the eMedNY Provider Services Call Center. You will support workforce planning, scheduling, real-time monitoring, and operational reporting for a multi-skilled large call center. You will help transform call volume, agent activity, and service-level data into actionable workforce information that supports contractual performance and customer experience. This role is based at our office at Corporate Woods in Albany, NY." We need to ensure we don't repeat the job title as heading; we already have About the role heading. - Responsibilities:

• each duty. The list includes many items. Need to preserve all. Let's extract each bullet: From "Responsibilities Will Include, But Not Limited To:" then each line: 1. Support interval-level call volume forecasting and staffing analysis using historical call patterns, average handle time (AHT), service-level performance, abandonment, shrinkage, and other operational data 2. Monitor real-time queues and workforce management (WFM) data across multiple call center skills and identify emerging staffing, queue, or service-level risks 3. Analyze forecasted call volume, staffing, and performance trends to actual results and identify that may require schedule or resource adjustments 4. Monitor schedule and real-time agent adherence, and escalate significant variances 5. Utilize WFM, ACD, call recording, and reporting systems to research trends, validate workforce data, and support performance analysis 6. Prepare workforce reports covering service level, average speed of answer (ASA), AHT, abandonment, occupancy, adherence, shrinkage, call volume, and related performance metrics 7. Maintain agent skill assignments, historical records, and staffing assumptions used for forecasting, scheduling, and capacity planning We need to keep them as list items. - Requirements: need to include education, experience, technical skills, skills/abilities. From "WHAT YOU’LL NEED TO SUCCEED:": Education: BA/BS or 2+ years of experience working in a call center, workforce management, reporting, scheduling, or analytical support role Required Experience: 2+ of office experience (maybe typo: "2+ of office experience" meaning 2+ years office experience) Required Technical Skills: Working knowledge of Microsoft Word, Zoom and Excel, including formulas, sorting/filtering, charts, and pivot tables Preferred Technical Skills: NICE, Verint, Calabrio (Verint) or similar WFM platforms Required Skills and Abilities: - Understanding of call center metrics including service level, ASA, AHT, after call work, abandonment, occupancy, schedule adherence, shrinkage, and Aux activity - Basic understanding of call center forecasting, scheduling, staffing, and multi-skill queue environments; familiarity with Erlang-based staffing concepts is a plus - Strong analytical, problem-solving, organizational, and attention-to-detail skills - Excellent written and verbal communication skills with the ability to communicate operational findings clearly - Ability to multi-task and prioritize changing operational needs in a fast-paced call center environment - Strong adherence to accuracy - Ability to multi-task (duplicate? but keep) - Location: Hybrid GDIT IS YOUR PLACE ... Actually location is separate. We should include all these points. Could format as
  • for each bullet. But we also have "Location: Hybrid GDIT IS YOUR PLACE" which is more about location and benefits; maybe location goes under Schedule? Actually schedule section includes location/hybrid. We'll handle location under Schedule. Thus Requirements section will contain education, experience, technical skills, skills/abilities. We need to avoid repeating location. Now Benefits: from "GDIT IS YOUR PLACE" and "Total Rewards At GDIT". Need to capture all benefits specifics: From GDIT IS YOUR PLACE: - Growth: AI-powered career tool that identifies career steps and learning opportunities - Support: An internal mobility team focused on helping you achieve your career goals - Rewards: Comprehensive benefits and wellness packages, 401K with company match, and competitive pay and paid time off - Flexibility: Full-flex work week to own your priorities at work and at home - Community: Award-winning culture of innovation and a military-friendly workplace From Total Rewards At GDIT: - benefits package for all US-based employees includes a variety of medical plan options, some with Health Savings Accounts, dental plan options, a vision plan, and a 401(k) plan offering the ability to contribute both pre and post-tax dollars up to the IRS annual limits and receive a company match. - To encourage work/life balance, GDIT offers employees full flex work weeks where possible and a variety of paid time off plans, including vacation, sick and personal time, holidays, paid parental, military, bereavement and jury duty leave. - To ensure our employees are able to protect their income, other offerings such as short and long-term disability benefits, life, accidental death and dismemberment, personal accident, critical illness and business travel and accident insurance are provided or available. - We regularly review our Total Rewards package to ensure our offerings are competitive and reflect what our employees have told us they value most. Also identity verification process etc but that's boilerplate? Might be considered boilerplate? It's about hiring process, not benefits. Probably we should exclude as it's not benefits. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Identity verification maybe not boilerplate but could be considered part of hiring process; but it's not benefits. We'll exclude. Thus Benefits section will list those items. Pay: include the salary range sentence. Schedule: include "Scheduled Weekly Hours: 40", "Travel Required: None", "Telecommuting Options: Hybrid", "Work Location: USA NY Albany". Also "Hybrid GDIT IS YOUR PLACE" maybe. We'll include these as

    or

    . Since schedule is not a list but details, we can use

    with sentences. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    • Education: BA/BS or 2+ years of experience working in a call center, workforce management, reporting, scheduling, or analytical support role
    • Required Experience: 2+ years of office experience
    • Required Technical Skills: Working knowledge of Microsoft Word, Zoom and Excel, including formulas, sorting/filtering, charts, and pivot tables
    • Preferred Technical Skills: NICE, Verint, Calabrio (Verint) or similar WFM platforms
    • Required Skills and Abilities:
      • Understanding of call center metrics including service level, ASA, AHT, after call work, abandonment, occupancy, schedule adherence, shrinkage, and Aux activity
      • Basic understanding of call center forecasting, scheduling, staffing, and multi-skill queue environments; familiarity with Erlang-based staffing concepts is a plus
      • Strong analytical, problem-solving, organizational, and attention-to-detail skills
      • Excellent written and verbal communication skills with the ability to communicate operational findings clearly
      • Ability to multi-task and prioritize changing operational needs in a fast-paced call center environment
      • Strong adherence to accuracy
      • Ability to multi-task
    But nesting ul inside li may be okay but could be messy. Could instead flatten: each ability as separate li under Requirements without nested ul. Simpler: just list each as separate li. Thus Requirements ul with many li: education, required experience, required technical skills, preferred