Project Manager - Building Engineering

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, etc). Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Content: - Intro paragraph about HDR culture, mission, etc. Could be "About the role" or maybe "About the role" is generic. The posting includes description of role: "HDR is looking for a project manager whose experience focuses on client development and delivery of large, complex projects." etc. So we can put that under "About the role". - Responsibilities: list of duties: "In the role of Project Manager, we’ll count on you to:" then bullet list: Direct and coordinate work..., Responsible..., Produce..., Establish..., Conduct..., Coordinate..., Track..., Work..., Implement..., Supervise..., 10-20% Travel..., Control..., Forecasting..., Create..., Perform other duties as needed. We need to put each as

. - Preferred Qualifications: list: Working knowledge of Revit..., Demonstrated experience..., Professional Engineering (PE) license, PMP certification, Masters degree, Excellent organizational..., Availability to frequently travel..., Active in area industry associations, Healthcare, Science and Technology, Data Center facilities, Aviation..., and/or Aerospace experience, Preference given to local candidates. - Required Qualifications: Bachelor's degree in Engineering, 7 years related experience, A minimum 2 years project management experience, Requires professional engineering license recognized by the licensing board..., MS Office and MS Project experience required (Access experience plus), Demonstrated leadership skills, An attitude and commitment to being an active participant of our employee-owned culture is a must. - Also there is "What We Believe" and "Our Commitment" about culture, employee network groups. Could be part of "About the role" or maybe separate "About HDR". But we only have allowed headings; we could put that under "About the role" as well. - Also there is "Primary Location: United States-Missouri-Kansas City Other Locations: United States-Missouri-St Louis, United States-Missouri-Springfield Industry: Building Engineering Schedule: Full-time Employee Status: Regular BusinessClass: Program Management Job Posting: Sep 28, 2026". This includes Schedule: Full-time. So we have schedule info: Full-time. So we can create a Schedule section with that content. Also maybe Pay? No pay info. Benefits? Not mentioned. So we should not create Benefits or Pay sections. - Also there is "Employee Status: Regular". Could be part of Schedule? Not needed. - Also "BusinessClass: Program Management". Might be role classification; could be part of About the role. - Also "Job Posting: Sep 28, 2026". Could be minor metadata; we can fold into a short p or drop. Probably drop. - Also "At HDR, we are committed to the principles of employment equity..." is EEO boilerplate; remove. Thus sections: About the role: include intro paragraphs about HDR culture and role description. Responsibilities: bullet list. Qualifications: Could combine Required and Preferred? The spec says we can have Requirements, Qualifications, Skills sections. We need to decide. The posting has "Preferred Qualifications" and "Required Qualifications". Could map Required Qualifications to "Requirements" section, Preferred Qualifications to "Qualifications" section, and maybe Skills to "Skills" section (like excellent organizational, project management, communication). But we can also put skills under Qualifications. However we must not create thin sections. Let's think. We have: - Required Qualifications: Bachelor's degree, 7 years experience, 2 years PM experience, PE license, MS Office/MS Project, leadership skills, attitude commitment. - Preferred Qualifications: software knowledge, multidiscipline experience, PE license (again), PMP, Masters, excellent organizational/project management/communication skills, travel availability, industry associations, specific sector experience, preference local. - Skills: maybe "Excellent organizational, project management, and communication (both written and verbal) skills." appears in both Preferred and Required? Actually appears in Preferred. Also leadership skills. We could create a "Skills" section for those soft skills: Excellent organizational, project management, and communication (both written and verbal) skills, Demonstrated leadership skills. But we must avoid duplication. Let's decide to have: - Requirements (Required Qualifications) - Qualifications (Preferred Qualifications) - Skills (maybe combine leadership and communication etc.) But we need to ensure we don't create sections with filler. All have content. Also we have Schedule: Full-time. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. Check if any Benefits or Pay: none. Now we need to format. We must not repeat job title as heading. The job title is "Project Manager". Not used. We must not put Job ID etc. We must preserve all substantive info. Let's extract all substantive info. Intro paragraphs: "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." Then: "HDR is looking for a project manager whose experience focuses on client development and delivery of large, complex projects. The ideal candidate should have a proven background in successfully delivering various Healthcare, Civic, Sports, Transportation, Aerospace, and/or Commercial Real Estate projects ranging from upfront planning and pre-design activities through detail design, construction support and commissioning. In addition to managing and delivery projects (which is the primary focus of this role), the successful candidate must possess the drive, experience and charisma needed to develop and secure work from a robust global client base and expand upon HDR’s reputation within these markets. This individual will manage multi-disciplinary design teams from project conception to completion. Keen focus on organizational skills and follow-through are required to be successful in this role. This person will work closely with the Regional Building Engineering Services Business Group Managers as well as our global client management team. Some travel to client sites or other HDR offices is required." That's also part of About the role. Then responsibilities list. Then "Preferred Qualifications" list. Then "Required Qualifications" list. Then "What We Believe" and "Our Commitment" paragraphs about culture, employee network groups. Could be part of About the role or maybe separate but we can include in About the role. Then location and schedule info: "Primary Location:United States-Missouri-Kansas City Other Locations:United States-Missouri-St Louis, United States-Missouri-Springfield Industry:Building Engineering Schedule:Full-time Employee Status:Regular BusinessClass:Program Management Job Posting:Sep 28, 2026" We need to preserve location info? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Location is not minor metadata? It's substantive. Should we include location? The allowed headings do not include Location. We could include location in a paragraph under About the role or maybe a separate section not allowed. Since we cannot create a heading for Location, we should fold it into a short

