Project Manager

We need to output HTML fragment with sections: About the role? The posting includes description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodation, etc. Also remove application instructions (none). Keep substantive info. We need to parse the posting. Key info: - Position: Full Time Project Manager for Rural Health Transformation Program (RHTP) in Vermont. - Primary Location: Live within the state of Vermont. Work will take place either in the field, in an office environment, or from a personal location and will depend on the need of the project. - Travel Requirements: This position will require travel to complete work assignments or attend meetings. - Essential Functions (list of duties). We'll put under Responsibilities. - Minimum Qualifications (list). We'll put under Requirements or Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include. We have: - About the role: could be introductory paragraph summarizing role. - Responsibilities: essential functions list. - Requirements: Minimum Qualifications (degree, experience, leadership, substitution, knowledge, etc.) - Qualifications: Preferred Qualifications (advanced degree, CMS experience, statistical software, etc.) - Skills: maybe combine some skill statements from requirements? Could include leadership, communication, analytical, etc. But we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they said use headings for those categories; we can include both if they have content. - Benefits: listing: 10 paid Holidays, Vacation Pay, Sick Pay, 401(K) plan with matching, Company paid STD and LTD. Also Salary range: $110,000 - $125,000 (based on experience and location). That's Pay. - Schedule: Not explicitly given. There's mention of full-time, but no schedule details. So we should not create Schedule section unless posting actually states them. It does not give schedule details like hours, shift, etc. So omit Schedule. - Pay: we have salary range. So include Pay section. - Benefits: include Benefits section. - About the role: we can include a short paragraph summarizing role. - Responsibilities: list of essential functions. - Requirements: Minimum Qualifications. - Qualifications: Preferred Qualifications. - Skills: maybe we can extract skill statements from requirements: Strong leadership and team management skills, Excellent communication and stakeholder engagement skills, Ability to prioritize and manage multiple projects, Analytical and strategic thinking abilities, Demonstrated proficiency in data interpretation and basic statistical analysis. Those could go under Skills. But they also appear in Requirements. To avoid duplication, we could put them under Skills and keep Requirements focused on degree/experience. However the instruction says preserve ALL substantive information; we must not lose any. So we need to include those skill statements somewhere. If we put them under Skills, we still preserve. If we also keep them under Requirements, that's duplication but maybe okay? The instruction didn't forbid duplication, but we should avoid unnecessary repetition. Better to split: Requirements: degree, experience, leadership, substitution, knowledge of federal grant regulations. Skills: leadership, communication, prioritization, analytical thinking, data interpretation, statistical methods. But note that the Minimum Qualifications also includes "Strong leadership and team management skills..." etc. Those are skills. So we can move them to Skills. Let's extract: Minimum Qualifications bullet points (as paragraph): - Degree: Bachelor's degree in a relevant field, such as public health, public administration, etc. - Experience: Ten (10) or more years in health project / program administration and grant management, preferably at the local, tribal, or state government level(s). - Leadership: Five (5) or more years of supervisory experience. - Experience and Degree Substitution: An equivalent combination of experience and training that demonstrates the required knowledge, skills, and abilities necessary to effectively perform the duties and functions of this position may be considered in lieu of a degree. - Knowledge of and demonstrated experience with federal grant regulations and compliance requirements, particularly related to the Rural Health Transformation Program and/or state and other applicable federal grant funding requirements. Then after that there is a paragraph: "Strong leadership and team management skills to inspire and guide project teams towards program goals.Excellent communication and stakeholder engagement skills to foster partnerships and collaboration. Ability to prioritize and manage multiple projects simultaneously in a dynamic environment.Analytical and strategic thinking abilities, grounded in data literacy and statistical reasoning, to identify opportunities for project improvement, measure program impact, and drive evidence-based innovation.Demonstrated proficiency in data interpretation and basic statistical analysis, including experience working with datasets, performance dashboards, or analytical tools (e.g., Excel pivot tables, Tableau, Power BI, or equivalent) to support program evaluation and reporting." That seems like skills. Preferred Qualifications: - Degree: Master of Public Health, Master of Public Administration, or an advanced degree in a related field. - Demonstrated work with Centers for Medicare & Medicaid Services (CMS) programs, rural health initiatives, or large-scale federal health grants. - Experience with Statistical software or data analysis platforms (e.g., SPSS, SAS, R, Stata, or advanced Excel functions) and familiarity with health-related data sources such as CMS datasets, HRSA reporting systems, or state health information exchanges. Now Benefits: - 10 paid Holidays - Vacation Pay - Sick Pay - 401 (K) plan with matching - Company paid STD and LTD Pay: - Salary will be based on experience and location: $110,000 - $125,000 Now About the role: we can summarize: "IEM is seeking a Full-Time Project Manager to develop and execute a comprehensive program strategy for a state's Rural Health Transformation Program (RHTP). The role involves working with IEM teams under client direction to promote operational change, establish new processes, and integrate existing state systems. Primary location: must reside in Vermont; work may be field, office, or remote as needed, with travel required." Now Responsibilities: list essential functions as bullet list. Let's list them: - Manage the implementation of RHTP projects / program as determined by the state, including day-to-day program governance and oversight of the grant. This includes issue escalation, recommendations and decision support to state leadership. - Monitor project timelines, budgets, and performance metrics to ensure successful delivery and compliance with all federal and state funding and grant management guidelines. - Identify risks, propose mitigation strategies and prepare the projects for audit readiness from the beginning. - Coordinate with internal and external stakeholders to align project activities with program objectives and funding requirements. - Collaborate with state leadership and community partners (as needed) to enhance program effectiveness and sustainability. - Lead a team of project staff (coordinators / analysts, etc.) to support the execution of program activities and deliverables. - Prepare and present program updates and reports to key stakeholders, including progress reports, budget analysis, and impact assessments. - Evaluate program outcomes and impact on rural health systems / programs / infrastructure in the state. - Remain flexible and available to operate within the dynamic needs of a multi-year project that may evolve and require additional or different efforts. - Collect, organize, and analyze quantitative and qualitative program data (including grant expenditure rates, population health indicators, and service-utilization metrics) to evaluate project performance against established benchmarks and inform evidence-based recommendations to state leadership. - Interpret statistical reports, dashboards, and data visualizations produced by internal analysts or external evaluators, translating findings into actionable insights for non-technical stakeholders and incorporating those insights into program strategy adjustments. - Apply basic statistical methods (e.g., descriptive statistics, trend analysis, variance analysis) to monitor key performance indicators, validate data integrity in grant reporting, and support audit-readiness documentation with defensible, data-driven narratives. Now we need to output HTML fragment with headings

