Project Delivery Lead (Building Engineering)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to parse the posting and decide which sections to include.
Content:
- Intro paragraph about HDR culture, employee-owners, welcoming environment, etc. Could be "About the role"? Actually "About the role" would be description of the role. The intro is more about company culture. Could be "About HDR" but not in list. The allowed headings are limited to those examples, but we can use others? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. Probably we should use those headings where content matches.
We have:
- Role description: "In the role of Project Delivery Lead, we'll count on you to:" followed by a long list of duties. That's responsibilities.
- Preferred Qualifications: list.
- Required Qualifications: list.
- What We Believe: maybe "About the role"? Not exactly. Could be "About HDR"? Not in allowed list. Could be omitted? But we need to preserve ALL substantive information. If we omit a section, we lose that info. However we could incorporate that info into a generic
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for those types. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections for any meaningful content, using appropriate heading names from the list or maybe custom if needed? The examples are just examples; we could also use "About HDR" if needed. But safer to stick to the given headings. However we have content about company culture, mission, values, benefits, pay, schedule. Those map to Benefits, Pay, Schedule sections. Also we have "What We Believe" and "Our Commitment" which could be considered "About the role"? Not exactly. Could be considered "About HDR". But we could put that under a generic
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but to be safe we could treat the introductory paragraphs as "About the role" (though it's about company). Or we could omit a heading and just have
elements. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies that if we have a heading, we should use . It doesn't forbid having no heading for some paragraphs. So we could output a series of
and
with headings where appropriate.
Thus plan:
- Start with an introductory covering the first paragraph(s) about HDR culture, mission, etc. No heading.
- Then a
Responsibilities
with - for each duty listed after "In the role of Project Delivery Lead, we'll count on you to:" (the long list). Need to split into items.
- Then a
Preferred Qualifications
with - for each bullet.
- Then a
Required Qualifications
with - for each bullet.
- Then maybe a
Benefits
with - for benefits listed: medical, dental, vision, short and long-term disability, life insurance, employee assistance program, paid time away, parental leave, paid holidays, retirement savings plan with employer match, employee referral bonus, tuition reimbursement. Also mention "comprehensive benefits package that promotes employee ownership, employee health, performance, and success". Also note "Stated benefits are for full-time regular positions."
- Then a
Pay
with containing the expected compensation range: $148,603.00 - $230,750.00 annually depending upon skills, experience, education and geographical location.
- Then a
Schedule
with containing "Full-time" (from Schedule:Full-time) and maybe also Employee Status:Regular, BusinessClass:Technical Design, etc. But schedule section should only be created if posting actually states them. It does state Schedule:Full-time. So we can include schedule.
- Also we have Primary Location, Other Locations, Industry, BusinessClass, Job Posting date. Those are metadata; we could fold into a short
or drop. 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
for location info.
- Also we have "What We Believe" and "Our Commitment" sections. Those could be placed under a heading like "About HDR" but not in list. Could we treat them as part of introductory paragraphs? They are substantive about culture, values, employee network groups. We could include them as a
after the intro, maybe under a heading "About HDR"? But not in allowed list. However we could still use
About HDR
as it's not prohibited. The instruction only gave examples; not exclusive. So we can add a heading "About HDR". That would preserve the info.
But we need to avoid filler. The content is real.
Thus final HTML:
Intro paragraph(s) about HDR culture, mission, etc.
About HDR
Content from "What We Believe" and "Our Commitment" maybe combined.
Responsibilities
...
Preferred Qualifications
...
Required Qualifications
...
Benefits
...
Pay
...
Schedule
Full-time
Location: Primary Location: United States-California-Sacramento; Other Locations: United States-California-Walnut Creek, United States-California-Folsom. Industry: Building Engineering. Job Posted: Sep 17, 2026.
We need to ensure we don't include boilerplate like EEO, etc. At the end there is EEO statement; we should remove.
Also remove duplicated lines.
Now extract the exact text.
Let's copy the posting and parse.
Posting text:
"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. In the role of Project Delivery Lead, we'll count on you to: Direct and coordinate work of single or multidiscipline teams throughout the project’s lifecycle (from development & initiation to close-out)Be responsible for all aspects of large multidiscipline projects or medium-sized projects with high degree of technical complexity, involving a large project staffProduce and coordinate several projects concurrentlyEstablish and maintain client relations, and be involved with marketing, contractual, design and production meetingsConduct work sessions for deliverable development in conjunction with other staff and stakeholdersCoordinate staffing and workload through entire project life cycle, and ensure completion of deliverables on scheduleTrack 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 scheduleWork with the Accounting, Operational and Business leadership for periodic project reviewsImplement QA/QC proceduresSupervise large project staffs and act as mentor for less-experienced Project ManagersAssist in the responsibility for operations of production section including staff development, profitability, morale, quality control and marketing supportAssist with administrative responsibility for section staff and technical service functions, and lead and coordinate services with other sectionsBe involved in marketing planning, proposals and interviewsAssist in ensuring that all work is planned, organized, controlled and evaluated through proactive project management systemImplement, monitor and support company policyAssist in the selection, training, development and management of Project Management and Administration personnelWork cooperatively with National Directors and marketing staff in local and national marketing and production effortsPerform other duties as needed Preferred Qualifications Strong communication and listening skillsA license/certificationPMP certificationGood leadership and organizational skillsAbility to handle multiple assignmentsFamiliar with Primavera P6 or SureTrak software preferredFamiliar with Procore, Newforma, ACC/Forma, GDrive/Google Suite software preferred Required Qualifications Bachelor's degree in related field or an equivalent combination of education and related professional experience10 years related experience A minimum of 5 years of project management experience Familiar with Microsoft Office, estimating and scheduling software, project management softwareMust have the ability to interact with various design teams, have excellent organizational, project management and communication (both written and verbal) skills An attitude and commitment to being an active participant of our employee-owned culture is a must 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
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and decide which sections to include. Content: - Intro paragraph about HDR culture, employee-owners, welcoming environment, etc. Could be "About the role"? Actually "About the role" would be description of the role. The intro is more about company culture. Could be "About HDR" but not in list. The allowed headings are limited to those examples, but we can use others? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. Probably we should use those headings where content matches. We have: - Role description: "In the role of Project Delivery Lead, we'll count on you to:" followed by a long list of duties. That's responsibilities. - Preferred Qualifications: list. - Required Qualifications: list. - What We Believe: maybe "About the role"? Not exactly. Could be "About HDR"? Not in allowed list. Could be omitted? But we need to preserve ALL substantive information. If we omit a section, we lose that info. However we could incorporate that info into a generic
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for those types. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections for any meaningful content, using appropriate heading names from the list or maybe custom if needed? The examples are just examples; we could also use "About HDR" if needed. But safer to stick to the given headings. However we have content about company culture, mission, values, benefits, pay, schedule. Those map to Benefits, Pay, Schedule sections. Also we have "What We Believe" and "Our Commitment" which could be considered "About the role"? Not exactly. Could be considered "About HDR". But we could put that under a generic
without heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot have other headings, but to be safe we could treat the introductory paragraphs as "About the role" (though it's about company). Or we could omit a heading and just have
elements. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies that if we have a heading, we should use . It doesn't forbid having no heading for some paragraphs. So we could output a series of
and
- with headings where appropriate.
Thus plan:
- Start with an introductory
- for each duty listed after "In the role of Project Delivery Lead, we'll count on you to:" (the long list). Need to split into items.
- Then a
Preferred Qualifications
with- for each bullet.
- Then a
Required Qualifications
with- for each bullet.
- Then maybe a
Benefits
with- for benefits listed: medical, dental, vision, short and long-term disability, life insurance, employee assistance program, paid time away, parental leave, paid holidays, retirement savings plan with employer match, employee referral bonus, tuition reimbursement. Also mention "comprehensive benefits package that promotes employee ownership, employee health, performance, and success". Also note "Stated benefits are for full-time regular positions."
- Then a
Pay
withcontaining the expected compensation range: $148,603.00 - $230,750.00 annually depending upon skills, experience, education and geographical location. - Then a
Schedule
withcontaining "Full-time" (from Schedule:Full-time) and maybe also Employee Status:Regular, BusinessClass:Technical Design, etc. But schedule section should only be created if posting actually states them. It does state Schedule:Full-time. So we can include schedule. - Also we have Primary Location, Other Locations, Industry, BusinessClass, Job Posting date. Those are metadata; we could fold into a short
or drop. 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
for location info. - Also we have "What We Believe" and "Our Commitment" sections. Those could be placed under a heading like "About HDR" but not in list. Could we treat them as part of introductory paragraphs? They are substantive about culture, values, employee network groups. We could include them as a
after the intro, maybe under a heading "About HDR"? But not in allowed list. However we could still use
About HDR
as it's not prohibited. The instruction only gave examples; not exclusive. So we can add a heading "About HDR". That would preserve the info. But we need to avoid filler. The content is real. Thus final HTML:Intro paragraph(s) about HDR culture, mission, etc.
About HDR
Content from "What We Believe" and "Our Commitment" maybe combined.
Responsibilities
- ...
Preferred Qualifications
- ...
Required Qualifications
- ...
Benefits
- ...
Pay
...
Schedule
Full-time
Location: Primary Location: United States-California-Sacramento; Other Locations: United States-California-Walnut Creek, United States-California-Folsom. Industry: Building Engineering. Job Posted: Sep 17, 2026.
We need to ensure we don't include boilerplate like EEO, etc. At the end there is EEO statement; we should remove. Also remove duplicated lines. Now extract the exact text. Let's copy the posting and parse. Posting text: "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. In the role of Project Delivery Lead, we'll count on you to: Direct and coordinate work of single or multidiscipline teams throughout the project’s lifecycle (from development & initiation to close-out)Be responsible for all aspects of large multidiscipline projects or medium-sized projects with high degree of technical complexity, involving a large project staffProduce and coordinate several projects concurrentlyEstablish and maintain client relations, and be involved with marketing, contractual, design and production meetingsConduct work sessions for deliverable development in conjunction with other staff and stakeholdersCoordinate staffing and workload through entire project life cycle, and ensure completion of deliverables on scheduleTrack 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 scheduleWork with the Accounting, Operational and Business leadership for periodic project reviewsImplement QA/QC proceduresSupervise large project staffs and act as mentor for less-experienced Project ManagersAssist in the responsibility for operations of production section including staff development, profitability, morale, quality control and marketing supportAssist with administrative responsibility for section staff and technical service functions, and lead and coordinate services with other sectionsBe involved in marketing planning, proposals and interviewsAssist in ensuring that all work is planned, organized, controlled and evaluated through proactive project management systemImplement, monitor and support company policyAssist in the selection, training, development and management of Project Management and Administration personnelWork cooperatively with National Directors and marketing staff in local and national marketing and production effortsPerform other duties as needed Preferred Qualifications Strong communication and listening skillsA license/certificationPMP certificationGood leadership and organizational skillsAbility to handle multiple assignmentsFamiliar with Primavera P6 or SureTrak software preferredFamiliar with Procore, Newforma, ACC/Forma, GDrive/Google Suite software preferred Required Qualifications Bachelor's degree in related field or an equivalent combination of education and related professional experience10 years related experience A minimum of 5 years of project management experience Familiar with Microsoft Office, estimating and scheduling software, project management softwareMust have the ability to interact with various design teams, have excellent organizational, project management and communication (both written and verbal) skills An attitude and commitment to being an active participant of our employee-owned culture is a must 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
- for benefits listed: medical, dental, vision, short and long-term disability, life insurance, employee assistance program, paid time away, parental leave, paid holidays, retirement savings plan with employer match, employee referral bonus, tuition reimbursement. Also mention "comprehensive benefits package that promotes employee ownership, employee health, performance, and success". Also note "Stated benefits are for full-time regular positions."
- Then a
- for each bullet.
- Then maybe a
- for each bullet.
- Then a
covering the first paragraph(s) about HDR culture, mission, etc. No heading. - Then a