Permanency Supervisor (Child Welfare Supervisor 2)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as a heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to extract substantive content: The posting includes: - Initial Posting Date, Application Deadline, Agency, Department, Salary Range, Position Type, Position Title (but we cannot repeat title as heading). We can include metadata in a short

  maybe. - Job Description: includes EEO boilerplate (remove), then narrative about role, responsibilities, etc. - Summary Of Duties: bullet list (though not bullet but sentences separated by periods). We need to turn into

  • . - Minimum Qualifications: list of options (OR statements). We need to turn into
    • . - Essential Attributes: list of experience statements. - Working Conditions: includes Work Locations, Travel, Hours, On-Call, Physical Requirements, etc. - Benefits: list of benefits. - Additional info: Employment Preference, General Information, Contact Information. We must not include application instructions (cover letter required etc.)? The instruction says: Remove ... application instructions. So we should drop cover letter requirement, resume instructions, etc. Also drop "Attention all candidates! Your work history profile..." etc. Also drop "Note: Your resume and cover letter may be uploaded..." etc. Also drop "The use of outside resources such as Artificial Intelligence software..." etc. Also drop "The State of Oregon does not request..." etc. Also drop "Background Checks And Requirements" maybe? That is substantive? It includes background check requirements, which is relevant. Should we keep? It's not application instruction per se, but it's about hiring process. The instruction says remove application instructions, but background check info is not exactly application instruction; it's a condition. Might keep as part of Requirements? Could be considered part of Qualifications? Might keep as a section like "Requirements" maybe. But we have to decide. We also have "Benefits" section with list. We have "Pay" (Salary Range) given: $6,199 - $9,603. That's pay info. So we should include a Pay section. Schedule: The posting mentions Hours: Regular work week with fluctuating hours; occasional overtime may be needed, including evenings and weekends. On-Call: rotating on-call schedule that includes evenings and weekends. So we have schedule info. So we can include a Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown. We need to decide sections: Could have: -

      About the role

      with prose summarizing the role (maybe from Job Description narrative). -

      Responsibilities

      with
      • from Summary Of Duties. -

        Qualifications

        with
        • from Minimum Qualifications. -

          Essential Attributes

          with
          • from Essential Attributes. -

            Working Conditions

            with
            • from Work Locations, Travel, Hours, On-Call, Physical Requirements, etc. -

              Benefits

              with
              • from Benefits list. -

                Pay

                with

                Salary Range $6,199 - $9,603. -

                Schedule

                maybe combine with Working Conditions? But we have separate schedule info; we could embed schedule in Working Conditions. However instruction: prefer few substantive sections over many thin ones. Could combine Working Conditions and Schedule into one section "Working Conditions & Schedule". But we need headings exactly from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They said use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if we have content. We can choose which to include. We have content for About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We also have Requirements maybe same as Qualifications? They differentiate Requirements and Qualifications; but we can put Minimum Qualifications under Qualifications. Requirements maybe could be Essential Attributes? Or we could put Essential Attributes under Requirements. But we need to avoid thin sections. Let's map: - About the role: narrative from Job Description. - Responsibilities: Summary Of Duties. - Requirements: Essential Attributes (or maybe Minimum Qualifications? but Qualifications is separate). We'll put Requirements as Essential Attributes. - Qualifications: Minimum Qualifications. - Skills: Not explicitly listed; maybe we could derive from Essential Attributes but better not to invent. If no specific skills, we should not create Skills section. - Benefits: Benefits list. - Pay: Salary Range. - Schedule: Hours, On-Call, Travel maybe? But Travel is part of Working Conditions. However we have schedule info: Hours, On-Call. Travel could be part of schedule but maybe better to include Travel under Working Conditions. Since we don't have a Working Conditions heading in list, we could incorporate Travel, Work Locations, Physical Requirements into Schedule or Benefits? Not appropriate. Could create a section "Working Conditions" but not in allowed headings. The instruction says use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings (e.g.). Likely they expect us to use those headings only. So we should not create other headings like Working Conditions. We need to fit that info somewhere else, maybe under Responsibilities or About the role? But that would dilute. However we must preserve ALL substantive information. So we need to include Travel, Work Locations, Hours, On-Call, Physical Requirements somewhere. We could put them under Schedule (Hours, On-Call) and maybe under Responsibilities? Not ideal. Alternatively, we could create a section "Working Conditions" but that deviates from instruction. The instruction says "Use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we could use other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." So we could add a Working Conditions section if needed. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add a Working Conditions section with real content. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule, Working Conditions. That's many sections but each substantive. But we could combine Working Conditions into Schedule (since schedule includes hours, on-call, travel). Physical Requirements maybe could go under Responsibilities? Not great. Better to have Working Conditions section. Let's decide to include: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule, Working Conditions. We must not repeat job title as heading. We'll include metadata like Initial Posting Date, Application Deadline, Agency, Department, Position Type in a short

                at top. Now we need to strip boilerplate: Remove EEO paragraphs, Equal Opportunity Employer, Equity North Star, etc. Also remove "Opportunity awaits! Are you ready..." maybe that's part of job description but it's rhetorical; we should keep substantive info? It's more promotional; but it's part of Job Description. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The promotional sentences are substantive? They are part of the posting; we should keep them? They are not boilerplate; they are part of the job description. However they are somewhat fluff but still content. We'll keep them as prose. But we also need to remove duplicated lines. There's some duplication? Not obvious. Now let's extract content. First, metadata: - Initial Posting Date 09/15/2026 - Application Deadline 09/22/2026 - Agency Department of Human Services - Salary Range $6,199 - $9,603 - Position Type Employee - Position Title Permanency Supervisor (Child Welfare Supervisor 2) (but we won't repeat as heading) We can put in a

                : "Posted 09/15/2026; application deadline 09/22/2026. Agency: Department of Human Services. Position type: Employee. Salary range: $6,199–$9,603." Now About the role: We'll take the paragraph after "Job Description" up to before "Summary Of Duties". Let's capture: "The Oregon Department of Human Services is proud to be an Equal Opportunity Employer. We are guided by our Equity North Star and our vision for a positive RiSE organizational culture that advances equity and diversity. We encourage applications from members of historically underrepresented racial/ethnic groups, women, individuals with disabilities, veterans, LGBTQIA2S+ community members, and others to help us achieve our vision of a diverse and inclusive community. Opportunity awaits! Are you ready to lead the way in Child Welfare services? Are you prepared to handle the responsibilities and challenges that come with being a supervisor, such as managing conflicts, setting goals, and providing feedback to your team members? Are you committed to creating a positive and inclusive work environment, where all team members feel valued, respected, and motivated to succeed? If so, join us in supervising social service staff to ensure the safety and permanency of children's lives. Make impactful decisions and create a positive change in the community. As an employee working within the Child Welfare Program, you will have an opportunity to make a meaningful difference in the lives of Oregon’s most vulnerable children and families. Your dedication will help us achieve the Child Welfare Vision for Transformation that will support children and young adults to be safer, healthier, experience less trauma and achieve a greater well-being. We are seeking a Permanency Supervisor (Child Welfare Supervisor 2) to join our Gresham team." We need to remove EEO boilerplate: The first sentences about Equal Opportunity Employer, Equity North Star, encouraging applications from underrepresented groups. That's EEO/equal-opportunity boilerplate; we should remove. So we start after that. Thus About the role content: "Opportunity awaits! Are you ready to lead the way in Child Welfare services? Are you prepared to handle the responsibilities and challenges that come with being a supervisor, such as managing conflicts, setting goals, and providing feedback to your team members? Are you committed to creating a positive and inclusive work environment, where all team members feel valued, respected, and motivated to succeed? If so, join us in supervising social service staff to ensure the safety and permanency of children's lives. Make impactful decisions and create a positive change in the community. As an employee working within the Child Welfare Program, you will have an opportunity to make a meaningful difference