Project Delivery Team Lead

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about HDR culture, mission, etc. We need to decide sections: maybe "About the role" (intro), "Responsibilities", "Qualifications" (maybe split Preferred and Required), "Skills"? The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need to extract content. We have: - Intro: "At HDR, our employee-owners are fully engaged..." etc. That's about company culture, mission. Could be "About the role" or maybe "About HDR". The instruction says we can use About the role heading. We'll put that intro as

under

About the role

. - Responsibilities: bullet list after "In the role of Project Delivery Team Lead, we'll count on you to:" then list items. So we need

Responsibilities

with

• each. - Preferred Qualifications: list after "Preferred Qualifications". Those are bullet-like lines. We'll treat as maybe "Qualifications" or "Preferred Qualifications". The allowed headings include Qualifications, Skills, Requirements. We could have a section "Qualifications" with sub-sections? But we can only use those headings. Could combine Preferred and Required under Qualifications? But we need to preserve all info. Could do two sections: "Preferred Qualifications" and "Required Qualifications" but those aren't in allowed list. However we could use "Qualifications" for required and maybe "Skills" for preferred? But better to follow instruction: use headings from list; we can still have multiple sections with same heading? Probably not. We could create "Qualifications" for required, and "Skills" for preferred (since many are skills). Let's see. Preferred Qualifications items: - Minimum of 5 years leadership experience - Minimum of 5 years of project management experience, specifically in Data Center/Mission Critical markets - Strong desire to stay current with the trends of the fast-paced Mission Critical industry. - Ability to interact with various design teams, have excellent organizational, project management and communication (both written and verbal) skills - Working knowledge of the following standards: Uptime Topology standards, ASHRAE TC 9.9, and the ISO standards regarding PUE, CUE, and WUE. - Working knowledge of Newforma Project Center and/or ProjectWise Document Management Software - Excellent organizational and communication skills - Strongly motivated and showing professional initiative. - Focused on client outcomes. These are a mix of experience and skills. Could put under "Qualifications" (preferred) and "Skills" (maybe overlapping). But we also have Required Qualifications: - Bachelor's degree or equivalent experience - A minimum of 7 years experience - Professional registration, license or certification may be required based on role - Strong communication and listening skills - Ability to handle multiple assignments - Good leadership and organizational skills - An attitude and commitment to being an active participant of our employee-owned culture is a must We could have a section "Qualifications" for required, and maybe "Skills" for preferred (or vice versa). However the instruction says "Prefer a few substantive sections over many thin ones." So maybe combine both preferred and required into one "Qualifications" section, separating with paragraphs? But we need to preserve all info; we can list them as
  under Qualifications, but we need to differentiate preferred vs required? Not required to differentiate; just preserve content. So we can put all qualification items under a single Qualifications section. But we also have "Skills" heading possible; we could put skill-related items under Skills. However many items are skills. Might be okay to have both Qualifications and Skills sections. Let's decide: We'll have: - About the role (intro paragraphs) - Responsibilities (list) - Qualifications (combined required and preferred) - Skills (maybe extract skill-specific items) But we risk duplication. Better: Use Qualifications for required, Skills for preferred (since many are skills). Let's extract skill items from preferred: ability to interact..., excellent organizational..., communication skills, working knowledge of standards, working knowledge of software, excellent organizational and communication skills (duplicate), strongly motivated..., focused on client outcomes. Also leadership experience and PM experience are experience not skill. Could still go under Skills? Might be okay. But we also have required items: Bachelor's degree, 7 years experience, professional registration, strong communication/listening skills, ability to handle multiple assignments, good leadership/organizational skills, attitude commitment. We could put required under Qualifications, and preferred under Skills. That seems reasonable. Let's craft:

  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. We believe building engineering is more than systems and structures, it’s about powering progress and enabling innovation. As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure that supports the digital age and shapes the spaces where people work, connect, and thrive. From high-performance data centers driving the future of AI to dynamic commercial environments, your work will directly support technological advancement, sustainability, and human experience. We bring together mechanical, electrical, structural, and civil engineering experts to solve complex design challenges with precision, creativity, and collaboration. Whether you're optimizing energy efficiency, integrating resilient systems, or engineering the backbone of next-generation facilities, your contributions will help define the future of the built environment. This isn’t just a job, it’s a chance to lead innovation, engineer impact, and build a legacy of excellence. This role is specifically dedicated to the Technology/Media/Telecom (TMT) market sector.

  Then Responsibilities:

  Responsibilities

  • Supervise, support, and develop a team of senior project managers, project managers, and assistant project managers
  • Assist the Project Delivery Leader with project delivery operations including recruiting, staff development, training, profitability, morale, quality control, and marketing support
  • May function as a Project Manager in addition to management responsibilities
  • Assist with administrative responsibility for section staff and technical service functions, and lead and coordinate services with other delivery teams
  • Be involved in marketing planning, proposals and interviews
  • Assist in ensuring that all work is planned, organized, controlled and evaluated through proactive project management system
  • Implement, monitor and support company policy - Assist in the selection, training, development and management of delivery staff
  • Work cooperatively with Market Sector Leaders and marketing staff in local and national marketing and delivery efforts
  • Perform other duties as needed
  Then Qualifications (required):

  Qualifications

  • Bachelor's degree or equivalent experience
  • A minimum of 7 years experience
  • Professional registration, license or certification may be required based on role
  • Strong communication and listening skills
  • Ability to handle multiple assignments
  • Good leadership and organizational skills
  • An attitude and commitment to being an active participant of our employee-owned culture is a must
  Then Skills (preferred):

  Skills

  • Minimum of 5 years leadership experience
  • Minimum of 5 years of project management experience, specifically in Data Center/Mission Critical markets
  • Strong desire to stay current with the trends of the fast-paced Mission Critical industry.
  • Ability to interact with various design teams, have excellent organizational, project management and communication (both written and verbal) skills
  • Working knowledge of the following standards: Uptime Topology standards, ASHRAE TC 9.9, and the ISO standards regarding PUE, CUE, and WUE.
  • Working knowledge of Newforma Project Center and/or ProjectWise Document Management Software
  • Excellent organizational and communication skills
  • Strongly motivated and showing professional initiative.
  • Focused on client outcomes.
  We should also maybe include location etc? The posting includes Primary Location etc. Should we include? The instruction: include section only when posting has real, specific content. Location is metadata but could be included in a short

  maybe under About the role? But we already have About the role long. Could add a

  after About the role for location? But we must not repeat job title. Location is not a heading; we could add a short paragraph under About the role or maybe a separate section like "Location"? Not in allowed headings. So we could fold into About the role as a sentence. But we already have long About the role; we could add a sentence at end: "Primary location: Overland Park, Kansas (with additional presence in Kansas City, Missouri)." However we must preserve ALL substantive information; location is substantive. So we should include it. We can add a

  after the intro about location. Similarly, Schedule: Full-time, Employee Status: Regular, BusinessClass: Program Management, Job Posting date. Those are metadata; we could include them in a short paragraph under About the role or maybe under a "Details" section? Not allowed headings. So we can incorporate into About the role as a brief note. But we must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state Schedule: Full-time. So we could include schedule info in a paragraph, but not as a separate Schedule heading unless we want to. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Schedule: Full-time. So we could create a Schedule section with that info. However we also have Employee Status etc. Could include under Schedule? Might be okay. But we already have many sections; maybe better to add a short paragraph under About the role. Given "Prefer a few substantive sections over many thin ones." So maybe avoid extra thin sections like Schedule. So we will incorporate schedule etc into About the role. Thus final HTML fragment includes the sections above. Check for boilerplate removal: We removed EEO, legal, etc. We kept the commitment paragraphs? Those were in "What We Believe" and "Our Commitment". Those are about culture; could be part of About the role. We already included some of that in the intro but not all. The posting includes: "What We Believe HDR is our company. Together, we build on each other's life experiences and perspectives to make great things possible every day. This shapes our collaborative culture, encourages organizational trust and connects us closer to the clients and communities we serve. Our Commitment As employee owners, we all have a role in creating an inclusive environment where each of us is welcomed, valued, respected and empowered to bring our authentic selves to work every day. Our eight Employee Network Groups (Asian Pacific, Black, Hispanic/Latino(a), LGBTQ+, People with Disabilities, Veterans, Women, Young Professionals) help create a sense of belonging and foster a supportive environment where everyone is empowered to engage and contribute. Each group has an executive sponsor and is open to all employees." We should preserve that. We can add to About the role after the intro. Thus About the role will be longer: include the initial paragraphs, then the What We Believe and Our Commitment paragraphs, then location/schedule note. Let's craft About the role content: Paragraph 1: "At