Dcs Case Aide-Welcome Center

We need to output HTML fragment with headings

for sections: About the role? The posting includes mission description, maybe "About the role" or "About DCS". We need to decide sections based on content. The posting includes: mission description (first paragraph), "Why DCS?" (benefits? actually mission and culture), "What You’ll Do" (responsibilities), "We’re Looking For Someone Who Can" (skills/qualities), "What We Need From You (Required Qualifications)" (requirements), "The Perks" (benefits), also shift and salary info near top. Also mention promotion after four years. We must not repeat job title as heading. No Job ID/requisition as heading. Use

for sections: About the role (maybe "About the position" or "About DCS"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose those that apply. We have Pay: Salary: $18.55 hourly. Also mention promotion to $21.70 after four years. So we can include Pay section. Schedule: Shift: Tuesday - Saturday, 12:00 P.M. - 9:00 P.M. Also may work outside regular hours, weekends, holidays, overtime. So Schedule section. Benefits: The Perks section lists medical, dental, life insurance, retirement, holidays, vacation, sick leave, parental leave, education discounts, wellness, professional growth. So Benefits. Responsibilities: "What You’ll Do" list. Requirements/Qualifications: "What We Need From You (Required Qualifications)" list. Skills: "We’re Looking For Someone Who Can" list (skills/abilities). Could be Skills section. About the role: maybe the introductory mission description and "Why DCS?" could be About the role or About DCS. We'll make an About the role section summarizing mission and why DCS. We must not include boilerplate like EEO, accommodation request, etc. Remove those lines. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from those sections. We must not include duplicated lines. We must not create sections with filler like "commensurate with experience". We have actual specifics. We must output only HTML fragment. Let's extract content. First paragraph: "ARIZONA DEPARTMENT OF CHILD SAFETY 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." Then "We're Hiring! CASE AIDE - WELCOME CENTER Phoenix, AZ 85021 https://dcs.az.gov/careers Shift: Tuesday - Saturday, 12:00 P.M. - 9:00 P.M. Salary: $18.55 hourly Requisition Closing Date: 9/21/2026" We should not include requisition closing date as heading; we can fold into a short p maybe. But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a paragraph with "Requisition Closing Date: 9/21/2026" maybe as minor metadata. But we could drop it? It says preserve ALL substantive information; do NOT invent or summarize away detail. The closing date is substantive? It's metadata but maybe minor. We'll include in a p. Then mission description after "Make An Impact With DCS". Actually after the header we have "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. ..." That's about DCS culture. Then "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. If you're passionate about working with children and families, becoming a Case Aide at a DCS Welcome Center can be a life-changing experience. After four years of successful service, you’ll also be eligible for promotion to the DCS Specialist Trainee position ($21.70 per hour)." That includes promotion info. Then "What You’ll Do As an Assistant Case Manager/Case Aide at the Welcome Center, you’ll:" followed by list. Then "You may also be required to work outside of regular hours, including weekends, holidays, and overtime." This could go under Schedule. Then "We’re Looking For Someone Who Can" list. Then "What We Need From You (Required Qualifications)" list. Then "Knowledge Areas That Support Success" list (maybe could be part of Skills or Requirements). It lists basic principles etc. Could be included under Skills or Requirements. We'll treat as part of Skills/Knowledge. Then "The Perks Join Us, And You’ll Enjoy" list. Then later "If You Have the Skills, You Can Make a Lasting Impact." etc. That's motivational, maybe not needed as separate section. Then accommodation request and EEO boilerplate to remove. We need to output HTML with sections. Let's decide sections: - About the role (or About DCS): combine mission description and "Why DCS?" and promotion info? Might be too much but okay. Better: About the role: mission description and why DCS? plus promotion info. - Responsibilities: What You’ll Do list. - Requirements: What We Need From You (Required Qualifications) list. - Skills: We’re Looking For Someone Who Can list + Knowledge Areas That Support Success. - Benefits: The Perks list. - Pay: Salary and promotion info? But promotion info already in About the role maybe. Could still include Pay section with salary and potential promotion. - Schedule: Shift details and note about overtime/weekends/holidays. We must not repeat info. If we put promotion in About the role, we shouldn't also put in Pay? But Pay section should include salary and maybe mention progression. Could include both but not duplicate exact same sentence. We can mention base salary and potential promotion. Let's craft. We'll produce:

About the role

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. 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. A career with DCS is a mission‑driven opportunity that offers purpose, growth, and the chance to make a lasting difference; after four years of successful service you may be eligible for promotion to the DCS Specialist Trainee position ($21.70 per hour).

Responsibilities

• Transport clients and ensure proper use of child safety seats
• Assist clients with application processes
• Provide Case Assistance to participants involved in child safety services
• Engage, observe and interact with children (examples: lice treatments, changing diapers, potty training, bathing, comforting)
• Provide trauma informed care to children
• Perform housekeeping functions (examples: laundry, cleaning dishes, preparing meals, general cleaning)
• Participate in professional meetings and deliver goods as requested
• Document client interactions and activities

Requirements

• High School Diploma or GED
• Valid driver’s license and a satisfactory 39‑month driving record
• 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
• Ability to obtain and maintain CPR certification

Skills

• Understand child development needs, behavioral needs, and cultural influences on families and communities
• Familiarize themselves with community resources and services that support children and families
• Use strong communication skills, including active listening, de‑escalation, and clear verbal and written communication
• Use Microsoft Office, Outlook, Teams, digital calendars, video conferencing, and mobile technology to document and coordinate work
• Knowledge of basic principles of human and social services
• Knowledge of child welfare and family support concepts
• Knowledge of basic safety practices related to client transportation and child safety seating

Benefits

• Comprehensive medical, dental, and life insurance options
• 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

Pay

Starting salary: $18.55 per hour. After four years of successful service, eligibility for promotion to the DCS Specialist Trainee position at $21.70 per hour.

Schedule

Shift: Tuesday – Saturday, 12:00 P.M. – 9:00 P.M. May require work outside regular hours, including weekends, holidays, and overtime.

We also need to include the requisition closing date maybe as a minor p somewhere. Could add after schedule or at end as a small p. But instruction: fold minor metadata into a short

or drop it. We'll add a small p after schedule:

Requisition closing date: 9/21/2026

. Make sure not to include any boilerplate like accommodation request, EEO, etc. Check that we didn't repeat any content. We included mission description, why DCS, promotion info in About the role and Pay. Promotion appears in both but we phrased differently; still duplicate info but maybe acceptable? Might be considered duplication. Better to keep promotion only in Pay section and not repeat in About the role. Let's adjust About the role to not mention promotion; keep Pay section with salary and promotion. Thus About the role: mission description and why DCS (without promotion). Pay: salary and promotion. Let's rewrite About the role accordingly. Also ensure we didn't include "We're Hiring! CASE AIDE - WELCOME CENTER Phoenix, AZ 85021 https://dcs.az.gov/careers" - we omitted that; it's okay as it's just job title and location which we already have as heading? Actually we omitted location; but location is substantive? The posting includes location Phoenix, AZ 85021. Should we preserve? The instruction: preserve ALL substantive information. Location is substantive. We should include location somewhere, maybe in a short p after About the role or in a meta paragraph. Since we cannot put job title as heading, we can include location in a paragraph. We could add a paragraph after About the role:

Location: Phoenix, AZ 85021

. Also include the URL? Not needed. We also omitted the link to careers; not essential. Let's add location paragraph.