LDSP (Quailrun Mid)

We need to output HTML fragment only, with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions, cookie/navigation, etc. Also remove Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. We need to parse the posting. Key info: - FT/PT Status – Full-Time - Benefits Eligibility – This position is eligible for a full benefits package. - Salary – $22.81 - $37.53 Hourly Wage - Remote Work / In-Office – In-Office / On-Site - Recruiter – Tiffany Wagner | twagner@utah.gov | 801-763-4070 - Application Deadline – 9/21/2026* (note: may close earlier) - Days off: Sunday/Monday - Shift: 9:45pm - 6:15am - Supervisor: Amanda Buxton - Unit Director: Pedro Nuila - Key Responsibilities (list) - Qualifications: Minimum or "day-one" qualifications: list - Preferred Or Trainable/on-the-job Qualifications: list - About The Role: paragraph - Location – 895 N 900 E American Fork, Utah, 84003 United States - Background Check Required – You must successfully pass a criminal history check. - Drug Test Required – No - Schedule Code – AX - Employees in supervisory positions - Why You Should Join Our Team Benefits: paragraph about benefits (list of benefits) - The Agency: mission statement paragraph - EEO Statement: to be removed (boilerplate) - Also "For accommodations, please contact (801) 957-9390." maybe considered boilerplate? It's accommodation contact; could be considered EEO/legal; but likely we should remove as it's boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove EEO statement and accommodation contact. We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: we have "About The Role" paragraph. Also maybe "The Agency" could be considered about the role? But we have separate "About The Role". We'll put that paragraph under

About the role

. - Responsibilities: we have "Key Responsibilities Day-to-day Responsibilities Of This Position" followed by a long sentence with multiple responsibilities separated by semicolons? Actually it's a paragraph with no clear list but we can split into

