Project Manager-1

We need to output HTML fragment with sections only if content present. Must use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, accommodation contact, etc. Also remove navigation/legal etc. Keep substantive info. We need to parse the posting. Content: Intro paragraph: "If you’re looking for a special place to build or grow your career, you’ve found it. Whether you’re an experienced professional, a recent college graduate or somewhere in between, IDEX is a place where you can apply your existing skills and learn new ones in an environment where you can make an impact. With interesting opportunities in engineering, marketing, sales, supply chain, operations, HR, finance, and more across more than 40 diverse businesses (https://www.idexcorp.com/our-businesses/business-segments/) around the globe, chances are, we have something special for you." Then metadata: Reports to: Sr. Director, PMO Function: Project Management / Enterprise Execution / Strategic Initiatives Location: Remote Based in the US, Preferably in Eastern and Central time zones Travel: As needed to support project launches, milestone reviews, business leader working sessions, and implementation activities across the business footprint. We can fold minor metadata into a short

or drop it. Probably include a short paragraph with that info. Then "Role Summary" paragraph(s). Then "Key Outcomes" with bullet list (list of statements). Then "Core Responsibilities" with subheadings? Actually they have bullet points under categories: Lead Project Planning and Execution, Establish Governance, Cadence, and Accountability, Partner Cross-Functionally to Drive Results, Manage Risk, Issues, Dependencies, and Change, Support Business Prioritization and Value Creation, Communicate with Executive Presence, Build Repeatable PMO Tools and Practices. Each has multiple sentences. We can treat each as a list item under Responsibilities. Then "Required Qualifications" list. Then "Preferred Qualifications" list. Then "Working Conditions" paragraph. We need sections: About the role (maybe intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: we have intro paragraph and role summary. Could combine into About the role. - Responsibilities: core responsibilities list. - Requirements: maybe Required Qualifications. - Qualifications: maybe Preferred Qualifications? But we already have Required Qualifications as Requirements. Could treat Required Qualifications as Requirements, Preferred Qualifications as Qualifications? Or Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. We need to decide what goes where. Typically: Requirements = mandatory qualifications; Qualifications = preferred qualifications. Skills could be separate list of skills (maybe from required qualifications includes skills). But we can also put skills under Skills heading if we have explicit skill list. The posting includes skills like "Strong business acumen", "Excellent written and verbal communication", "Proven ability to influence without authority", "Strong analytical and problem-solving skills", "High comfort level operating in ambiguity", "Proficiency with project management tools, Microsoft Office applications, and project reporting methods." Those could go under Skills. But we can also incorporate them into Requirements. However instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Required Qualifications and Skills into Requirements? But we need to follow headings usage only if content present. We could have: - About the role (intro + role summary) - Responsibilities (core responsibilities) - Requirements (required qualifications) - Qualifications (preferred qualifications) - Skills (maybe we could extract skill statements from required qualifications and put them here, but that would duplicate). Better to put skills under Requirements or Qualifications? The heading list includes Skills as optional; we can omit if not needed. Since we already have Required Qualifications covering skills, we can omit Skills section. - Benefits, Pay, Schedule: not present (no specifics). So omit those sections. Thus output sections: About the role, Responsibilities, Requirements, Qualifications. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO, accommodation contact, etc. We need to include the link in About the role? The intro includes a link to businesses. Should we keep it? Yes, preserve all substantive information. So include the link as part of paragraph. We need to include metadata like Reports to, Location, Travel etc. Could be a short paragraph after About the role or within About the role. Probably best to include a short paragraph after the intro: "Reports to: Sr. Director, PMO. Function: Project Management / Enterprise Execution / Strategic Initiatives. Location: Remote (based in the US, preferably Eastern and Central time zones). Travel: As needed to support project launches, milestone reviews, business leader working sessions, and implementation activities across the business footprint." We need to ensure we don't repeat job title. Now craft HTML. Structure:

  About the role

  If you’re looking for a special place to build or grow your career, you’ve found it. Whether you’re an experienced professional, a recent college graduate or somewhere in between, IDEX is a place where you can apply your existing skills and learn new ones in an environment where you can make an impact. With interesting opportunities in engineering, marketing, sales, supply chain, operations, HR, finance, and more across more than 40 diverse businesses (https://www.idexcorp.com/our-businesses/business-segments/) around the globe, chances are, we have something special for you.

  Reports to: Sr. Director, PMO. Function: Project Management / Enterprise Execution / Strategic Initiatives. Location: Remote (based in the US, preferably Eastern and Central time zones). Travel: As needed to support project launches, milestone reviews, business leader working sessions, and implementation activities across the business footprint.

  Role Summary The Project Manager is responsible for leading cross-functional projects that translate strategic priorities into clear, actionable, and measurable execution plans. Reporting to the Sr. Director, PMO, this role will help drive disciplined project execution across the organization by defining project scope, milestones, deliverables, owners, risks, decision points, and success metrics. This role is designed for a highly resourceful, business-minded project leader who can operate effectively in ambiguity, influence without authority, and move seamlessly between strategic thinking and hands-on execution. The Project Manager will partner closely with business leaders, functional leaders, site teams, and initiative owners to ensure work is prioritized, resourced, governed, and executed with focus and accountability. The role will support execution of the organization’s critical priorities by building integrated project plans, establishing governance routines, tracking progress, escalating risks, and helping teams make practical trade-offs between competing priorities. The following role profile emphasizes converting strategic priorities into initiatives with clear outcomes, owners, milestones, and operating cadences, and this Project Manager role is intended to bring that same execution discipline to the PMO.

  Then Key Outcomes? Actually Key Outcomes could be part of Responsibilities? But we have a separate "Key Outcomes" section with bullet list. Could we treat that as part of Responsibilities? The instruction: Use
  • for any list of duties/requirements/benefits. The Key Outcomes list is a list of success metrics. Could be placed under Responsibilities or maybe a separate section like "Key Outcomes" but not in allowed headings. Since allowed headings are limited, we could incorporate Key Outcomes into Responsibilities as part of duties. But we need to preserve all detail; we can add a
    under Responsibilities for those outcome statements. Similarly Core Responsibilities have subheadings; we can flatten into a list. Thus Responsibilities section will contain multiple
    lists? Could have multiple
    each preceded by a

    heading? But we cannot add extra headings not allowed. We could just have one big

    with all responsibility items. However we need to keep the grouping? Not required. We can just list all responsibility statements as
    • . That would preserve all info. Similarly Required Qualifications as
      . Preferred Qualifications as
      . We need to ensure we don't lose any nuance like "Lead Project Planning and Execution" etc. We'll just include each sentence as a list item. Let's extract all responsibility statements: From "Lead Project Planning and Execution": - Translate strategic initiatives, business priorities, and functional objectives into integrated project plans with clear deliverables, timelines, milestones, owners, dependencies, and success metrics. - Develop and maintain project plans, workback schedules, risk logs, issue trackers, decision logs, stakeholder maps, and status reporting tools. - Ensure each project has a clearly defined scope, business case, expected outcomes, resource requirements, and governance model. - Drive execution discipline by ensuring project teams understand priorities, timing, decision rights, and accountabilities. - Proactively identify barriers to progress and work with leaders and team members to resolve issues quickly. - Maintain momentum across multiple workstreams while ensuring project teams remain focused on the highest-value activities. From "Establish Governance, Cadence, and Accountability": - Create and manage project governance routines, including project team meetings, steering committee updates, milestone reviews, decision forums, and escalation processes. - Ensure project progress is visible through consistent reporting, clear metrics, and timely communication. - Track actions, owners, decisions, risks, and dependencies to ensure accountability across the project team. - Escalate risks and decisions appropriately, ensuring leaders have the information needed to make timely and informed decisions. - Help reinforce disciplined operating routines so that project execution is embedded into how leaders manage the business, consistent with the attached document’s emphasis on cadence, governance, decision forums, and escalation paths. From "Partner Cross-Functionally to Drive Results": - Partner with business leaders, functional leaders, site leaders, and initiative owners to align project work with business priorities. - Coordinate across functions such as Operations, Finance, HR, Commercial, Continuous Improvement, IT, Supply Chain, and other business teams as needed. - Build strong working relationships across diverse stakeholder groups and influence progress without relying on direct authority. - Drive clarity on roles, responsibilities, decision rights, resource needs, and expected outcomes. - Facilitate alignment when priorities compete, information is incomplete, or stakeholders have differing perspectives. - Help leaders and teams make practical trade-offs regarding scope, timing, budget, resources, and value. From "Manage Risk, Issues, Dependencies, and Change": - Identify project risks, issues, dependencies, resource constraints, and potential execution gaps early. - Develop mitigation plans and partner with stakeholders to remove roadblocks. - Monitor project health and provide fact-based updates on schedule, scope, budget, quality, adoption, and business impact. - Anticipate the operational, financial, organizational, and people-related implications of project decisions. - Support change management activities by helping teams understand what is changing, why it matters, what is expected, and how success will be measured. - Ensure communication is clear, timely, and tailored to the needs of different stakeholder groups. From "Support Business Prioritization and Value Creation": - Apply strong business and financial acumen to understand how projects support growth, margin improvement, operational performance, productivity, customer outcomes, or organizational effectiveness. - Help teams focus work on the highest-value priorities and reduce effort on lower-value activities. - Use data, metrics, and business insights to inform project decisions, status updates, and recommendations. - Support project prioritization by helping leaders understand resource needs, trade-offs, timing implications, and execution risks. - Where applicable, help connect project work to 80/20 thinking, customer/product priorities, operational routines, and value-creation opportunities, reflecting the attached document’s focus on