(maybe under About the role). Similarly, Industry, BusinessClass, Employee Status could be minor metadata; we could drop or fold. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep location info. We can include it in a paragraph after About the role maybe as a separate

not under a heading. That's allowed: we can have

for prose anywhere. So we can add a paragraph with location details. Similarly schedule: we have Schedule: Full-time. That's substantive; we should create a Schedule section because we have actual schedule info. So we will have a Schedule section with

Schedule

and

Full-time

maybe. Now Benefits and Pay: not present, so we omit those sections. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

About the role

... (intro paragraphs + role description + What We Believe + Our Commitment maybe)

Responsibilities

• Direct and coordinate work of single or multidiscipline teams throughout the project’s lifecycle (from development and initiation to close-out)
• Responsible for all aspects of complex small to medium projects or routine large projects
• Produce and coordinate several small to medium projects concurrently
• Establish and maintain client relations, and be involved with marketing, contractual, design and production meetings
• Conduct work sessions for deliverable development in conjunction with other staff and stakeholders
• Coordinate staffing and workload through entire project life cycle, and ensure completion of deliverables on schedule
• Track financial aspects of projects, and coordinate and adjust work effort with team to ensure that work is completed within parameters of agreed-to budget and schedule
• Work with the Accounting, Operational and Business leadership for periodic project reviews
• Implement QA/QC procedures
• Supervise large project staffs and act as mentor for less-experienced Project Managers
• 10-20% Travel to project sites, including international if needed
• Control project budget, scope, and schedule
• Forecasting, Invoicing and contract management
• Create vital proposal content including scope, schedule and budget
• Perform other duties as needed

Requirements

• Bachelor's degree in Engineering
• 7 years related experience
• A minimum 2 years project management experience
• Requires professional engineering license recognized by the licensing board for the location of the position offered (e.g., Professional Engineer (PE or P.Eng) license)
• MS Office and MS Project experience is required (Access experience would be a plus)
• Demonstrated leadership skills
• An attitude and commitment to being an active participant of our employee-owned culture is a must

Qualifications

• Working knowledge of Revit, AutoCAD, Autodesk Construction Cloud, Newforma, Procore, BIM360 Docs, BIM