• items. The responsibilities list includes: - Supervising and training the Direct Support Professionals while serving as a resource in the overall delivery of direct patient care - Managing caseload to include: processing updates, filling out forms and recording activities; progress notes and evaluations - Conducting employee evaluations, creating performance plans and approving time bi-weekly - Working with subordinates to manage and provide direct care services to include bathing, showering, dressing, toileting or changing incontinent briefs (diapering), oral hygiene and feeding individuals who are non-compliant, self-abusive, and aggressive (including maladaptive behaviors such as kicking, scratching, biting, head butting, spitting, throwing objects, etc.) - Consulting with others to discuss treatment plans, new or unusual situations, findings, options, and recommendations on client/patient cases - Coordinating program activities, services, and/or program implementation with private providers, other governmental entities, program users, etc. - Adapting program(s) to meet specific needs or concerns - Cleaning, sterilizing and or disinfecting areas and/or equipment We need to preserve all substantive info; we can break into list items. - Requirements: maybe "Minimum or 'day-one' qualifications:" and "Preferred Or Trainable/on-the-job Qualifications". Those could be under Requirements or Qualifications. The spec says we have sections: Requirements, Qualifications, Skills. We need to decide mapping. We have qualifications (minimum) and preferred. Could treat minimum as Requirements, preferred as Qualifications? Or we could combine both under Qualifications. But we need to avoid thin sections. Perhaps we can have: - Requirements: Minimum qualifications (day-one) - Qualifications: Preferred qualifications - Skills: maybe we can extract skills from responsibilities? But we have no explicit skills list. Could we put communication skills, etc. from qualifications? Actually qualifications include "Excellent communication skills and positive attitude" under minimum. Also "Compassion, reliability and ability to provide excellent care". Those could be skills. But we already have them in qualifications. Might be better to put skills under Qualifications? But spec says we can have Skills section if there is real specific content. We have explicit mention of skills: "Excellent communication skills and positive attitude", "Compassion, reliability and ability to provide excellent care", "Work with or contribute to a work group or team", "Observe details at close range and at a distance", "Observe physical conditions, behavior or surroundings for potential areas of concern or inappropriate activity", "Hear sounds that may indicate potential areas of concern or inappropriate activity". Those are skills/abilities. Could put them under Skills. But we need to avoid duplication. We could put minimum qualifications under Requirements, preferred under Qualifications, and skills under Skills (extract from both). However we must preserve all substantive info; we can't lose any. So we need to ensure each piece appears somewhere. Let's extract: Minimum qualifications (day-one): - Experience working with the intellectually disabled for one year or more - Experience working as a supervisor - Working knowledge of Echart/iChart and Staff Management - Compassion, reliability and ability to provide excellent care - Excellent communication skills and positive attitude Preferred qualifications: - Preference may be given to applicants with prior supervisory experience - Identify developmental needs of others and coach, mentor, or otherwise help others to improve their knowledge, skills and abilities - Work with or contribute to a work group or team to complete assigned task(s) - Observe details at close range and at a distance - Observe physical conditions, behavior or surroundings for potential areas of concern or inappropriate activity - Hear sounds that may indicate potential areas of concern or inappropriate activity Now we also have responsibilities list (above). Also we have location, shift, days off, supervisor, unit director, recruiter, deadline, benefits eligibility, salary, remote/in-office, schedule code, background check, drug test. We need sections for Pay, Schedule, Benefits. Pay: we have salary range $22.81 - $37.53 Hourly Wage. So we can put under

  Pay

  a

  $22.81 - $37.53 hourly wage

  . Schedule: we have shift (9:45pm - 6:15am), days off (Sunday/Monday), schedule code AX. Also maybe full-time status. So we can put schedule details. Benefits: we have "Benefits Eligibility – This position is eligible for a full benefits package." plus "Why You Should Join Our Team Benefits" paragraph with bullet list of benefits: Job Stability, Career Growth, Meaningful Work, Supportive Work Environment. Also maybe other benefits? The paragraph says "Other benefits may include:" then list. So we can capture those. Also we have "Full-Time" status. We also have location, recruiter, deadline, background check, drug test. Those could be placed under a short

  maybe under About the role? Or we could create a separate section like "Details" but not in allowed headings. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location, recruiter, deadline, background check, drug test as a short paragraph maybe under About the role or after responsibilities. But we must not create new headings not in list. So we can add a

  after some section containing that metadata. We need to output only HTML fragment, no /. So we can start with

  About the role

  etc. We need to ensure we don't repeat job title as heading (not present). Good. We need to avoid filler like "commensurate with experience". Not present. Now decide structure: Option:

  About the role

  [About The Role paragraph] plus maybe location, recruiter, deadline, background check, drug test? But that might be too much. Better to keep About the role just the role description. Then add a

  for metadata after that. But we must not create extra headings. So we can just have a

  containing location, recruiter, deadline, background check, drug test, full-time status, etc. Let's extract metadata: - FT/PT Status – Full-Time - Location – 895 N 900 E American Fork, Utah, 84003 United States - Recruiter – Tiffany Wagner | twagner@utah.gov | 801-763-4070 - Application Deadline – 9/21/2026* - Background Check Required – You must successfully pass a criminal history check. - Drug Test Required – No - Schedule Code – AX - Employees in supervisory positions (maybe part of schedule) - Days off: Sunday/Monday - Shift: 9:45pm - 6:15am - Supervisor: Amanda Buxton - Unit Director: Pedro Nuila We could put supervisor and unit director under Responsibilities? Not needed. Better to put metadata in a

  after About the role. Now sections: - About the role: paragraph. - Responsibilities:

  • ...
  - Requirements:
  • ...
  (minimum qualifications) - Qualifications:
  • ...
  (preferred qualifications) - Skills: maybe we can combine some skills from both lists that are not already covered? But we already have communication skills etc in minimum; we could still list them under Skills. However to avoid duplication, we could decide not to have Skills section and instead put those under Qualifications. But spec says we can have Skills section if there is real specific content. We have explicit skills list in preferred qualifications (identify developmental needs, coach, mentor, observe details, observe physical conditions, hear sounds). Those are skills/abilities. So we could put those under Skills. Meanwhile minimum qualifications include experience, supervisor, knowledge, compassion, reliability, communication skills. Those could be under Requirements (minimum) and Qualifications (maybe not needed). But we need to avoid thin sections. Let's think: We have: - Requirements (minimum): experience, supervisor, knowledge, compassion, reliability, communication skills, positive attitude. - Qualifications (preferred): prior supervisory experience, identify developmental needs, coach/mentor, work with team, observe details, observe physical conditions, hear sounds. - Skills: maybe we could extract communication skills, compassion, reliability, etc. But they are already in Requirements. Could still list them under Skills but duplication. Better to follow typical pattern: Requirements = minimum qualifications; Qualifications = preferred qualifications; Skills = maybe not needed. But we have explicit skill-like items in preferred qualifications; we could still put them under Qualifications. Then we could omit Skills section. But we need to decide which sections to include: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. That seems reasonable. We must not include Skills if we don't have distinct content beyond what's already covered. However