Senior Project Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes JOB SUMMARY/PURPOSE, DEPARTMENT DESCRIPTION, EXPERIENCE/EDUCATION/QUALIFICATIONS, KNOWLEDGE/SKILLS/ABILITIES, PHYSICAL DEMANDS (but that seems like a table with categories). We need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the 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. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - JOB SUMMARY/PURPOSE: description of role, responsibilities. Could map to "About the role" or "Responsibilities". We'll use

  About the role

  with prose. - DEPARTMENT DESCRIPTION: description of department. Could be part of About the role or separate "Department". Not in list of allowed headings but we can still use

  Department

  ? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use other headings? Probably we should stick to those headings where applicable. Department description could be part of About the role. But we could also create a separate heading like "Department". 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 those are typical. Safer to use those headings only. We can embed department description within About the role paragraph. - EXPERIENCE/EDUCATION/QUALIFICATIONS: This is qualifications and requirements. Could map to "Requirements" and "Qualifications". We'll need to split maybe into Requirements (experience/education) and Qualifications (certifications). But we can combine into one section "Requirements". Use

  • for list. - KNOWLEDGE/SKILLS/ABILITIES: This is skills. Use heading "Skills". Use
    • . - PHYSICAL DEMANDS: This is a table of physical demands with categories and frequencies. This is substantive content. There's no standard heading for that; maybe we can use "Physical Demands". Not in examples but we can still use

      Physical Demands

      . The instruction didn't forbid other headings; it just gave examples. It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use other headings as needed. We'll include Physical Demands. We must not include Pay, Schedule, Benefits unless present. Not present. We must not include filler like "commensurate with experience". Not present. We need to preserve all substantive information. Let's extract. JOB SUMMARY/PURPOSE text: "Occasionally JOB SUMMARY/PURPOSELeads enterprise level projects, programs, and portfolios across SHS. Completes and manages the creation of project documentation, facilitates large and complex project teams, tracks project-related tasks, milestones and resources. Manages scope, effort, budget, and timeline within assigned areas. Leads other project managers to understand impact of projects on other initiatives and mitigate risk across the organization. May act in the role of a business consultant working with senior administration to define strategic goals and associated plans. May lead projects related to construction, new business development, system implementations, process improvement and/or operational assistance. Defines, emulates, and follows defined PMO methodologies and templates. Assists with updates and changes to the defined methodologies and templates. Works closely with all levels within SHS, including all levels of management, primarily senior administration." Note there is weird "Occasionally JOB SUMMARY/PURPOSE". Probably a formatting artifact. We'll ignore "Occasionally". We'll keep the rest. DEPARTMENT DESCRIPTION: "The Strategy & Planning department manages the comprehensive project portfolio for the organization and also oversees the Project Governance Process at SHS which ensures alignment between the system goals and the project portfolio. The team works closely with all levels of leadership in the organization and provides project management, project consulting, business planning, strategy development and continuous improvement leadership." EXPERIENCE/EDUCATION/QUALIFICATIONS: "Bachelor’s degree in a related field (e.g., Business, Healthcare, or Information Technology) required. Master’s degree preferred.Project Management Professional (PMP) Certification required within one (1) year of hire. Seven (7) years of project management experience required.Experience leading complex organization-level initiatives required.Experience in Lean, Operational Improvement, and Organizational Change Management/Development preferred.Experience in a healthcare setting preferred." We need to split into list items. KNOWLEDGE/SKILLS/ABILITIES: Long list of abilities. We'll extract each sentence as list item. Let's list them: - Understands project management basics, work breakdown structures, meeting facilitation, timelines, roles and responsibilities, negotiating for resources and timelines, change management and risk identification. - Ability to read a room, lead teams, present to all levels of an organization. - Ability to modify approach based on situations and individuals involved. - Ability to help define what “done” is and focus on driving to completion. - Ability to keep teams and stakeholders moving towards a goal while listening to their needs and keeping them involved. - Ability to coordinate multiple tasks and projects with minimal supervision. - Ability to identify needs, tasks, risks, issues early and make sure to follow through on action items and communication within assigned projects. - Ability to develop solutions that address the need not just the ask. - Ability to communicate at all levels of the organization, both written and verbal. - Ability to diffuse and resolve conflict within assigned projects. - Ability to understand how projects interact across multi-disciplinary departments. - Ability to understand, communicate and facilitate the needs across the system and not focus on a single area. We'll put each as

      . PHYSICAL DEMANDS: We have a list of activities with frequency categories: Rarely (1 - 10% of the time), (11 - 33% of the time), Frequently (34 - 66% of the time), Continually (67 - 100% of the time). Then each activity with a level? Actually the format: PHYSICAL DEMANDS Rarely (1 - 10% of the time) (11 - 33% of the time) Frequently (34 - 66% of the time) Continually (67 - 100% of the time) CLIMB - STAIRS LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs LIFT (Knee to chest: 24"-54") 0 - 20 Lbs LIFT (Waist to Eye: up to 54") 0 - 20 Lbs CARRY 1-handed, 0 - 20 pounds BEND FORWARD at waist CARRY 2-handed, 0 - 20 pounds KNEEL (on knees) STAND WALK - LEVEL SURFACE ROTATE TRUNK Standing REACH - Upward PUSH (0-20 pounds force) PULL (0-20 pounds force) SIT ROTATE TRUNK Sitting REACH - Forward MANUAL DEXTERITY Hands/wrists FINGER DEXTERITY PINCH Fingers GRASP Hand/Fist None specified It seems like they attempted to map each activity to a frequency column but got messed up. We need to preserve all substantive information; we can present as a definition list or a table? The instruction says use

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

        for prose. For physical demands, it's not a list of duties/requirements/benefits but a table. We could still use

        • each activity with its frequency? But the frequencies are ambiguous. Perhaps we can present as a but not prohibited. The instruction only says use
          • for any list of duties/requirements/benefits, and

            for prose. It doesn't forbid tables for other content. So we can use a table to represent physical demands. We'll create a table with two columns: Activity, Frequency (or level). But the data is messy. Let's try to parse: The header line: "Rarely (1 - 10% of the time) (11 - 33% of the time) Frequently (34 - 66% of the time) Continually (67 - 100% of the time)" seems to have duplicated Rarely ranges? Actually maybe they meant columns: Rarely (1-10%), Occasionally (11-33%), Frequently (34-66%), Continually (67-100%). But they wrote Rarely twice. We'll interpret as four columns: Rarely (1-10%), Occasionally (11-33%), Frequently (34-66%), Continually (67-100%). Then each activity likely has a checkmark under one of those columns, but the text after header seems to list activities with some numbers. Let's examine after header: "CLIMB - STAIRS LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs LIFT (Knee to chest: 24"-54") 0 - 20 Lbs LIFT (Waist to Eye: up to 54") 0 - 20 Lbs CARRY 1-handed, 0 - 20 pounds BEND FORWARD at waist CARRY 2-handed, 0 - 20 pounds KNEEL (on knees) STAND WALK - LEVEL SURFACE ROTATE TRUNK Standing REACH - Upward PUSH (0-20 pounds force) PULL (0-20 pounds force) SIT ROTATE TRUNK Sitting REACH - Forward MANUAL DEXTERITY Hands/wrists FINGER DEXTERITY PINCH Fingers GRASP Hand/Fist None specified" It seems each activity is followed by some description and maybe a frequency indicator missing. Eg "CLIMB - STAIRS" then "LIFT (Floor to Waist: 0"-36") 0 - 20 Lbs" maybe that's a separate activity? Actually it's confusing. Given the ambiguity, perhaps we should just preserve the physical demands section as a block or as a

            containing the raw text. The instruction says use

            for prose. So we can put the physical demands block inside a

            . That preserves all info without trying to interpret. Thus we will have:

            Physical