Program Manager, Workforce Development, Aging and Community Services

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes a lot of info: Position/Program Information (maybe about the role), Essential Job Functions (responsibilities), Requirements (qualifications), Additional Information (assessment process, etc). No explicit Benefits, Pay, Schedule. So we should not create those sections. We need to preserve all substantive information, but remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Withhold Information", "Endorsement Of County Qualifications", maybe some parts like "License", "Physical Class", "Additional Information" maybe part of qualifications? The instructions: "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 include a short paragraph for metadata like exam number, type of recruitment, when to apply etc. But we need to decide what to keep. We need to preserve all substantive information: The description of why work for us, essential job functions, requirements, assessment process details, etc. We should drop application instructions like "Apply online by clicking on the 'Apply' green button", "Please fill out the application completely", etc. Also drop "We will send notifications..." etc. Also drop "Register the below domains..." etc. Also drop "Social Security Number Federal law requires..." (cut off). Also drop "Withhold Information", "Endorsement Of County Qualifications", "License", "Physical Class", maybe those are part of qualifications? The instructions say we should not create sections unless there is real specific content. The license and physical class could be considered qualifications? They are specific requirements: "License A valid California Class C Driver License or the ability to use an alternative method of transportation when needed to carry out job-related essential functions." and "Physical Class 2 – Light: ...". Those are substantive qualifications. So we should include them under Requirements or Qualifications. We need to decide headings: About the role (maybe from "Why work for us?" and position/program information). Responsibilities (Essential Job Functions). Requirements (including options, special requirement info, license, physical class). Qualifications maybe same as Requirements? Could combine. But we need to avoid thin sections. Perhaps we have: About the role (why work for us + position/program info). Responsibilities (Essential Job Functions). Requirements (including options, license, physical class). Assessment process maybe separate? Could be part of Requirements? But it's about selection process; maybe we can include a section "Selection Process". However headings list includes Benefits, Pay, Schedule, Skills, Qualifications. Not "Selection Process". But we can still create a heading if content exists? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we can use other headings? It says use

for section headings (e.g. ...). Likely we should stick to those headings. So we can map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. We have content for About the role (why work for us, position/program info). Responsibilities (essential job functions). Requirements (options, license, physical class). Qualifications maybe overlapping with Requirements; maybe we can treat Requirements as qualifications. Skills maybe not explicitly listed; we could infer from assessment content (Management Judgement, Willingness to Learn, etc.) Those are skills/competencies assessed. Could be placed under Skills. Benefits, Pay, Schedule not present, so omit. Thus we will have sections: About the role, Responsibilities, Requirements, Skills. Possibly also Qualifications if we separate but we can merge Requirements and Qualifications? The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we need to decide which heading to use. Since we have both options and license etc., that's more like qualifications. Let's use "Requirements" heading for the eligibility criteria (options, license, physical). Use "Skills" heading for the assessment competencies (Management Judgement, Willingness to Learn, Empathy, etc.). Use "About the role" for why work for us and position/program info. Use "Responsibilities" for essential job functions. We must not repeat job title as heading. The job title is likely "Program Manager, Workforce Development, Aging and Community Services". Not to be used as heading. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the details from each section. Let's extract content: Position/Program Information: - EXAM NUMBER AG8194B-R - TYPE OF RECRUITMENT We welcome applications from anyone. - WHEN TO APPLY: We will be accepting online applications from Wednesday, September 23, 2026, at 8:00 a.m. (PT) until Monday, September 28, 2026, 5:00 PM (PT). All applications must be received before 5:00 p.m. (PT) on Monday, September 28, 2026, to be accepted. We can fold minor metadata into a short

. So we can include a paragraph with exam number, type of recruitment, application window. Why work for us? paragraph: The Aging and Disabilities Department (AD) serves the growing population... etc. Essential Job Functions: list of bullet points (each sentence). We need to convert to

