Program Manager

We need to output HTML fragment with sections: About the role (maybe from Position Overview), Responsibilities (Essential Duties And Responsibilities), Requirements (Qualifications), maybe Skills (if present), Benefits (none), Pay (none), Schedule (none). We must only include sections when posting has real specific content. The posting includes Position Overview (we can treat as About the role). It includes Essential Duties And Responsibilities (list). It includes Required Qualifications (education, experience, etc.) and Preferred Qualifications. We can combine qualifications into Requirements section. Skills maybe not separate; but we could include Skills if present: they mention Strong communication, organization, facilitation, problem-solving skills; proficiency with tools. Could be part of Requirements. But we can create a Skills section if we want, but we need real specific content. The posting includes those skill statements under Required Qualifications. Could extract them into Skills section. However we must not repeat job title as heading. Also we must not include Job ID etc. We'll include a short p for metadata maybe location? The location is given: MURC - Marshall University Research Corporation. Could be placed in a p under About the role or separate? Probably include location in About the role paragraph. We must not include boilerplate like Posting Detail Information, Posting Number, Open Date, Close Date, Special Instructions, Supplemental Questions, Applicant Documents Required, etc. Remove those. We must preserve all substantive information: Position Overview, Essential Duties And Responsibilities (list), Required Qualifications (education, experience, skills, proficiency), Preferred Qualifications (education, experience). Also Salary Range: "Salary is commensurate with education, experience, and internal equity" - that's not specific; we should not create Pay section because it's not specific (commensurate). So we omit Pay. Benefits: none. Schedule: none. Thus sections: About the role (h3), Responsibilities (h3), Requirements (h3), maybe Preferred Qualifications could be part of Requirements or separate? Could combine but we could have Requirements and Preferred Qualifications as subheadings? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can have Qualifications as a heading. But we already have Requirements. Could use Requirements for required qualifications, and maybe a separate Skills section for skill statements. But we can also include both required and preferred under Requirements. However we need to avoid thin sections. Let's create:

About the role

Position Overview ... plus location maybe.

Responsibilities

