Sr. Manager, IT Project Manager

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

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to include sections based on content. The posting includes: "The Role" description (prose). Could map to "About the role". Responsibilities: many bullet points under "Key Responsibilities". Requirements: maybe "Required Skills & Qualifications". Qualifications: maybe same as required skills? We can combine. Skills: maybe list of capabilities. Benefits: none given. Pay: none. Schedule: mention "Fidelity’s Onsite Working Model" - mentions onsite expectations. That could be schedule info. So we can include Schedule section with that content. We must not include boilerplate like immigration sponsorship note? That's minor metadata; we can fold into short p or drop. The note "Fidelity is not providing immigration sponsorship for this position" is minor metadata; we can include in a short p maybe under About the role? Probably drop as it's not substantive? It's a note but maybe minor metadata; we can fold into short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short p for that note. Also "Certifications Category: Information Technology" maybe minor metadata; could be dropped. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all responsibilities bullet points, required skills, etc. We must not create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's structure:

About the role

... The Role paragraph ... plus maybe the note about immigration sponsorship as a short p? Could combine. Better:

The IT Project Manager drives and is accountable for delivery outcomes across one or more technology projects, teams, or complex initiatives, partnering primarily with engineering and technology leaders and collaborating with product and program partners to align priorities and outcomes. Responsible for planning, tracking, and driving coordinated delivery across dependencies, risks, releases, and status. Ensures alignment across teams to execute against commitments with strong predictability, transparency, and delivery discipline. By modeling Fidelity leadership behaviors and adaptive ways of working, the IT Project Manager helps advance an innovative and collaborative delivery culture.

Note: Fidelity is not providing immigration sponsorship for this position.

Then Responsibilities:

Responsibilities

