Senior Enterprise IT Project Manager

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

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Remove boilerplate. We need to preserve substantive info. Let's parse the posting. Intro paragraph about HDR culture, mission, etc. Could be "About the role"? Actually "About the role" heading could contain description of role: "The HDR Senior Enterprise IT Project Manager leads large, strategic, enterprise-wide IT initiatives and serves as a trusted advisor to business and IT leadership. This role is accountable for delivering measurable business outcomes, not simply managing project activities." Also maybe include mission statement? But we should only include sections with real content. We have "Key Responsibilities" list. So we can have

Responsibilities

with

• each bullet. We have "Preferred Qualifications" and "Required Qualifications". Could combine into Qualifications section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading containing both required and preferred? Or separate Requirements and Qualifications? The list includes Requirements and Qualifications as possible headings. We need to decide based on content. We have "Preferred Qualifications" and "Required Qualifications". Could put Required under Requirements heading, Preferred under Qualifications heading. Or combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine into one Qualifications section with subheadings? But we cannot add custom headings beyond those listed? It 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 as examples. Safer to stick to those. We could have Requirements for required qualifications, Qualifications for preferred qualifications. That seems appropriate. We also have "Skills" maybe from proficiency with tools etc. Could put under Skills. We have "Benefits": not mentioned explicitly. There's mention of employee-owned culture, employee network groups, etc. That could be considered Benefits? But not explicit benefits like health, retirement. The instruction: never create Benefits section unless posting actually states them. It does mention employee-owned culture, employee network groups, but not explicit benefits like health insurance, 401k. Might be considered benefits? It's ambiguous. Safer to omit Benefits section if not explicit. Pay: not mentioned. Schedule: mentions "Schedule:Full-time". That's explicit. So we can have Schedule heading with Full-time. Also we have location etc. Could put under About the role? Or maybe a short p for metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include location, industry, schedule etc in a short p maybe under About the role? But schedule we already have separate heading. Could still include location in About the role paragraph. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all responsibilities bullets, qualifications, etc. Let's extract responsibilities bullets: - Lead high-visibility, mission-critical enterprise IT projects across matrixed teams; balance competing priorities and drive alignment across multiple workstreams. - Anticipate communication gaps in complex initiatives and adjust messaging to keep teams aligned and focused. - Partner with business leaders to define project scope, objectives, and measurable success metrics; drive decisions that maximize business value. - Facilitate engagement with executive stakeholders and steering committees; lead complex stakeholder discussions and align diverse groups around priorities, scope, risks, and tradeoffs. - Influence delivery strategy through project leadership experience; resolve complex cross-team conflicts and drive compromises aligned with business outcomes. - Leverage quantitative project data, including schedule performance, cost variance, resource utilization, risk trends, and delivery metrics, to assess project health, proactively identify risks and opportunities, and provide actionable recommendations to stakeholders. - Develop and maintain project resource plans that align skills, capacity, and availability with project timelines; proactively forecast demand, address resource constraints, and partner with functional leaders to support successful delivery. - Identify, document, and actively manage cross-project dependencies across teams, systems, and initiatives; assess downstream impacts, coordinate sequencing and resource alignment, and escalate risks as needed to maintain portfolio alignment. - Foster a high-performing project team environment through emotional intelligence, collaboration, and leadership; motivate and support team members through change and challenges. - Ensure adherence to and drive continuous improvement of Enterprise PMO governance, standards, methodologies, and delivery processes. Now Required Qualifications: - Bachelor's degree in Computer Science, Information Technology, Quality Assurance or closely related field - A minimum of 5 years IT management experience, including management of multiple concurrent projects - Extensive knowledge of project management processes, systems development methods, organizational change management concepts, and business process improvement methods - Experience in working with business users to establish priorities and manage expectations - Self-starter, with the ability to handle multiple tasks and deadlines with minimal supervision - Excellent client service, interpersonal and communication skills - Strong verbal and written communication skills and capable of performing tasks in a dynamic environment, many times working under tight delivery schedules - Engineering and/or Construction background a plus - An attitude and commitment to being an active participant of our employee-owned culture is a must Preferred Qualifications: - Minimum 8 years of progressive IT project management experience. - Strong executive presence with the ability to effectively communicate and influence senior leaders and executive stakeholders. - Deep understanding of complex IT ecosystems, enterprise applications, and cross-functional dependencies. - Experience leading large-scale, enterprise-wide, high-visibility technology initiatives. - Proficiency with project management and work management tools such as Microsoft Project, Jira, and ServiceNow. - Experience facilitating executive steering committees and driving alignment among diverse stakeholder groups. - Experience with portfolio management, organizational transformation, digital modernization, or large-scale enterprise initiatives. - PMP, PMI-ACP, SAFe, or similar project management certification. - Experience with project resource planning, capacity forecasting, and dependency management across multiple concurrent initiatives. - Engineering and/or construction industry experience. Also there is a paragraph about HDR culture at start: "At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story:' https://www.hdrinc.com/our-story' Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world." That could go under About the role? Or maybe a general About HDR section. Since we have About the role heading, we could put that description there. Also there is "What We Believe" and "Our Commitment" paragraphs about culture, employee network groups. That could also go under About the role or maybe a separate section like "About HDR". But we only have allowed headings; we could put under About the role as well. We must not repeat job title as heading. So we will not have heading "Senior Enterprise IT Project Manager". Good. We need to output only HTML fragment. Let's structure:

  About the role

  At HDR, our employee-owners are fully engaged in creating a welcoming environment where each of us is valued and respected, a place where everyone is empowered to bring their authentic selves and novel ideas to work every day. As we foster a culture of inclusion throughout our company and within our communities, we constantly ask ourselves: What is our impact on the world? Watch Our Story: https://www.hdrinc.com/our-story Each and every role throughout our organization makes a difference in our ability to change the world for the better. Read further to learn how you could help make great things possible not only in your community, but around the world. The HDR Senior Enterprise IT Project Manager leads large, strategic, enterprise-wide IT initiatives and serves as a trusted advisor to business and IT leadership. This role is accountable for delivering measurable business outcomes, not simply managing project activities.

  Maybe also include What We Believe and Our Commitment paragraphs. We could add another

  after that containing those paragraphs. But we must not invent content; we can include them as is. Now Responsibilities:

  Responsibilities

  • ...
  ...
  Now Requirements (required qualifications):

  Requirements

  • Bachelor's degree in Computer Science, Information Technology, Quality Assurance or closely related field
  • A minimum of 5 years IT management experience, including management of multiple concurrent projects
  • Extensive knowledge of project management processes, systems development methods, organizational change management concepts, and business process improvement methods
  • Experience in working with business users to establish priorities and manage expectations
  • Self-starter, with the ability to handle multiple tasks and deadlines with minimal supervision
  • Excellent client service, interpersonal and communication skills
  • Strong verbal and written communication skills and capable of performing tasks in a dynamic environment, many times working under tight delivery schedules
  • Engineering and/or Construction background a plus
  • An attitude and commitment to being an active participant of our employee-owned culture is a must
  Now Qualifications (preferred qualifications):

  Qualifications

  • Minimum 8 years of progressive IT project management experience.
  • Strong executive presence with the ability to effectively communicate and influence senior leaders and executive stakeholders.
  • Deep understanding of complex IT ecosystems, enterprise applications, and cross-functional dependencies.
  • Experience leading large-scale, enterprise-wide, high-visibility technology initiatives.
  • Proficiency with project management and work management tools such as Microsoft Project, Jira, and ServiceNow.
  • Experience facilitating executive steering committees and driving alignment among diverse stakeholder groups.
  • Experience with portfolio management, organizational transformation, digital modernization, or large-scale enterprise initiatives.
  • PMP, PMI-ACP, SAFe, or similar project management certification.
  • Experience with project resource planning, capacity forecasting, and dependency management across multiple concurrent initiatives.
  • Engineering and/or construction industry experience.
  Now Skills? Could we extract skills from responsibilities? But we already have responsibilities and qualifications. The instruction says prefer few substantive sections over many thin ones. Could we merge Skills into Qualifications? But we already have Qualifications heading for preferred. Could we have Skills heading for tools proficiency etc. However we already listed tools under Qualifications. Might be okay to not have separate Skills. Schedule: we have explicit "Schedule:Full-time". So we can have:

  Schedule

  Full-time

  Also location maybe we can include in About the role paragraph? Already we have location not mentioned in that paragraph. Could add a short p after About the role: "Primary Location: United States-Nebraska-Omaha". But that's minor metadata; we can fold into a short p. We also have Industry:IT, Employee Status:Regular, BusinessClass:Marketing and Admin, Job Posting:Sep 22, 2026. Those are metadata; we could include them in a short p under About the role or separate? 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 p with that metadata. Let's create a p after About the role: "Primary Location: United States-Nebraska-Omaha; Industry: IT; Schedule: Full-time; Employee Status: Regular; Business Class: Marketing and Admin; Job Posting: Sep 22, 2026." But we already have Schedule heading; we might duplicate. Better to not duplicate