• . The list includes many items; we need to preserve all. Requirements: Options 1,2,3 with details. Also Special Requirement Information (definitions). Also License and Physical Class. We need to preserve all details; not to summarize. So we need to include the options text verbatim (or close). Also the special requirement information paragraphs. Also license and physical class. Skills: from Assessment Content: list of competencies: Management Judgement, Willingness to Learn, Empathy, Working Relationships, Sharing Knowledge and Guidance, Analyzing Information, Learning Quickly, Generating New Ideas, Using time Efficiently, Working to High Quality Standards, Adapting to Change, Controlling Emotions, Achievement, Responsibility, Management Potential, Deductive Reasoning, Reading Comprehension. Also mention passing score 70% or higher. Also exam review info etc. But exam review info maybe considered part of assessment process; but we can include under Skills? Might be better to include under Requirements? However the instruction says we can use Skills heading for competencies. We'll list them as
  • . Also mention passing score. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out sections like "Application and Filing information", "We only accept applications filed online.", "Apply online by clicking on the 'Apply' green button", etc. Also "We will send notifications..." etc. Also "Register the below domains..." etc. Also "Social Security Number Federal law requires..." (cut off). Also "Withhold Information", "Endorsement Of County Qualifications", maybe we can keep license and physical class but drop the rest. Also "Additional Information OUR ASSESSMENT PROCESS" includes headings like Examination Content, Exam Review, Transfer of Test Components, Test preparation, Eligibility and Vacancy Information, Application and Filing information. We need to keep Examination Content (the list of competencies) and passing score. The rest like Exam Review, Transfer, Test preparation, Eligibility and Vacancy Information, Application and Filing information are mostly instructions or boilerplate; we should drop them. However "Eligibility and Vacancy Information" includes that applicants who passed are placed on a list for six months; that's substantive? Might be considered part of process but not required? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that info if it's substantive. But it's about process after exam; maybe we can keep under a section? But we don't have a heading for that; we could incorporate into Skills or Requirements? Might be considered part of "Selection Process". Since we don't have a heading for that, maybe we can omit? But it's substantive. However the instruction says prefer a few substantive sections over many thin ones. Could we add a section "Selection Process"? Not in the examples but maybe allowed. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. So we could add other headings if needed. But to be safe, we could incorporate that info into Requirements or Skills? It doesn't fit well. Perhaps we can add a heading "Selection Process". I think it's acceptable as it's substantive. However 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 suggests using those. To be safe, we could put that info under Requirements? Not really. Maybe we can add a heading "Process". But risk of deviating. Given the instruction to prefer few substantive sections, we could keep the eligibility and vacancy info as a short paragraph under Requirements or Skills? It's about after exam; maybe under Requirements? Not ideal. Alternatively, we could create a section "Selection Process" as an

    . I think it's okay. But we also have "Test preparation" resources links; those are application instructions? Might be considered boilerplate? They are resources for preparation; could be considered substantive? The instruction says remove application instructions. Test preparation resources are not application instructions per se, but they are guidance. Might be considered part of the posting but not essential. Safer to drop. Thus we will keep: - About the role: includes position/program info (exam number, type, when to apply) and why work for us paragraph. - Responsibilities: essential job functions list. - Requirements: includes options 1,2,3, special requirement information, license, physical class. - Skills: includes assessment competencies list and passing score requirement. - Selection Process: includes eligibility and vacancy info (list for six months, used to fill vacancies). Possibly also exam review? But we drop exam review as it's about not reviewable; maybe keep? It's substantive but maybe not needed. We'll keep eligibility and vacancy. We must not include duplicated lines. Ensure we don't repeat. Now craft HTML. We'll start with a

    for metadata: maybe combine exam number, type, when to apply. Then

    About the role

    with

    containing why work for us paragraph. Then

    Responsibilities

    with
    • each essential job function. Then

      Requirements

      with

      for options etc. Might need multiple paragraphs and sublists. We need to preserve the options text exactly. Let's copy: OPTION 1 One (1) year of experience at the level of Los Angeles County's class of Project Supervisor, Community Services* , or higher, responsible for the development and/or implementation of community development and older adult services or related programs**. OPTION 2 Three (3) years of experience at the level of Los Angeles County's class of Community Center Director I* ** , or higher, one (1) year of which must include supervision during the last three (3) years, participating in the development and/or implementation of community development and older adult services or related programs** or in departmental administrative support functions. OPTION 3 Three