with each bullet. We need to capture all bullet points under Key Responsibilities. They are grouped under headings: Planning and Coordination, Execution and Delivery Management, Continuous Improvement and Predictability, Technology and Quality Oversight, Team Leadership and Culture. We can just list each bullet as
• . Ensure we keep the text exactly as given. Let's extract bullet points: Under Planning and Coordination: - Lead and drive project scope, objectives, and delivery roadmaps for multiple projects or complex initiatives with significant dependencies. - Drive development and maintenance of realistic delivery plans, balancing scope, timelines, capacity, and dependencies to improve predictability and inform trade-off decisions. - Partner with product, program, and technology leaders to drive integrated planning, prioritization, and sequencing across teams. - Establish and maintain transparent delivery plans and documentation, ensuring visibility across stakeholders. - Drive alignment of delivery plans with product, business, and technology priorities, facilitating trade-offs to maintain delivery momentum. Execution and Delivery Management: - Own and drive execution across projects or complex initiatives, ensuring alignment, sequencing, and progress across participating teams. - Ensure clarity of priorities, timelines, and dependencies so work advances predictably across teams. - Track, analyze, and communicate delivery progress and health using metrics and indicators, identifying trends, risks, and actionable insights to guide decisions and course corrections. - Proactively manage and resolve risks and dependencies, including complex cross-team dependencies. - Drive accountability for delivery outcomes, ensuring milestones, quality standards, and business objectives are achieved. - Orchestrate communication and coordination across teams and stakeholders to maintain alignment, remove blockers, and proactively drive delivery outcomes across teams. - Leverage delivery events and routines to drive decision-making, alignment, and forward progress. Continuous Improvement and Predictability: - Drive continuous improvement of delivery practices and processes, using delivery data and insights to improve predictability and efficiency. - Optimize workflows and coordination across teams, reducing delivery friction and improving throughput and flow. - Use delivery data, retrospectives, and trends to improve planning accuracy, forecasting reliability, and execution consistency. Technology and Quality Oversight: - Ensure adherence to engineering and quality standards across delivery, including defect management, technical debt tracking, and change processes. - Drive adoption and ensure consistent application of Software Development Lifecycle (SDLC) practices, including effective use of AI-assisted development tools and workflows. - Own and ensure end-to-end release readiness across projects or initiatives, coordinating across teams and stakeholders to align dependencies, timelines, and quality expectations. Team Leadership and Culture: - Foster a collaborative environment that promotes ownership, accountability, and transparency, while enabling teams to operate with autonomy, leverage their expertise, and take responsibility for outcomes. - Drive accountability and alignment across teams, reinforcing delivery expectations and standards. - Influence teams and stakeholders to adopt modern iterative delivery practices and continuously improve ways of working. - Support onboarding, development, and continuous learning across teams. Now Required Skills & Qualifications: we can split into Requirements and Qualifications maybe. But we have sections: Requirements, Qualifications, Skills. The posting has "Required Skills & Qualifications" with subheadings: Experience and Education, Project And Professional Capabilities, plus maybe "The Team" description. We could put Experience and Education under Requirements, Project And Professional Capabilities under Skills, and maybe The Team under Qualifications? But Qualifications maybe similar to Requirements. However we should not create thin sections. Perhaps combine Requirements and Qualifications into one section? But we have to follow instruction: use headings only if real specific content. We could have:

  Requirements

  Experience and Education: Bachelor’s degree in Business, Technology, or related field (or equivalent experience). 5-7 years of experience in project or delivery management roles. Experience leading delivery across multiple teams, using modern iterative practices in a large enterprise environment.

  Skills

  list of Project And Professional Capabilities items. We could also have a

  Qualifications

  maybe not needed if we covered. But we have "The Team" description which is more about team culture; could be Qualifications? Actually it's description of team, not a qualification for candidate. Could be omitted as not required for candidate? It's substantive about team but not a requirement. Might be considered "About the team" but we don't have a heading for that. Could include under About the role? Probably not needed. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep The Team description somewhere. Could add a

  Team

  but not in allowed headings list. Allowed headings are only those specified: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we must fit content into those headings. The Team description could go under Qualifications? Or maybe under About the role? It's about the team, not the role. Could be placed under Qualifications as "Team environment". But Qualifications heading is for candidate qualifications; but we can still put descriptive text there as long as it's not filler. Might be acceptable. Alternatively, we could omit The Team description? That would be losing substantive info. So we need to include it somewhere. Perhaps under Qualifications we can add a paragraph describing the team. Similarly, "Fidelity’s Onsite Working Model" is schedule info; we can put under Schedule. We also have "Certifications Category: Information Technology" maybe minor metadata; could be dropped. Now Benefits, Pay: none given, so we should not create those sections. Thus final HTML:

  About the role

  The IT Project Manager drives and is accountable for delivery outcomes across one or more technology projects, teams, or complex initiatives, partnering primarily with engineering and technology leaders and collaborating with product and program partners to align priorities and outcomes. Responsible for planning, tracking, and driving coordinated delivery across dependencies, risks, releases, and status. Ensures alignment across teams to execute against commitments with strong predictability, transparency, and delivery discipline. By modeling Fidelity leadership behaviors and adaptive ways of working, the IT Project Manager helps advance an innovative and collaborative delivery culture.

  Note: Fidelity is not providing immigration sponsorship for this position.

  Responsibilities

  • Lead and drive project scope, objectives, and delivery roadmaps for multiple projects or complex initiatives with significant dependencies.
  • Drive development and maintenance of realistic delivery plans, balancing scope, timelines, capacity, and dependencies to improve predictability and inform trade-off decisions.
  • Partner with product, program, and technology leaders to drive integrated planning, prioritization, and sequencing across teams.
  • Establish and maintain transparent delivery plans and documentation, ensuring visibility across stakeholders.
  • Drive alignment of delivery plans with product, business, and technology priorities, facilitating trade-offs to maintain delivery momentum.
  • Own and drive execution across projects or complex initiatives, ensuring alignment, sequencing, and progress across participating teams.
  • Ensure clarity of priorities, timelines, and dependencies so work advances predictably across teams.
  • Track, analyze, and communicate delivery progress and health using metrics and indicators, identifying trends, risks, and actionable insights to guide decisions and course corrections.
  • Proactively manage and resolve risks and dependencies, including complex cross-team dependencies.
  • Drive accountability for delivery outcomes, ensuring milestones, quality standards, and business objectives are achieved.
  • Orchestrate communication and coordination across teams and stakeholders to maintain alignment, remove blockers, and proactively drive delivery outcomes across teams.
  • Leverage delivery events and routines to drive decision-making, alignment, and forward progress.
  • Drive continuous improvement of delivery practices and processes, using delivery data and insights to improve predictability and efficiency.
  • Optimize workflows and coordination across teams, reducing delivery friction and improving throughput and flow.
  • Use delivery data, retrospectives, and trends to improve planning accuracy, forecasting reliability, and execution consistency.
  • Ensure adherence to engineering and quality standards across delivery, including defect management, technical debt tracking, and change processes.
  • Drive adoption and ensure consistent application of Software Development Lifecycle (SDLC) practices, including effective use of AI-assisted development tools and workflows.
  • Own and ensure end-to-end release readiness across projects or initiatives, coordinating across teams and stakeholders to align dependencies, timelines, and quality expectations.
  • Foster a collaborative environment that promotes ownership, accountability, and transparency, while enabling teams to operate with autonomy, leverage their expertise, and take responsibility for outcomes.
  • Drive accountability and alignment across teams, reinforcing delivery expectations and standards.
  • Influence teams and stakeholders to adopt modern iterative delivery practices and continuously improve ways of working.
  • Support onboarding, development, and continuous learning across teams.

  Requirements

  Bachelor’s degree in Business, Technology, or related field (or equivalent experience). 5-7 years of experience in project or delivery management roles. Experience leading delivery across multiple teams, using modern iterative practices in a large enterprise environment.

  Skills

  • Project Coordination and Planning – Leads and drives scope definition, planning, and execution across projects or complex initiatives while ensuring alignment across stakeholders and dependencies.
  • Delivery Planning and Forecasting - Drives development of realistic delivery plans, balancing scope, timelines, capacity, and dependencies to improve predictability and support informed decision-making.
  • Delivery Execution - Drives coordinated execution across multiple