Site Civil Engineer
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Content:
- Intro paragraph about HDR culture, mission, etc. Could be "About the role" or maybe "About the role" is appropriate. The instruction: do NOT repeat the job title as a heading. Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading with the introductory paragraphs describing role and company.
- Then "Primary Responsibilities" list: we need to put under Responsibilities
with - items.
- Then "Preferred Qualifications" and "Required Qualifications": these could go under Requirements or Qualifications. The instruction: we have headings Requirements, Qualifications, Skills. We need to decide where to place content. Likely "Requirements" for required qualifications, "Qualifications" for preferred qualifications, and maybe "Skills" for skills like Microsoft Office, communication, etc. But we can combine.
We need to preserve all substantive information. Not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove lines like "Read further to learn how you could help make great things possible not only in your community, but around the world." That's maybe part of intro but not boilerplate? It's still substantive? It's a call to read further; maybe we can keep as part of About the role.
We need to remove duplicated lines: there are repeated sentences? Not many.
We need to remove "At HDR, we are committed to the principles of employment equity..." that's EEO boilerplate; remove.
Also remove "We consider all qualified applicants, regardless of criminal histories..." also EEO.
Also remove "What We Believe", "Our Commitment", "Our eight Employee Network Groups", etc. Those are benefits/culture but maybe they belong in Benefits? However they are not benefits like medical etc. They are culture statements. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Benefits section should include actual benefits like medical, dental, vision, etc. The posting includes: "We provide a comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes medical, dental, vision, short and long-term disability, life insurance, an employee assistance program, paid time away, parental leave, paid holidays, a retirement savings plan with employer match, employee referral bonus and tuition reimbursement." That's specific benefits; we can include Benefits section.
Pay: The posting includes: "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) {Pay Transparency Location1}: $100,000____ - $_130,000___". That seems to have placeholders with underscores. It says "$100,000____ - $_130,000___". That's placeholder; we should not include Pay section if it's filler/placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "$100,000____ - $_130,000___" which seems like placeholder with underscores; it's not a real number. Likely we should omit Pay section because it's not specific. However the text also says "The expected compensation range for this position depends upon skills, experience, education and geographical location." That's vague. So we should not create Pay section.
Schedule: The posting includes "Schedule:Full-time". That's specific. So we can include Schedule section with Full-time.
Also there is "Primary Location:United States-Colorado-Denver Other Locations:United States-Colorado-Englewood". That's location metadata; we could fold into a short
under About the role or maybe not needed as heading. 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 paragraph with location info.
Now we need to decide sections:
- About the role: include introductory paragraphs about HDR, role description, mission, etc. Also location paragraph maybe.
- Responsibilities: list of duties from "In the role of Site Civil Engineer we'll count on you to:" bullet points.
- Requirements: maybe required qualifications (Bachelor's degree, previous experience in general civil engineering, requires PE license, demonstrated leadership and communication skills, proficient with MS Office, good verbal/written communication, attitude commitment to employee-owned culture). Also maybe "Previous experience with an architectural/engineering firm" is preferred, not required.
- Qualifications: preferred qualifications (Previous experience with an architectural/engineering firm, Preference given to local candidates). Could also include "Preferred Qualifications" heading.
- Skills: maybe we can include skills like Microsoft Office, communication, leadership, etc. But those are already in requirements. Could combine.
- Benefits: list of benefits.
- Schedule: Full-time.
We need to avoid duplicate content. Let's extract.
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' 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. 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 can keep that as About the role.
Then location: "Primary Location:United States-Colorado-Denver Other Locations:United States-Colorado-Englewood". We'll make a short p.
Then Responsibilities: list from "In the role of Site Civil Engineer we'll count on you to:" followed by many items separated by line breaks. Let's extract each:
- Contribute to the development of civil engineering scope of work and budgets for proposals
- Serve as the Engineer of Record on non-complex projects
- Coordinate with internal and external resources to complete all due diligence research and documentation
- Develop concept site layouts that are compliant with all Jurisdictional requirements and support the Pre-Application process
- Coordinate with the Authority Having Jurisdiction to determine design and submittal requirements and coordinate design solutions
- Assist with community outreach as defined within the scope of a project
- Attend and contribute to client meetings
- Transition the concept plans through the schematic and construction design processes
- Coordinate with subconsultants for support and design services
- Design and produce plan sets, details, specifications, and cost estimates
- Perform calculations in support of the site development (stormwater pond sizing, culvert and pipe capacity analysis, hydrology calcs, etc.)
- Author reports that are technically sound, grammatically correct, and well organized
- Use engineering judgement to determine the best course of action
- Be independent in your pursuit for information and solutions
- Manage your time and organization of multiple tasks/projects
- Communicate effectively with managers and team members
- Pursue efficiencies within your work and operations
- Mentor junior staff and delegate appropriate tasks
- Be an advocate for HDR, the BES Business Group, and the Site Civil team
- Perform other tasks that support the mission and vision of HDR and the BES Business Group
We'll put each as
- .
Now Requirements (required qualifications):
- Bachelor's degree
- Previous experience in general civil engineering
- Requires professional engineering license recognized by the licensing board for the location of the position offered. Example: Professional Engineer (PE or P.Eng) license.
- Demonstrated leadership and communication skills
- Proficient with Microsoft Office
- Good verbal and written communication skills
- An attitude and commitment to being an active participant of our employee-owned culture is a must
We could also include "Previous experience with an architectural/engineering firm" is preferred, not required.
Now Qualifications (preferred):
- Previous experience with an architectural/engineering firm
- Preference given to local candidates
Now Skills: maybe we could list "Microsoft Office proficiency, communication skills, leadership, engineering judgement, time management, mentoring". But those are already covered. Might be redundant. Perhaps we can omit Skills section to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine skills into Requirements or Qualifications. Let's put skills under Requirements (since they are required). Or we could have a Skills section for things like "Microsoft Office, communication, leadership". But we already have those in Requirements. To avoid duplication, we can keep them in Requirements and not have a separate Skills section.
Benefits: list:
- 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". We'll include that as prose maybe.
Schedule: Full-time.
Now we need to output HTML fragment only, no /. Use
for headings, - for lists,
for prose.
We must not include any markdown code fences.
Let's craft.
Structure:
About the role
Intro paragraphs...
Primary Location: United States-Colorado-Denver; Other Locations: United States-Colorado-Englewood.
Responsibilities
- ...
...
Requirements
- Bachelor's degree
- Previous experience in general civil engineering
- 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)
- Demonstrated leadership and communication skills
- Proficient with Microsoft Office
- Good verbal and written communication skills
- An attitude and commitment to being an active participant of our employee-owned culture is a must
Qualifications
- Previous experience with an architectural/engineering firm
- Preference given to local candidates
Benefits
We provide a comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes:
- med
Responsibilities
with- items.
- Then "Preferred Qualifications" and "Required Qualifications": these could go under Requirements or Qualifications. The instruction: we have headings Requirements, Qualifications, Skills. We need to decide where to place content. Likely "Requirements" for required qualifications, "Qualifications" for preferred qualifications, and maybe "Skills" for skills like Microsoft Office, communication, etc. But we can combine.
We need to preserve all substantive information. Not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove lines like "Read further to learn how you could help make great things possible not only in your community, but around the world." That's maybe part of intro but not boilerplate? It's still substantive? It's a call to read further; maybe we can keep as part of About the role.
We need to remove duplicated lines: there are repeated sentences? Not many.
We need to remove "At HDR, we are committed to the principles of employment equity..." that's EEO boilerplate; remove.
Also remove "We consider all qualified applicants, regardless of criminal histories..." also EEO.
Also remove "What We Believe", "Our Commitment", "Our eight Employee Network Groups", etc. Those are benefits/culture but maybe they belong in Benefits? However they are not benefits like medical etc. They are culture statements. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Benefits section should include actual benefits like medical, dental, vision, etc. The posting includes: "We provide a comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes medical, dental, vision, short and long-term disability, life insurance, an employee assistance program, paid time away, parental leave, paid holidays, a retirement savings plan with employer match, employee referral bonus and tuition reimbursement." That's specific benefits; we can include Benefits section.
Pay: The posting includes: "The expected compensation range for this position depends upon skills, experience, education and geographical location. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.) {Pay Transparency Location1}: $100,000____ - $_130,000___". That seems to have placeholders with underscores. It says "$100,000____ - $_130,000___". That's placeholder; we should not include Pay section if it's filler/placeholder? The instruction: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here we have "$100,000____ - $_130,000___" which seems like placeholder with underscores; it's not a real number. Likely we should omit Pay section because it's not specific. However the text also says "The expected compensation range for this position depends upon skills, experience, education and geographical location." That's vague. So we should not create Pay section.
Schedule: The posting includes "Schedule:Full-time". That's specific. So we can include Schedule section with Full-time.
Also there is "Primary Location:United States-Colorado-Denver Other Locations:United States-Colorado-Englewood". That's location metadata; we could fold into a short
under About the role or maybe not needed as heading. 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 paragraph with location info. Now we need to decide sections: - About the role: include introductory paragraphs about HDR, role description, mission, etc. Also location paragraph maybe. - Responsibilities: list of duties from "In the role of Site Civil Engineer we'll count on you to:" bullet points. - Requirements: maybe required qualifications (Bachelor's degree, previous experience in general civil engineering, requires PE license, demonstrated leadership and communication skills, proficient with MS Office, good verbal/written communication, attitude commitment to employee-owned culture). Also maybe "Previous experience with an architectural/engineering firm" is preferred, not required. - Qualifications: preferred qualifications (Previous experience with an architectural/engineering firm, Preference given to local candidates). Could also include "Preferred Qualifications" heading. - Skills: maybe we can include skills like Microsoft Office, communication, leadership, etc. But those are already in requirements. Could combine. - Benefits: list of benefits. - Schedule: Full-time. We need to avoid duplicate content. Let's extract. 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' 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. 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 can keep that as About the role. Then location: "Primary Location:United States-Colorado-Denver Other Locations:United States-Colorado-Englewood". We'll make a short p. Then Responsibilities: list from "In the role of Site Civil Engineer we'll count on you to:" followed by many items separated by line breaks. Let's extract each: - Contribute to the development of civil engineering scope of work and budgets for proposals - Serve as the Engineer of Record on non-complex projects - Coordinate with internal and external resources to complete all due diligence research and documentation - Develop concept site layouts that are compliant with all Jurisdictional requirements and support the Pre-Application process - Coordinate with the Authority Having Jurisdiction to determine design and submittal requirements and coordinate design solutions - Assist with community outreach as defined within the scope of a project - Attend and contribute to client meetings - Transition the concept plans through the schematic and construction design processes - Coordinate with subconsultants for support and design services - Design and produce plan sets, details, specifications, and cost estimates - Perform calculations in support of the site development (stormwater pond sizing, culvert and pipe capacity analysis, hydrology calcs, etc.) - Author reports that are technically sound, grammatically correct, and well organized - Use engineering judgement to determine the best course of action - Be independent in your pursuit for information and solutions - Manage your time and organization of multiple tasks/projects - Communicate effectively with managers and team members - Pursue efficiencies within your work and operations - Mentor junior staff and delegate appropriate tasks - Be an advocate for HDR, the BES Business Group, and the Site Civil team - Perform other tasks that support the mission and vision of HDR and the BES Business Group We'll put each as
- .
Now Requirements (required qualifications):
- Bachelor's degree
- Previous experience in general civil engineering
- Requires professional engineering license recognized by the licensing board for the location of the position offered. Example: Professional Engineer (PE or P.Eng) license.
- Demonstrated leadership and communication skills
- Proficient with Microsoft Office
- Good verbal and written communication skills
- An attitude and commitment to being an active participant of our employee-owned culture is a must
We could also include "Previous experience with an architectural/engineering firm" is preferred, not required.
Now Qualifications (preferred):
- Previous experience with an architectural/engineering firm
- Preference given to local candidates
Now Skills: maybe we could list "Microsoft Office proficiency, communication skills, leadership, engineering judgement, time management, mentoring". But those are already covered. Might be redundant. Perhaps we can omit Skills section to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could combine skills into Requirements or Qualifications. Let's put skills under Requirements (since they are required). Or we could have a Skills section for things like "Microsoft Office, communication, leadership". But we already have those in Requirements. To avoid duplication, we can keep them in Requirements and not have a separate Skills section.
Benefits: list:
- 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". We'll include that as prose maybe.
Schedule: Full-time.
Now we need to output HTML fragment only, no /. Use
for headings,
- for lists,
for prose. We must not include any markdown code fences. Let's craft. Structure:
About the role
Intro paragraphs...
Primary Location: United States-Colorado-Denver; Other Locations: United States-Colorado-Englewood.
Responsibilities
- ... ...
Requirements
- Bachelor's degree
- Previous experience in general civil engineering
- 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)
- Demonstrated leadership and communication skills
- Proficient with Microsoft Office
- Good verbal and written communication skills
- An attitude and commitment to being an active participant of our employee-owned culture is a must
Qualifications
- Previous experience with an architectural/engineering firm
- Preference given to local candidates
Benefits
We provide a comprehensive benefits package that promotes employee ownership, employee health, performance, and success, which includes:
- med
- for lists,