Project Manager - Building Engineering
HDR · Springfield, MO · 2 wk ago
On-siteConsultingFull-time
We need to output HTML fragment with sections for headings where content exists. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions.
We need to preserve all substantive information. Let's parse the posting.
First paragraph: intro about HDR culture, mission, etc. That's about the role? Could be "About the role" or maybe "About HDR". But we only have allowed headings; we can put "About the role" for that intro.
Then description: "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure..." That's also about role.
Then: "HDR is looking for a project manager whose experience focuses on client development and delivery of large, complex projects." That's also about role.
Then bullet list of duties after "In the role of Project Manager, we’ll count on you to:" followed by many items separated by line breaks. Those are responsibilities.
Then "Preferred Qualifications" list.
Then "Required Qualifications" list.
Then "What We Believe" etc. That's more about culture; could be part of About the role or maybe separate but we don't have a heading for culture; we could include under About the role.
Then "Our Commitment" etc. Also culture.
Then location, schedule, etc. At end: "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 include Schedule if present: "Schedule:Full-time". So we can create a Schedule section with that.
Pay: not mentioned, so omit.
Benefits: not mentioned, omit.
We need to include sections only when there is real specific content.
Thus sections: About the role, Responsibilities, Requirements (maybe combine required qualifications?), Qualifications (maybe preferred?), Skills, Schedule.
But we have both Required Qualifications and Preferred Qualifications. Could combine into Requirements (required) and Qualifications (preferred) or Skills. The instruction: use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements for required qualifications, Qualifications for preferred qualifications, Skills for skills like software knowledge, leadership, etc.
Let's extract.
About the role: include introductory paragraphs about HDR mission, building engineering services group, role description, etc. We'll combine the first few paragraphs up to before "In the role of Project Manager, we’ll count on you to:" maybe.
Responsibilities: the list after that.
Requirements: Required Qualifications bullet list.
Qualifications: Preferred Qualifications bullet list.
Skills: maybe include "Excellent organizational, project management, and communication (both written and verbal) skills." etc. But that's also in Preferred Qualifications. Could also include "MS Office and MS Project experience is required (Access experience would be plus)" etc. That's in Required Qualifications. Might be better to put skills under Skills heading: e.g., "Excellent organizational, project management, and communication (both written and verbal) skills.", "MS Office and MS Project experience", "Leadership", etc. But we already have Required and Preferred sections; we could keep them as Requirements and Qualifications. Skills maybe redundant but we can still include if there is distinct skill content not covered elsewhere. However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Required and Preferred into Requirements and Qualifications, and not create Skills unless there is distinct skill list not already covered. The posting includes "Excellent organizational, project management, and communication (both written and verbal) skills." under Preferred Qualifications. Also "Demonstrated leadership skills" under Required Qualifications. Also "MS Office and MS Project experience is required (Access experience would be plus)". Also "Professional Engineering (PE) license", "PMP certification", "Masters degree". Those are qualifications.
Thus we can have:
- Requirements: Required Qualifications (Bachelor's degree, 7 years experience, 2 years PM experience, PE license, MS Office/MS Project, leadership, employee-owned culture commitment).
- Qualifications: Preferred Qualifications (Revit/AutoCAD etc., experience with multi-disciplined teams, PE license (again?), PMP, Masters, excellent organizational/communication skills, availability to travel, industry associations, specific sector experience, preference for local candidates).
But note PE license appears both required and preferred; we can keep as required.
Now Skills: maybe we could include "Excellent organizational, project management, and communication (both written and verbal) skills." but that's already in Qualifications. Could skip Skills.
Schedule: we have "Schedule:Full-time". Also maybe "Full-time Employee Status:Regular". So schedule section: Full-time.
We also have location info; but we don't have a heading for location. Could include under About the role as a short paragraph.
We must not include boilerplate like EEO, etc.
Now produce HTML.
We need to wrap content in appropriate tags:
.
Now Requirements (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 for the location of the position offered. Example: Professional Engineer (PE or P.Eng) license.
- MS Office and MS Project experience is required (Access experience would be plus)
- Demonstrated leadership skills
- An attitude and commitment to being an active participant of our employee-owned culture is a must
Now Qualifications (Preferred Qualifications):
- Working knowledge of Revit, AutoCAD, Autodesk Construction Cloud, Newforma, Procore, BIM360 Docs, BIM360 Field, and Bluebeam
- Demonstrated experience in working with multi-disciplined teams of Architects, Engineers, and Designers.
- Professional Engineering (PE) license
- PMP certification
- Masters degree
- Excellent organizational, project management, and communication (both written and verbal) skills.
- Availability to frequently travel locally to project locations (:50%) and regional sites as needed (Active in area industry associations)
- Healthcare, Science and Technology, Data Center facilities, Aviation and other mass transportation facilities, and/or Aerospace experience
- Preference given to local candidates
Note: The phrase "Availability to frequently travel locally to project locations (:50%) and regional sites as needed (Active in area industry associations)" seems a bit garbled; we keep as is.
Now Schedule: we have "Schedule:Full-time". Also "Employee Status:Regular". We'll put Full-time.
We could also include "Primary Location: United States-Missouri-Kansas City Other Locations: United States-Missouri-St Louis, United States-Missouri-Springfield". Could be part of About the role or maybe a separate section but we don't have a heading for location. We'll add a short paragraph under About the role after the intro maybe.
Let's add a sentence: "Primary location is Kansas City, Missouri, with additional offices in St. Louis and Springfield, Missouri."
Now ensure we don't repeat content.
Now produce HTML.
We'll output:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, etc. Also remove navigation, cookie, legal, duplicated lines, application instructions.
We need to preserve all substantive information. Let's parse the posting.
First paragraph: intro about HDR culture, mission, etc. That's about the role? Could be "About the role" or maybe "About HDR". But we only have allowed headings; we can put "About the role" for that intro.
Then description: "As part of HDR’s Building Engineering Services Group, you’ll help design the critical infrastructure..." That's also about role.
Then: "HDR is looking for a project manager whose experience focuses on client development and delivery of large, complex projects." That's also about role.
Then bullet list of duties after "In the role of Project Manager, we’ll count on you to:" followed by many items separated by line breaks. Those are responsibilities.
Then "Preferred Qualifications" list.
Then "Required Qualifications" list.
Then "What We Believe" etc. That's more about culture; could be part of About the role or maybe separate but we don't have a heading for culture; we could include under About the role.
Then "Our Commitment" etc. Also culture.
Then location, schedule, etc. At end: "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 include Schedule if present: "Schedule:Full-time". So we can create a Schedule section with that.
Pay: not mentioned, so omit.
Benefits: not mentioned, omit.
We need to include sections only when there is real specific content.
Thus sections: About the role, Responsibilities, Requirements (maybe combine required qualifications?), Qualifications (maybe preferred?), Skills, Schedule.
But we have both Required Qualifications and Preferred Qualifications. Could combine into Requirements (required) and Qualifications (preferred) or Skills. The instruction: use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements for required qualifications, Qualifications for preferred qualifications, Skills for skills like software knowledge, leadership, etc.
Let's extract.
About the role: include introductory paragraphs about HDR mission, building engineering services group, role description, etc. We'll combine the first few paragraphs up to before "In the role of Project Manager, we’ll count on you to:" maybe.
Responsibilities: the list after that.
Requirements: Required Qualifications bullet list.
Qualifications: Preferred Qualifications bullet list.
Skills: maybe include "Excellent organizational, project management, and communication (both written and verbal) skills." etc. But that's also in Preferred Qualifications. Could also include "MS Office and MS Project experience is required (Access experience would be plus)" etc. That's in Required Qualifications. Might be better to put skills under Skills heading: e.g., "Excellent organizational, project management, and communication (both written and verbal) skills.", "MS Office and MS Project experience", "Leadership", etc. But we already have Required and Preferred sections; we could keep them as Requirements and Qualifications. Skills maybe redundant but we can still include if there is distinct skill content not covered elsewhere. However the instruction says prefer a few substantive sections over many thin ones. So maybe we combine Required and Preferred into Requirements and Qualifications, and not create Skills unless there is distinct skill list not already covered. The posting includes "Excellent organizational, project management, and communication (both written and verbal) skills." under Preferred Qualifications. Also "Demonstrated leadership skills" under Required Qualifications. Also "MS Office and MS Project experience is required (Access experience would be plus)". Also "Professional Engineering (PE) license", "PMP certification", "Masters degree". Those are qualifications.
Thus we can have:
- Requirements: Required Qualifications (Bachelor's degree, 7 years experience, 2 years PM experience, PE license, MS Office/MS Project, leadership, employee-owned culture commitment).
- Qualifications: Preferred Qualifications (Revit/AutoCAD etc., experience with multi-disciplined teams, PE license (again?), PMP, Masters, excellent organizational/communication skills, availability to travel, industry associations, specific sector experience, preference for local candidates).
But note PE license appears both required and preferred; we can keep as required.
Now Skills: maybe we could include "Excellent organizational, project management, and communication (both written and verbal) skills." but that's already in Qualifications. Could skip Skills.
Schedule: we have "Schedule:Full-time". Also maybe "Full-time Employee Status:Regular". So schedule section: Full-time.
We also have location info; but we don't have a heading for location. Could include under About the role as a short paragraph.
We must not include boilerplate like EEO, etc.
Now produce HTML.
We need to wrap content in appropriate tags: About the role
then
... maybe multiple paragraphs. For lists:
- ...
About the role
...
Primary location is Kansas City, Missouri, with additional offices in St. Louis and Springfield, Missouri.
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Schedule
Full-time
Make sure no extra whitespace issues. Now check for any boilerplate removed: we removed EEO, legal, etc. Also removed "Watch Our Story:' https://www.hdrinc.com/our-story'" maybe we should keep? That's a link to story; it's not boilerplate but it's a promotional link. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Watch Our Story:" is not boilerplate; it's part of the intro about HDR.