Leave and Accommodation Manager II

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID. Remove boilerplate: EEO, legal, privacy, etc. Also remove application instructions. Keep substantive info. We need to parse the posting. Overview: description of Prime Healthcare. Could be "About the role" or maybe "Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - Overview: description of company. Could go under "About the role"? Usually "About the role" describes the role, not company. But we have no explicit "About the role". Could we create "About the role" with the overview? Might be okay. But we must only include sections when posting has real specific content for it. The overview is about the company, not the role. However we could treat it as "About the role" maybe not accurate. Better to maybe not include About the role if no specific role description besides responsibilities. But we have responsibilities section. Could we put overview under "About the role"? The instruction says use those headings as examples, not mandatory to use all. We can choose which sections to include based on content. We have: Responsibilities: detailed. Qualifications: includes required qualifications (High school Diploma, five years experience, etc.) and Preferred Qualifications. Skills: maybe we can extract skills from qualifications: strong knowledge, ability to analyze, etc. Could be separate Skills section. Benefits: mentioned in Pay Transparency paragraph: "Prime Healthcare offers competitive compensation and a comprehensive benefits package..." includes list: paid time off, 401K, medical, dental, vision, tuition reimbursement, voluntary benefits. Also note benefits may vary based on employment status. Pay: compensation estimate $85,000-$100,000 annualized. Schedule: "Employment Status Full Time Shift Days". Not specific shift days; just says Full Time. Could we consider Schedule section? The posting says "Employment Status Full Time Shift Days". That's vague. Might be considered schedule info but not specific. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state employment status full time, but not shift days. Could we still include Schedule? It says "Shift Days" but no details. Might be considered placeholder. Better to omit Schedule if not specific. We also have "Pay Transparency" section with compensation estimate and benefits. We need to avoid boilerplate: EEO, privacy notice, etc. Thus final HTML could have sections:

About the role

maybe with overview? Or we could skip About the role and go straight to Responsibilities. But we need to follow instruction: use

for section headings (e.g. About the role, Responsibilities...). It doesn't say we must include About the role. So we can omit if no content. We have Responsibilities, Qualifications (maybe split into Required Qualifications and Preferred Qualifications), Skills, Benefits, Pay. We need to avoid duplication. Let's extract responsibilities text: "The Leave and Accommodation Manager II manages the complete cycle of medical leaves of absence from initial requests to return to work, and the complete cycle of the interactive process for accommodation requests, for their assigned facilities. This includes following the required processes under FMLA and state leave laws as well the interactive process under ADAA, PWFA and state disability laws. Case management includes supporting employees seeking medical leave and/or accommodation answering with process questions, intake, determining eligibility, sending required notifications, seeking sufficient documentation, leading any interactive discussion as required under law, sending determinations. It also includes explaining benefit impacts as well as explaining and processing leave of absence pay requests. Case management requires extensive use of the phones, emails, outlook and case management system. Role serves as support for Leave and Accommodation Manager I and may support with Family Care, Military, Pregnancy, Bereavement, and union/company leaves of absence requests and escalations." We'll put that in

maybe with

