Project Manager, Sr.

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: 1. Job Brief/About the role - there's a "Job Brief" section with pay range and company description 2. Job Summary - describes the role 3. What You'll Bring To The Team - skills/qualities 4. Licensure & Certification 5. Education Required/Preferred 6. Experience Required/Preferred The pay range is given: $107,952.00 to $172,723.20 - this should go in a Pay section. I need to use

for section headings,

• for lists,

  for prose. Rules: - Don't repeat job title as heading (page already shows it) - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when posting has real, specific content - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Let me structure this: 1. About the role (or Job Summary) - the "Job Summary" paragraph 2. Responsibilities - but the posting doesn't have explicit responsibilities list, it has "What You'll Bring To The Team" which is more like qualifications/skills 3. Requirements/Qualifications - combine Licensure, Education, Experience 4. Skills - "What You'll Bring To The Team" could be skills 5. Pay - the pay range is given Actually, looking at the content: - "Job Brief" contains company description and pay range - "Job Summary" describes the role - "What You'll Bring To The Team" lists skills/qualities - "Licensure & Certification" lists required certifications - "Education Required/Preferred" lists education - "Experience Required/Preferred" lists experience I should create sections for: - About the role (Job Summary) - Responsibilities? Not explicitly listed, but the Job Summary describes what the role does. Could include that as prose. - Qualifications/Requirements - combine licensure, education, experience - Skills - "What You'll Bring To The Team" - Pay - the pay range But the rules say: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)" I need to map the content to these standard headings where appropriate. Let me think: - "About the role" - for the Job Summary paragraph - "Responsibilities" - the Job Summary describes responsibilities, but it's prose. Could put as

  under Responsibilities. - "Qualifications" or "Requirements" - for licensure, education, experience - "Skills" - for "What You'll Bring To The Team" - "Pay" - for the pay range The company description in Job Brief is more about the employer, not the role. The rules say "About the role" for section heading. The Job Summary is about the role. The company description could be part of "About the role" or omitted? The rules say "Preserve ALL substantive information". The company description is substantive but it's about the hospital, not the role. However, it's part of the job posting. I could include it as a preamble under "About the role" or as a separate "About the organization" but that's not in the example headings. The example headings include "About the role". I think I should include the company description as part of the context. But the rules: "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "PROJECT MANAGER" but the posting says "Senior Project Manager" in Job Summary. The pay range says "PROJECT MANAGER". I'll assume the title is known. I'll structure:

  About the role

  Company description...

  Job Summary...

  Responsibilities

  The Senior Project Manager serves as a senior project delivery and project governance leader within Information Services. The role independently leads complex, high-impact, cross-functional initiatives while helping establish and mature project governance, standards, processes, portfolio reporting, resource planning, and performance measures. The Senior Project Manager works across IS leadership and existing Project Managers to drive consistent project management practices, improve visibility into project priorities and resource capacity, and strengthen the successful delivery of organizational initiatives. The role provides mentorship and functional leadership to Project Managers and other project resources without direct supervisory responsibility.

  Skills

  • Expert understanding of project management methodologies, principles, and tools.
  • Strong leadership and team facilitation skills.
  • Excellent verbal and written communication skills.
  • Strong organizational and time management capabilities.
  • Advanced problem-solving and critical-thinking skills.
  • Ability to influence without direct authority.
  • Experience managing competing priorities in a dynamic environment.
  • Proficiency with Microsoft Office Suite, Project, Visio, SharePoint, and collaboration platforms.
  • Knowledge of change management and continuous improvement methodologies.

  Qualifications

  Licensure & Certification

  • Project Management or similar certification required (e.g., PMP, CAPM, PMI).

  Education

  • Required: Bachelor’s degree in business, Information Technology, Healthcare Administration, Engineering, or related field.
  • Preferred: Master’s degree in business administration, Healthcare Administration, Information Systems, or related discipline.

  Experience

  • Required: 7+ years of progressive healthcare IT project management experience leading complex cross-functional projects.
  • Required: Experience in managing full life cycle information systems projects, large scale systems development and/or information technology initiatives.
  • Required: Demonstrated experience presenting to executive leadership and steering committees.
  • Required: Demonstrated experience developing, implementing or improving project management methodologies, governance processes, standards, templates and reporting practices.
  • Required: Experience with project management methodologies and software tools.
  • Preferred: Experience managing large-scale technology implementations, infrastructure, cybersecurity, ERP, EHR, or digital transformation projects.
  • Preferred: Extensive clinical or financial system implementation knowledge and experience.
  • Preferred: Education of customers in system concepts and operation.

  Pay

  Opening pay range: $107,952.00 to $172,723.20 per year.

  But the rules say: "use

  for section headings" and "Use

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

    for prose." It doesn't mention

    . Should I use

    for subsections? The example headings are all

    . I could make "Licensure & Certification", "Education", "Experience" as separate

    sections, but that might be too many thin sections. The rules: "Prefer a few substantive sections over many thin ones." So better to group under one "Qualifications" heading with sub-lists. But the rules say "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid subheadings, but to keep it simple, I'll use

    for main sections and maybe or just list items with labels. I'll do:

    About the role

    ...company description...

    ...job summary...

    Responsibilities

    ...job summary text...

    Skills

    ...

    Qualifications

    • Licensure & Certification: Project Management or similar certification required (e.g., PMP, CAPM, PMI).
    • Education: Bachelor’s degree in business, Information Technology, Healthcare Administration, Engineering, or related field (required); Master’s degree in business administration, Healthcare Administration, Information Systems, or related discipline (preferred).
    • Experience: 7+ years of progressive healthcare IT project management experience leading complex cross-functional projects; experience managing full life cycle information systems projects, large scale systems development and/or information technology initiatives; demonstrated experience presenting to executive leadership and steering committees; demonstrated experience developing, implementing or improving project management methodologies, governance processes, standards, templates and reporting practices; experience with project management methodologies and software tools. Preferred: experience managing large-scale technology implementations, infrastructure, cybersecurity, ERP, EHR, or digital transformation projects; extensive clinical or financial system implementation knowledge and experience; education of customers in system concepts and operation.

    But that's a long list item. Better to break into separate

    under Qualifications with bold labels. Actually, the rules: "Use
    • for any list of duties/requirements/benefits". So I can have multiple
      under one

      . I'll do:

      Qualifications

      Licensure & Certification: Project Management or similar certification required (e.g., PMP, CAPM, PMI).

      Education:

      • Required: Bachelor’s degree in business, Information Technology, Healthcare Administration, Engineering, or related field.
      • Preferred: Master’s degree in business administration, Healthcare Administration, Information Systems, or related discipline.

      Experience:

      • Required: 7+ years of progressive healthcare IT project management experience leading complex cross-functional projects.
      • Required: Experience in managing full life cycle information systems projects, large scale systems development and/or information technology initiatives.
      • Required: Demonstrated experience presenting to executive leadership and steering committees.
      • Required: Demonstrated experience developing, implementing or improving project management methodologies, governance processes, standards, templates and reporting practices.
      • Required: Experience with project management methodologies and software tools.
      • Preferred: Experience managing large-scale technology implementations, infrastructure, cybersecurity, ERP, EHR, or digital transformation projects.
      • Preferred: Extensive clinical or financial system implementation knowledge and experience.
      • Preferred: Education of customers in system concepts and operation.
      That seems good. Now, the company description: "Your Work Here Matters... Ready to make your mark? Join the team that's been setting the standard for compassionate, innovative healthcare for nearly 50 years. Your next great chapter starts here." This is employer branding. Should I include it? The rules: "Preserve ALL substantive information". It is substantive about the employer. But the section is "About the role". Could include as a preamble. I'll include it as a paragraph under "About the role" before the job summary. Also, the pay range is in the Job Brief: "Opening Pay Range: PROJECT MANAGER - $107,952.00 to $172,723.20". I'll put that in Pay section. Now, check for any boilerplate to remove: The text includes "Your Work Here Matters. Your Career Here Thrives. Imagine coming to work every day knowing that what you do genuinely changes lives. At Henry Mayo Newhall Hospital, that's not just a tagline — it's the reality for every member of our team. We're