Habilitation Manager, IDD

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, identify sections: - About the role (intro paragraph) - Responsibilities (the bullet points under "The Habilitation Manager will:") - Requirements/Qualifications (the bullet points under "Qualifications for a Habilitation Manager:") - Benefits (the list under "BAYADA Home Health Care offers a comprehensive benefits plan that includes the following:") - There's also "Why you'll love BAYADA:" which includes some culture points and schedule info (Mon-Fri work hours, Paid Weekly). That could be a Benefits or Culture section. Rules: - Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. - Use

• for lists,

  for prose. - Do NOT repeat job title as heading. - Do NOT put Job ID/requisition numbers as headings. - Preserve ALL substantive information; no invention or summarization. - Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. - Include a section ONLY when real, specific content exists — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). - Never create Pay/Schedule/Benefits sections unless posting actually states them. - Prefer few substantive sections over many thin ones. - Output ONLY HTML fragment — no /, no markdown code fences. Now, parse the content: 1. Opening paragraph: "BAYADA Home Health Care has an immediate opening for a Habilitation Manager (Qualified Professional) in our Charlotte, NC office. If you are looking for an exciting career opportunity in a growing industry, a Habilitation Manager could be the position for you!" This is about the role. Could be "About the role" section with a

  . 2. Responsibilities: "The Habilitation Manager will:" followed by bullet points. Those are duties. Use

  • . 3. Qualifications: "Qualifications for a Habilitation Manager:" followed by bullet points. Use
    • . Could be "Requirements" or "Qualifications". The rule says headings like "Requirements, Qualifications". I'll use "Qualifications" as heading. 4. "Why you'll love BAYADA:" includes culture points, awards, and "Paid Weekly Mon-Fri work hours". That's schedule info. Also "AMAZING culture", "Strong employee values and recognition", "Small team at a local office", "Growth opportunities". Could be a "Benefits" or "Culture" section. But the rule says include Benefits section only if posting states them. There is a separate benefits list later. The "Why you'll love BAYADA" includes schedule (Mon-Fri work hours) and pay frequency (Paid Weekly). That could be a "Schedule" and "Pay" section? But the rule says never create Pay/Schedule sections unless posting actually states them. It does state "Paid Weekly Mon-Fri work hours". That's both pay frequency and schedule. Could create a "Schedule" section with that info, and maybe a "Pay" section? But "Paid Weekly" is pay frequency, not salary amount. The rule says "Pay" section if posting states them. It states "Paid Weekly". That's a pay detail. However, the rule also says never create Pay/Schedule sections unless posting actually states them. It does state them. But we should avoid thin sections. Could combine into a "Benefits" section? The later benefits list is separate. The "Why you'll love BAYADA" includes awards and culture. Might be better to have a "Culture & Perks" section? But the allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Culture" not listed. Could use "Benefits" for the perks? But there is a separate benefits plan. Might create two sections: "Benefits" for the comprehensive benefits plan, and "Schedule" for work hours, and maybe "Pay" for paid weekly. However, the rule says prefer few substantive sections over many thin ones. The "Why you'll love BAYADA" includes multiple items: awards, culture, schedule, pay frequency, growth opportunities. Could make a "Why BAYADA" section? But not in allowed headings. The allowed headings are those listed. Could use "Benefits" to encompass all? But the comprehensive benefits plan is distinct. Might create "Benefits" for the plan, and "Schedule" for Mon-Fri, and "Pay" for weekly pay. But that's three thin sections. Alternatively, combine schedule and pay into a "Compensation & Schedule" but not allowed heading. The rule says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use Pay and Schedule if content exists. The posting states "Paid Weekly Mon-Fri work hours". That's both pay frequency and schedule. Could create a "Pay" section with "Paid Weekly" and a "Schedule" section with "Mon-Fri work hours". But that's thin. Could combine into one section? Not allowed. Might include both in a "Benefits" section? But benefits list is separate. The rule says include a section ONLY when the posting has real, specific content for it. The posting has specific content for schedule (Mon-Fri) and pay frequency (weekly). So we should include them. However, the rule also says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them. So we can create them. But also there is "Growth opportunities" which could be "Career growth" but not a heading. Might include in "Benefits" or "About the role". Let's structure: - About the role: introductory paragraph. - Responsibilities: list of duties. - Qualifications: list of qualifications. - Benefits: the comprehensive benefits plan list. - Schedule: Mon-Fri work hours. - Pay: Paid Weekly. But the "Why you'll love BAYADA" also includes awards and culture. Could add a "Culture" section? Not in allowed headings. Could add as a paragraph under "About the role" or separate? The rule says use

      for section headings (e.g. ...). It says "e.g." meaning those are examples, but we should stick to those? The instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those. However, we should only include sections with real content. The awards and culture are real content. Could create a "Culture" heading? But not in list. Might be okay to use "About the role" to include that? But "About the role" is for the role description. The "Why you'll love BAYADA" is about the company. Could be a separate section "Why BAYADA" but not in list. The rule says "use

      for section headings (e.g. ...)". It doesn't say we cannot use others. But to be safe, maybe include as a "Benefits" section? But benefits already used for the plan. Could have two benefits sections? Not ideal. Alternatively, we can include the awards and culture as a paragraph under "About the role" or as a separate "Company Overview" but not required. The rule says preserve ALL substantive information. So we must include the awards and culture points. They are substantive. We can create a section "Why BAYADA" with

      Why BAYADA

      and list the points. But the instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings if needed. However, the system prompt might expect only those headings. The user says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings. But we can also use "Qualifications" instead of "Requirements". The posting has "Qualifications". So we'll use "Qualifications". Now, the "Why you'll love BAYADA" includes: - BAYADA Home Health Care offers the stability and structure of a national company with the values and culture of a family-owned business. - Link to Newsweek rankings (but we should not include links? The rule says preserve substantive information. The link is to a ranking. Could include as text.) - List of awards: Newsweek's Best Place to Work for Diversity 2023, Newsweek Best Place to Work for Women 2023, Newsweek Best Place to Work (overall) 2024, Newsweek Best Place to Work for Women and Families 2023, Glassdoor Best Places to Work 2018 and 2019, Forbes Best Places to Work for Women 2020, Glassdoor Best Places to Work in 2018 and 2019, Forbes 2020 Best Places to Work for Women. - Paid Weekly - Mon-Fri work hours - AMAZING culture - Strong employee values and recognition - Small team at a local office - Growth opportunities Then separate benefits plan: "BAYADA Home Health Care offers a comprehensive benefits plan that includes the following: Paid holidays, vacation and sick leave, vision, dental and medical health plans, employer paid life insurance, 401k with company match, direct deposit and employee assistance program" Also there is a link to benefits page, but we can ignore link. Then boilerplate: accreditation, 50 years, EEO statement. Remove. So we need to include all substantive info. Let's decide sections: 1. About the role: introductory paragraph + maybe the company description? The first paragraph is about the opening. The "Why you'll love BAYADA" is about company. Could split: "About the role" for the first paragraph, and "Company Overview" for the rest? But not in allowed headings. Could put company description under "About the role" as a second paragraph? Might be okay. But the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must include the awards list. That's a list. Could be a "Recognition" section? Not allowed. Could be under "Benefits"? But benefits are separate. Could create a "Culture & Recognition" section with

      Culture & Recognition

      . But the instruction says use

      for section headings (e.g. ...). It doesn't forbid others. However, the system might expect only those. But the user is the one giving the instruction. The user says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That is a guideline. I think we can use other headings if needed, but we should prefer those. The awards are not exactly benefits, pay, schedule, etc. They are company accolades. Could include as a paragraph in "About the role" or a separate "About BAYADA" section. But the job posting is for a role, not company. However, the posting includes it as "Why you'll love BAYADA". That's a selling point. I'll create a section "Why BAYADA" with

      Why BAYADA

      and include the awards and culture points as a list. But the rule says "never emit a