EMPLOYEE SERVICES MANAGER

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 need to parse the posting. Key info: - Job Title: PUBLIC SERVICE ADMINISTRATOR - 37015 (but we should not repeat as heading) - Location: Springfield, IL, US, 62704 - Salary: Anticipated Starting Salary is $8,625 - $10,178 monthly - Work Hours: Monday - Friday; 8:30a - 5:00p - Anticipated Hybrid Work Schedule Availability: 2 to 5 Days per week in office, depending on operational needs - Benefits: listed under "As a State of Illinois employee, you will receive a robust benefit package that includes the following:" then list items. - Overview: Position Overview paragraph. - Essential Functions: list of duties. - Minimum Qualifications: list. - Preferred Qualifications: list. - Conditions of Employment: list. - About The Agency: paragraph. - Why Work for Illinois? paragraph. - etc. We need to decide sections: About the role (maybe Position Overview), Responsibilities (Essential Functions), Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications?), Skills (maybe from preferred qualifications like Excel, Power BI), Benefits, Pay, Schedule. We must not invent sections with placeholder text. We need to preserve all substantive info, not invent or summarize away detail. Use

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

  for prose. We must remove boilerplate: diversity statement, reasonable accommodation, sponsorship, disclosure of salary info (though salary info is present, we keep it), date, location, job requisition ID, opening/closing dates, agency, class title, skill option, bilingual option, job type, category, number of vacancies, bargaining unit, merit comp code, work hours, anticipated hybrid schedule, headquarters location, work county, agency contact, resume encouragement, why work for Illinois (maybe keep as part of About the role? but it's substantive). However "Why Work for Illinois?" is a section with substantive content about benefits and values; we could incorporate into Benefits or About the role. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can have sections: About the role (Position Overview + Why Work for Illinois?), Responsibilities (Essential Functions), Requirements (Minimum Qualifications), Qualifications (Preferred Qualifications), Skills (maybe from preferred qualifications like Excel, Power BI, etc.), Benefits (benefit list), Pay (salary), Schedule (work hours + hybrid schedule). Ensure we don't create sections with filler. We must not repeat job title as heading. We must not put Job ID etc as headings. We need to output only HTML fragment. Let's extract content. Position Overview paragraph: "The Department of Commerce and Economic Opportunity (DCEO) seeks a strategic, detail-oriented professional to serve as Employee Services Manager (PSA Option 1) within the Human Resources Division. This role oversees payroll, timekeeping, benefits, and personnel transactions while ensuring compliance with the Illinois Personnel Code, CMS Personnel Rules, and collective bargaining agreements. This position also leads the development of data dashboards and reporting tools to support informed decision-making and improve operational efficiency. This is an excellent opportunity for a candidate who combines strong HR expertise with data-driven insight to enhance workforce operations in a dynamic public sector environment." Why Work for Illinois? paragraph: "Working with the State of Illinois is a testament to the values of compassion, equity, and dedication that define our state. Whether you’re helping to improve schools, protect our natural resources, or support families in need, you’re part of something bigger—something that touches the lives of every person who calls Illinois home. No matter what state career you’re looking for, we offer jobs that fit your life and your schedule—flexible jobs that provide the gold standard of benefits. Our employees can take advantage of various avenues to advance their careers and realize their dreams. Our top-tier benefits and great retirement packages can help you build a rewarding career and lasting future with the State of Illinois." We could combine these into About the role. Responsibilities (Essential Functions): List: - Serves as the Employee Services Manager for Department of Commerce and Economic Opportunity (DCEO) in planning, organizing, and directing the operations of Benefits, Timekeeping, Payroll, and Personnel Transactions. - Develops, implements, and maintains reports, dashboards, and data visualization tools to support Human Resources operations and ensure strategic alignment of the Unit’s efforts with the Agency’s mission. - Serves as a member of the DCEO Labor Relations Advisory Team by making recommendations to DCEO’s Labor Relations Administrator and providing interpretation of union contracts, supplemental agreements and past practices, CMS Personnel Rules, Code, Pay Plan and DCEO rules and policies. - Serves as a full-line supervisor. - Performs other duties as required or assigned which are reasonably within the scope of duties enumerated above. We'll put each as

• . Requirements (Minimum Qualifications): List: - Requires knowledge, skill, and mental development equivalent to completion of four (4) years of college with courses in business, public administration, human resources, personnel administration, organizational management, or related fields of study. - Requires prior experience equivalent to three (3) years of progressively responsible administrative experience working with human resources operational functions, specifically with payroll, benefits, timekeeping, and/or labor/employee relations. Qualifications (Preferred Qualifications): List: - Prefers five (5) years of professional work experience in a public or private organization supervising and managing multiple human resources operational units (e.g., benefits, payroll, transactions, and/or timekeeping), including ensuring compliance with federal and state regulations [e.g., Employee Retirement Income Security Act (ERISA), Affordable Care Act (ACA), Family Medical Leave Act (FMLA), Americans with Disabilities Act (ADA), and/or Workers’ Compensation]. - Prefers three (3) years of professional work experience in statewide personnel processes, policies and procedures, including a Personnel Code, Personnel Rules, Pay Plan, collective bargaining agreements, Family Medical Leave Act, Americans with Disabilities Act and/or other relevant laws and regulations. - Prefers two (2) years of professional experience designing, developing, and utilizing interactive dashboards using tools such as Microsoft Power BI to integrate data from multiple sources. - Prefers advanced proficiency in Excel, Power BI, Access, or other related data analysis software. - Prefers three (3) years of professional experience managing an automated timekeeping program or payroll program. - Prefers two (2) years of professional supervisory experience overseeing staff in a professional workplace setting. - Prefers three (3) years of professional experience interpreting and applying collective bargaining unit contract language to determine discipline. Skills: Could be extracted from preferred qualifications: advanced proficiency in Excel, Power BI, Access, or other related data analysis software; experience designing dashboards using Power BI; etc. But we might treat Skills as a separate section listing those specific skills. However we must not invent content; we can list skills derived from the posting. The posting includes "advanced proficiency in Excel, Power BI, Access, or other related data analysis software." Also "designing, developing, and utilizing interactive dashboards using tools such as Microsoft Power BI". Also "managing an automated timekeeping program or payroll program". Also "interpreting and applying collective bargaining unit contract language". Also "supervisory experience". But these are already in Preferred Qualifications. Might be redundant to have both Qualifications and Skills. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications and Skills into one section called Qualifications (including both minimum and preferred). But we already have Requirements (minimum) and Qualifications (preferred). Could also have Skills as separate if there is explicit skill list. There is "advanced proficiency in Excel, Power BI, Access, or other related data analysis software." That's a skill. Could be placed under Skills. But we need to avoid thin sections. Perhaps we have: About the role, Responsibilities, Requirements, Qualifications (including preferred qualifications and skills), Benefits, Pay, Schedule. Let's see if we have enough content for each. About the role: combine Position Overview + Why Work for Illinois? (two paragraphs). Good. Responsibilities: Essential Functions list (good). Requirements: Minimum Qualifications list (good). Qualifications: Preferred Qualifications list (good). Could also include skills within that list; but we could also add a Skills subsection? Might be thin if we separate. Better to keep Qualifications as preferred qualifications (including skills). So we won't have separate Skills. Benefits: list of benefits (good). Pay: salary range (good). Schedule: work hours + hybrid schedule (good). Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Now we need to format. Use

  for each section heading. Inside each section, use

  for prose,

  • for lists. We must not include any boilerplate like diversity statement, reasonable accommodation, etc. Also remove "Date:", "Location:", "Job Requisition ID:", "Opening Date:", "Closing Date:", "Agency:", "Class Title:", "Skill Option:", "Bilingual Option:", "Job Type:", "Category:", "Number of Vacancies:", "Bargaining Unit Code:", "Merit Comp Code:", "Work Hours:" (but we need work hours for Schedule section, so we keep that info but not as a heading). Similarly "Anticipated Hybrid Work Schedule Availability:" goes to Schedule. We need to preserve all substantive information: so we need to include the work hours and hybrid schedule info in Schedule section. We need to include location? The instruction says do not put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. Location is minor metadata? Could be included in a short paragraph maybe under About the role? But we already have About the role with prose; we could add a

    with location and maybe salary? But salary is its own section. Location could be included in a short

    under About the role or maybe we drop it. The instruction: "fold minor metadata into a short

    or drop it." So we could include location in a short

    within About the role or maybe at top. But we already have About the role with two paragraphs; we could add a third short paragraph for location. However we must not repeat job title as heading. It's okay to have location in a paragraph. But we must preserve ALL substantive information. Is location substantive? It's location of job. Probably yes. So we should include it. Similarly, we might include "Agency: Department of Commerce and Economic Opportunity" maybe as part of About the role? But we already mention DCEO in overview. Could be redundant. But to preserve all substantive info, we could include agency in a short paragraph. But we must avoid duplication. The overview already mentions Department of Commerce and Economic Opportunity (DCEO). So agency is covered. Location: "Springfield, IL, US, 62704". We'll include as a short paragraph. Also "Work County: Sangamon" maybe minor metadata; could be included in location paragraph. Also "Headquarter Location: 1011 S 2nd St, Springfield, Illinois, 62704" - that's more specific. Could be included. But we need to decide what to keep. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep all details like location, work county, headquarters, etc. However they might be considered minor metadata; but they are substantive info about job location. We can include them in a short paragraph under About the role or maybe a separate section "Location". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We cannot add a Location heading unless we have real specific content for it (we do). But the instruction says use

    for section headings (e.g.