• for list of duties? The responsibilities are prose; we could keep as

  . Could also break into list but not required. Qualifications: Required: - High school Diploma - Five years' experience in Human Resources in a benefits, leave management or generalist related position, with a minimum three (3) years’ experience in interactive process administration. - Strong knowledge of federal and state leave and disability laws, specifically ADAAA, FEHA, PWFA, FMLA, CFRA, CA PDL, NJFLA; experience with CA leaves and accommodations is required. - Strong knowledge of the interplay between federal and state leave and disability laws. - Strong knowledge and understanding of absence management integrated workflows, return-to-work strategies, interactive process workflows. - Strong knowledge of benefits impacts while on leaves of absence. - Strong knowledge of leave of absence pay integrations with wage replacement benefits. - Ability to analyze, problem solve, organize and manage multiple priorities, and effectively follow up in a fast-paced environment. - Ability to build and maintain effective professional relationships through strong interpersonal skills including consistent demonstration of solid professional judgement. - Strong written and verbal communication abilities, including effective presentation skills to all levels of the organization. - Solid skills in Microsoft Office programs, including Excel, Word, PowerPoint, Outlook. Preferred Qualifications: - Bachelor’s degree in Human Resources, Business Administration, or related field. - Experience working in a Healthcare environment with high volume of leave and accommodation cases. - Experience with Lawson, JBDev or leave case management software preferred. - Experience managing leave and accommodation across US. - Experience working in unions environments. We could combine Required and Preferred under Qualifications heading, maybe separate subheadings? But we only have

  for sections; we could have

  Qualifications

  and then within that we could have

  for required and

  for preferred, or use

  • . Probably better to use
    • for list. Skills: Could extract from qualifications: strong knowledge, ability to analyze, etc. But we might just treat qualifications as skills. However we have a separate Skills heading possible. We could put skills like: Strong knowledge of federal and state leave laws, ability to analyze, problem solve, interpersonal skills, communication, Microsoft Office proficiency. But that duplicates qualifications. Might be better to not create Skills section if it's just repeating qualifications. But we could still create Skills section with those abilities. However we need to avoid filler. The posting does have explicit skill statements: "Ability to analyze, problem solve, organize and manage multiple priorities...", "Ability to build and maintain effective professional relationships...", "Strong written and verbal communication abilities...", "Solid skills in Microsoft Office programs...". Those are skills. So we can create Skills section with those. Benefits: list: paid time off, 401K retirement plan, medical, dental, vision coverage, tuition reimbursement, many more voluntary benefit options. Also note benefits may vary based on employment status. Pay: compensation estimate $85,000-$100,000 annualized. Schedule: we have "Employment Status Full Time Shift Days". Not specific. Might omit. Thus final HTML:

      Responsibilities

      ...

      Qualifications

      • High school diploma
      • Five years' experience in Human Resources in a benefits, leave management or generalist related position, with a minimum three (3) years’ experience in interactive process administration.
      • Strong knowledge of federal and state leave and disability laws, specifically ADAAA, FEHA, PWFA, FMLA, CFRA, CA PDL, NJFLA; experience with CA leaves and accommodations is required.
      • Strong knowledge of the interplay between federal and state leave and disability laws.
      • Strong knowledge and understanding of absence management integrated workflows, return-to-work strategies, interactive process workflows.
      • Strong knowledge of benefits impacts while on leaves of absence.
      • Strong knowledge of leave of absence pay integrations with wage replacement benefits.
      • Ability to analyze, problem solve, organize and manage multiple priorities, and effectively follow up in a fast-paced environment.
      • Ability to build and maintain effective professional relationships through strong interpersonal skills including consistent demonstration of solid professional judgement.
      • Strong written and verbal communication abilities, including effective presentation skills to all levels of the organization.
      • Solid skills in Microsoft Office programs, including Excel, Word, PowerPoint, Outlook.

      Preferred Qualifications

      • Bachelor’s degree in Human Resources, Business Administration, or related field.
      • Experience working in a Healthcare environment with high volume of leave and accommodation cases.
      • Experience with Lawson, JBDev or leave case management software preferred.
      • Experience managing leave and accommodation across US.
      • Experience working in unions environments.
      But we only allowed headings from list; Preferred Qualifications not in list. Could we incorporate preferred qualifications under Qualifications? Probably better to keep Qualifications heading and include both required and preferred within that, maybe separate paragraphs. 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 we should stick to those. So we should not add Preferred Qualifications heading. Instead we can include preferred qualifications as part of Qualifications section, maybe as a note. Thus Qualifications section will contain both required and preferred. Skills section: we can extract skills: Ability to analyze, problem solve, organize and manage multiple priorities, follow up; Ability to build/maintain relationships; Strong written/verbal communication; Solid skills in Microsoft Office programs. Also maybe strong knowledge of laws etc but that's more knowledge than skill. We'll list those. Benefits section: list. Pay section: compensation estimate. We should not include schedule. We also need to include overview? Could be under "About the role". The overview describes the company, not the role. But maybe we can treat as "About the role" with a brief description of the role's purpose? The overview is about Prime Healthcare, not the role. However we could still put it under About the role as context. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid using About the role for company overview. Might be okay. But we need to ensure we don't create filler. The overview is substantive. So we can include

      About the role

      with a paragraph summarizing Prime Healthcare. Let's craft that: "Prime Healthcare is an award-winning health system headquartered in Ontario, California. It operates 54 hospitals and more than 360 outpatient locations across 15 states, serving over 3.0 million patient visits annually. The system employs over 60,000 employees and physicians, with twenty-one hospitals affiliated with the Prime Healthcare Foundation, a 501(c)(3) not-for-profit public charity." That's from overview. Now responsibilities as above. Qualifications: combine required and preferred. Skills: list. Benefits: list. Pay: compensation estimate. We must not include boilerplate: EEO, privacy, etc. Now produce HTML fragment. Make sure to use
      • for any list of duties/requirements/benefits. For responsibilities we could keep as

        but could also make list. The responsibilities paragraph is long; we could break into

        • for each duty. But the instruction: "Use
          • for any list of duties/requirements/benefits". It doesn't forbid using

            for prose. So we can keep responsibilities as

            . However we could also split into list for clarity. But we must