CASE MANAGER

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - Department description: "The Arizona Department of Child Safety (DCS) is a social and human services agency whose mission is to successfully partner with families, caregivers, and the community to strengthen families, ensure safety, and achieve permanency for all Arizona’s children through prevention, services, and support." Also "We’re Hiring! CASE MANAGER/CHILD SAFETY SPECIALIST Show Low And Winslow, Arizona https://dcs.az.gov/careers Salary: $21.7068 with step increases after training & years of service Requisition Closing Date: Open Until Filled; Applications Reviewed Daily". We need to drop Job ID etc. The salary line is relevant for Pay section. - "Make An Impact With DCS" paragraph: description of mission, "compassioneers". This could be About the role or maybe About the organization. We'll put under About the role. - "Why DCS?" paragraph: mission-driven career, purpose, growth, etc. Could be part of About the role or maybe Benefits? But it's more about why work there. Could be part of About the role. - "What You’ll Do As a Case Manager/Child Safety Specialist, you’ll:" then bullet list (but not using

yet). Items: Work full-time, 40 hours a week on-site/in field; alternative work hours may be required; Respond to allegations of child abuse or neglect; Conduct interviews and assess child safety; Work with families in their homes and in the community; Coordinate services and develop case plans; Attend court hearings and prepare professional reports; Transport children and support placement needs; Manage cases throughout your assigned region; Collaborate with courts, providers, and partner agencies. We need to put these under Responsibilities as
• . - "We're Looking For Someone Who Can" then list of abilities: Analyze information quickly and accurately, apply logic to complex situations and make independent, sound decisions in high pressure moments; Communicate with clarity and compassion, conduct effective interviews, gather accurate information, and remain professional during challenging situations; Stay organized and maintain accuracy and quality in a high-volume environment; Remain calm in stressful situations; understand diverse family systems and cultural backgrounds; and show empathy while maintaining professional boundaries; Provide strong attention to detail. These could be Skills or Requirements? They are more like desired competencies. Could be Skills. - "What We Need From You (Required Qualifications)" then list: Bachelor’s or master’s degree earned from an institution accredited by an agency recognized by the U.S. Department of Education (conferred transcripts); OR 4 years as an Arizona Department of Child Safety Case Aide; Valid driver’s license and a satisfactory 39 month driving record; The ability to obtain and maintain a valid Department of Public Safety Level One Fingerprint Clearance Card; Work history, Central Registry and Public Record will be considered; Successfully complete the 22 weeks of in person classroom and field training program; This position requires driving or the use of a vehicle as an essential function of the job to conduct State business, and the following requirements apply: Driver’s License Requirements. All newly hired State employees are subject to and must successfully complete the Electronic Employment Eligibility Verification Program (E-Verify). These are Requirements/Qualifications. We'll put under Requirements (or Qualifications). The spec says we can have both Requirements and Qualifications sections; but we should avoid thin sections. We could combine into one section "Requirements". But they ask to use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have content for About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. Schedule maybe from "Work full-time, 40 hours a week on-site/in field; alternative work hours may be required" - that's schedule info. Could be Schedule section. But we need to avoid filler. Let's see if we have enough for each. About the role: we have mission description, why DCS, etc. Good. Responsibilities: we have list. Requirements: we have qualifications list (degree, experience, driver license, fingerprint card, etc). That's substantive. Qualifications: maybe we could separate education vs experience? But we could just use Requirements for all required qualifications. The spec says we can include both but we should avoid thin sections. Since we have enough for Requirements, we can omit Qualifications or combine. But we need to decide. Skills: we have list of abilities (analyze, communicate, organized, calm, attention to detail). That's Skills. Benefits: we have "The Perks Join Us, And You’ll Enjoy Comprehensive medical, dental, and life insurance options A supportive retirement plan through the Arizona State Retirement System (ASRS) 10 paid holidays annually and generous vacation and sick leave Paid Parental Leave Program (must meet the criteria) Higher education discounts, wellness programs, and professional growth and development opportunities Please visit our State of Arizona benefits page." That's benefits. Pay: we have salary: $21.7068 with step increases after training & years of service. Also step increase details: Upon successful completion of the 22-week training program: $22.59/hour; After one year: $24.11; After two years: $25.96; After three years: $27.66. Also note about pay determination credit for qualifying years of service as OCWI Investigator Senior, etc. That's pay. Schedule: we have "Work full-time, 40 hours a week on-site/in field; alternative work hours may be required". That's schedule. Thus we can include all sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Possibly also Qualifications but we can skip to avoid thin. We must not repeat job title as heading. So no

  CASE MANAGER/CHILD SAFETY SPECIALIST>. Good. We must not put Job ID/requisition numbers as headings. We'll drop that metadata. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. At end there is EEO statement, contact for accommodation, recruitment team contact, Equal Opportunity statement. Those are boilerplate; we should remove them. Also the "Please visit our State of Arizona benefits page." is part of benefits; we can keep but maybe it's generic; but it's still substantive? It's a reference; we can keep. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include. We need to format as HTML fragment: use

  for section headings,

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

    for prose. Thus for each section: - About the role: combine paragraphs into

    maybe multiple

    s. - Responsibilities:

    • each duty. - Requirements: list of qualifications: maybe
      • . - Skills: list of abilities:
        • . - Benefits: list of perks:
          • . - Pay: maybe prose with details; could also be list but spec says use
            • for any list of duties/requirements/benefits. Pay is not a list but we can use

              . However we have step increase details; could be list but not required. We'll use

              with details. - Schedule: maybe

              with the schedule statement. We must ensure we don't create empty sections. Now let's extract exact text. About the role: The posting includes: "The Arizona Department of Child Safety (DCS) is a social and human services agency whose mission is to successfully partner with families, caregivers, and the community to strengthen families, ensure safety, and achieve permanency for all Arizona’s children through prevention, services, and support. We’re Hiring! CASE MANAGER/CHILD SAFETY SPECIALIST Show Low And Winslow, Arizona https://dcs.az.gov/careers Salary: $21.7068 with step increases after training & years of service Requisition Closing Date: Open Until Filled; Applications Reviewed Daily Make An Impact With DCS At the Arizona Department of Child Safety (“DCS”), we call ourselves "compassioneers" because everything we do is done with a compassionate heart. We work diligently to protect and support the safety, well-being, and future of vulnerable children and families across the state. DCS is proud to be a pillar of strength for our communities, and the work we do each day to build a safer, more compassionate and more resilient Arizona. Why DCS? Working for DCS is more than a just a job – it’s a mission-driven career that offers purpose, growth, and the opportunity to make a lasting difference. You’ll be part of a team that’s passionate about child welfare and committed to serving with integrity, compassion, and accountability. A career with DCS is an opportunity to give back to your community and help shape a brighter future for Arizona’s children and families." We need to drop the job title line and salary line? Salary goes to Pay section. The "We’re Hiring! CASE MANAGER/CHILD SAFETY SPECIALIST Show Low And Winslow, Arizona https://dcs.az.gov/careers Salary: $21.7068 with step increases after training & years of service Requisition Closing Date: Open Until Filled; Applications Reviewed Daily" includes job title and salary and requisition date. We should not repeat job title as heading, but we can keep the descriptive text? The instruction: "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." So we can drop the job title line entirely, or we could keep the location and maybe the link? But they said fold minor metadata into a short

              or drop it. The job title is minor metadata; we can drop it. The location "Show Low And Winslow, Arizona" maybe relevant but not a heading; could be part of About the role? Might be considered location info; but not required to keep? The instruction says preserve ALL substantive information; location is substantive? Probably yes, location is substantive. However they said fold minor metadata into a short

              or drop it. Location might be considered minor metadata? Not sure. But we can include location in a short

              under About the role. Similarly the link to careers maybe not needed. We'll drop link. Thus About the role paragraph(s) will include mission description, compassionate heart, why DCS, etc. We'll also include location maybe. Let's craft:

              The Arizona Department of Child Safety (DCS) is a social and human services agency whose mission is to successfully partner with families, caregivers, and the community to strengthen families, ensure safety, and achieve permanency for all Arizona’s children through prevention, services, and support.

              Located in Show Low and Winslow, Arizona, DCS calls its employees "compassioneers" because everything is done with a compassionate heart, working to protect and support the safety, well‑being, and future of vulnerable children and families across the state.

              Working for DCS is more than a job – it’s a mission‑driven career that offers purpose, growth, and the opportunity to make a lasting difference. You’ll be part of a team passionate about child welfare, committed to serving with integrity, compassion, and accountability, and helping shape a brighter future for Arizona’s children and families.

              That seems to capture. Now Responsibilities: list items exactly as given. We need to capture each bullet: - Work