• ... each duty as list items. Need to capture all duties from Essential Duties And Responsibilities. That's a long list with sub-bullets. We'll need to break into list items preserving content. Could group by major categories: Project Planning and Operational Management, Team and Partner Coordination, Clinical and Research Project Delivery, Resources and Technology, Performance Reporting and Quality Improvement, Budget and Funding Management. Each category could be a list item with sub-details maybe as sentences. But we must preserve ALL substantive information; we can't omit details. We could embed sub-details within each list item as sentences. That's okay. We need to ensure we don't lose any detail. Let's extract the duties: Under "Project Planning and Operational Management": - Develop and maintain project plans that define scope, objectives, tasks, accountable leads, milestones, dependencies, and deadlines. - Coordinate activities from project initiation and launch through implementation, evaluation, transition, and closeout. - Manage competing priorities across projects, identify shared resource needs, and resolve scheduling or capacity conflicts with leadership. - Track changes to scope, timelines, and resources through established approval processes. - Coordinate launch readiness, including staffing, training, facilities, equipment, systems, approvals, and documentation appropriate to each project. - Maintain standard operating procedures, implementation tools, meeting records, and decision logs. - Track risks and issues, assign owners and mitigation actions, and escalate barriers that threaten safety, quality, budgets, or delivery. Under "Team and Partner Coordination": - Serve as the operational liaison among clinical and research teams, participating sites, institutional departments, community organizations, sponsors, and other partners. - Clarify responsibilities, coordinate work across disciplines, monitor agreed deliverables, and address operational barriers. - Support recruitment, onboarding, training, and workload planning for project staff as assigned. - Organize project meetings, document decisions, and follow up on action items. - Develop orientation materials and training resources with subject-matter experts to support consistent implementation. Under "Clinical and Research Project Delivery": - Coordinate project-specific workflows for outreach, referral, recruitment, enrollment, consent documentation, service delivery, data collection, and follow-up, as applicable. - Support implementation of approved clinical pathways, study protocols, and evaluation plans. - Coordinate required institutional and regulatory submissions with investigators and designated compliance teams, and track approvals, renewals, and training. - Monitor participation, engagement, retention, and completion where relevant. - Work with clinical, research, and community teams to address access barriers and improve the patient or participant experience. - Escalate safety concerns, protocol deviations, and unresolved service or communication gaps to the responsible clinical or research lead. - Track operational follow-up and corrective actions through resolution. Under "Resources and Technology": - Coordinate purchasing, equipment and supply needs, vendor deliverables, service agreements, and technical support with the relevant institutional teams. - Support implementation and testing of project systems, including data-collection platforms, electronic health record workflows, or digital health tools where applicable. - Coordinate user training and contingency procedures. - Work with legal, privacy, security, and data teams to establish appropriate agreements, access permissions, secure information exchange, and records management. Under "Performance Reporting and Quality Improvement": - Work with analysts, investigators, and program leads to define project measures, maintain dashboards, and track progress against milestones, deliverables, and intended outcomes. - Prepare accurate progress reports, presentations, and supporting documentation for leadership, sponsors, funders, and institutional stakeholders according to project requirements and deadlines. - Identify performance gaps, coordinate reviews of their causes, assign improvement actions, and assess results. - Communicate data limitations, delivery risks, and decisions requiring leadership input. - Support evaluation, dissemination of findings, and preparation of project reports, presentations, manuscripts, or funding proposals in collaboration with the responsible teams. Under "Budget and Funding Management": - Develop and monitor project budgets with program leads, finance, and grants administration. - Track expenditures, commitments, invoices, staffing allocations, and variances; maintain documentation for review and audit. - Coordinate compliance with funding terms and institutional financial procedures, including required reports and approved budget changes. - Ensure costs are allocated appropriately across projects and funding sources, with no duplicate charging. - Support sustainability planning, resource forecasting, and future funding opportunities. - Coordinate project closeout, transfer of ongoing activities, and documentation of lessons learned for subsequent projects. We'll put each bullet as
• . Now Requirements: include education, experience, skills, proficiency. Let's extract: Required Qualifications: Education: Bachelor’s degree in healthcare administration, public health, business administration, nursing, health sciences, or a related field. Experience: At least five years of progressively responsible experience in program management, healthcare operations, clinical research, public health, or a related area, including at least two years leading projects or multidisciplinary teams. Demonstrated ability to manage project plans, budgets, deliverables, risks, and partner relationships, and to coordinate multiple priorities and deadlines. Experience with performance reporting, project documentation, and budget tracking in a healthcare, research, academic, or public health setting. Strong communication, organization, facilitation, and problem-solving skills; ability to interpret performance data and collaborate effectively with clinical, research, administrative, and community partners. Proficiency with project-management tools, spreadsheets, presentations, and collaborative systems; knowledge of confidentiality, secure data handling, and applicable institutional procedures. Preferred Qualifications: Education: Master’s degree in a relevant field; Project Management Professional (PMP) or comparable certification. Experience: Experience with grant-funded programs, clinical research, quality improvement, or implementation of new clinical or community services. Experience in diabetes, obesity, cardiometabolic disease, digital health, or rural and underserved populations; familiarity with research oversight, healthcare reimbursement, or sustainability planning. We could combine required and preferred into Requirements section, maybe separate subheadings? But we only allowed h3 headings; we could have

  Requirements

  and inside we could have

  ?? Not allowed? The instruction only mentions h3 for section headings; doesn't forbid other headings but says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those exact headings. So we should use Requirements for required qualifications, and maybe Skills for skill statements, Qualifications for preferred? But we have both required and preferred. Could treat Requirements as required qualifications, and Qualifications as preferred? Or we could include both under Requirements and not have a separate Qualifications section. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It's a list of examples, not mandatory to use all. So we can choose which sections to include based on content. We have content for About the role, Responsibilities, Requirements (required qualifications), Skills (maybe we can extract skill statements), and maybe Qualifications (preferred). But we need to avoid thin sections. Let's see if we can make a meaningful Skills section: we have "Strong communication, organization, facilitation, and problem-solving skills; ability to interpret performance data and collaborate effectively with clinical, research, administrative, and community partners." and "Proficiency with project-management tools, spreadsheets, presentations, and collaborative systems; knowledge of confidentiality, secure data handling, and applicable institutional procedures." That's substantive enough for a Skills section. We could then put required education and experience under Requirements, and preferred under Qualifications. That seems reasonable. Thus sections:

  About the role

  Position Overview ... plus location.

  Responsibilities

  ...

  Requirements

  Education: Bachelor’s degree in healthcare administration, public health, business administration, nursing, health sciences, or a related field.

  Experience: At least five years of progressively responsible experience in program management, healthcare operations, clinical research, public health, or a related area, including at least two years leading projects or multidisciplinary teams.

  Demonstrated ability to manage project plans, budgets, deliverables, risks, and partner relationships, and to coordinate multiple priorities and deadlines.

  Experience with performance reporting, project documentation, and budget tracking in a healthcare, research, academic, or public health setting.

  Skills

  Strong communication, organization, facilitation, and problem-solving skills; ability to interpret performance data and collaborate effectively with clinical, research, administrative, and community partners.

  Proficiency with project-management tools, spreadsheets, presentations, and collaborative systems; knowledge of confidentiality, secure data handling, and applicable institutional procedures.

  Qualifications

  Preferred education: Master’s degree in a relevant field; Project Management Professional (PMP) or comparable certification.

  Preferred experience: Experience with grant-funded programs, clinical research, quality improvement, or implementation of new clinical or community services.

  Preferred experience: Experience in diabetes, obesity, cardiometabolic disease, digital health, or rural and underserved populations; familiarity with research oversight, healthcare reimbursement, or sustainability planning.

  We must not include Pay/Benefits/Schedule sections. Check that we preserved all substantive info: Did we miss any details from Required Qualifications like "Strong communication, organization, facilitation, and problem-solving skills; ability to interpret performance data and collaborate effectively with clinical, research, administrative, and community partners." and "Proficiency with project-management tools, spreadsheets, presentations, and collaborative systems; knowledge of