and

• for lists,

  for prose. We must not include any markdown fences. We'll produce something like:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  Salary will be based on experience and location: $110,000 - $125,000

  We should not include Schedule. Check that we didn't repeat job title as heading. Good. We removed EEO boilerplate etc. Now ensure we preserve all substantive information: Did we miss anything? Let's review original text for any other details: - "Primary Location: Live within the state of Vermont.Work will take place either in the field, in an office environment, or from a personal location and will depend on the need of the project." We included that in About the role. - "Travel Requirements This position will require travel to complete work assignments or attend meetings." We could include that in About the role or Responsibilities. Probably include in About the role: mention travel required. - "Essential Functions" list we captured. - "Minimum Qualifications" we captured. - "Experience and Degree Substitution" we captured. - "Knowledge of and demonstrated experience with federal grant regulations..." captured. - After that we have the skills paragraph; we moved to Skills. - "Preferred Qualifications" captured. - "Additional Information Office Locations: Often, these offices are either owned by the client we work with or by IEM. All candidates are expected to follow any rules and regulations of the office in which they are required to work for that project." This is somewhat generic; could be considered boilerplate? It's about office locations. Might be considered not essential? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's generic office location info. Might be considered not substantive? However it's about office locations; could be considered relevant but not critical. The instruction says preserve ALL substantive information. Is this substantive? It says "Office Locations: Often, these offices are either owned by the client we work with or by IEM. All candidates are expected to follow any rules and regulations of the office in which they are required to work for that project." That's somewhat generic but could be considered part of Additional Information. Might be okay to keep? But we have no section for Office Locations. Could we include under About the role? Might be too detailed. The instruction says prefer a few substantive sections over many thin ones. So we could omit this as it's not critical. However it's substantive info about office locations and compliance. But we already have location (Vermont) and remote/work flexibility. The office location rule is generic; maybe we can drop as it's not unique. I'd lean to omit to keep sections thin. - "Personal Office / At Home Locations: All personal office / at home work environments require the ability to maintain minimum Internet speeds of 25 Mbps upload and 3 Mbps download, as well as a ping rate of 100 ms or less during working hours, regardless of the type and number of devices using your Internet connection. You must also have account privileges and access to your Internet service provider account during working hours for the purposes of maintaining the Internet connection, if needed." This is substantive about remote work requirements. Should we include? It's about remote work requirements. Could be included under About the role or maybe a separate section like "Remote Work Requirements". But we don't have a heading for that; we could incorporate into About the role. The