Construction Administration Team Leader

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, navigation, legal, EEO, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. 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.) Colorado: $123,893.00 - $176,990.00". So Pay info is present: Colorado range. Also schedule: "Schedule:Full-time". So we have schedule info. Benefits: they list benefits package. So we can include Benefits section. We need sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe combine required qualifications?), Qualifications (maybe preferred qualifications?), Skills (maybe list skills like Microsoft Office, construction management software, people skills, mentoring, etc). But we must not create thin sections; prefer few substantive sections. However we need to follow instruction: use headings for those section names if we include them. We can decide to include About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Skills, Benefits, Pay, Schedule. But we must avoid duplication. The posting includes "Preferred Qualifications" and "Required Qualifications". We could map them to Qualifications (maybe split into Required and Preferred). But instruction says use headings like Qualifications (maybe we can have one Qualifications section with both required and preferred). However they also list Skills separate. Could combine skills into Qualifications. But they said prefer a few substantive sections over many thin ones. So maybe we combine: About the role, Responsibilities, Qualifications (including required and preferred), Benefits, Pay, Schedule. Skills could be part of Qualifications. But they explicitly list Skills as a possible heading; we can omit if we incorporate into Qualifications. Let's see content: Responsibilities list many bullet-like sentences (starting with "Direct and coordinate..."). We'll put those in

• . Required Qualifications list bullet-like sentences (Bachelor's degree..., minimum 10 years..., etc). Preferred Qualifications list bullet-like sentences (Preference given to local candidates..., Experience and/or interest in sustainable design/LEED desired..., PMP certification..., etc). Skills: they mention "Ability to lead a team on fast-paced Mission Critical construction projects", "Experience with Microsoft Office (Word, Excel, Project)", "Good planning and mentoring skills", "Experience with construction management software such as Procore, Prolog, Primavera, Bluebeam, etc.", "Must have strong people skills and the ability to interact with the Owner, Engineer, Contractor and other project stakeholders". Some of these appear in qualifications already. But we can still include a Skills section if we want, but better to avoid thin sections. However the responsibilities already include many duties; qualifications include education/experience; skills could be separate but might be thin. Let's see if we can incorporate skills into Qualifications (maybe as a subsection). But the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not mandatory to use all. It says "include a section ONLY when the posting has real, specific content for it". So we can decide to include Skills if there is real specific content. There is: "Ability to lead a team on fast-paced Mission Critical construction projects", "Experience with Microsoft Office (Word, Excel, Project)", "Good planning and mentoring skills", "Experience with construction management software such as Procore, Prolog, Primavera, Bluebeam, etc.", "Must have strong people skills and the ability to interact with the Owner, Engineer, Contractor and other project stakeholders". That's specific. So we can include Skills section. We also have Requirements heading example; but we have Required Qualifications and Preferred Qualifications. Could we use Requirements heading for required qualifications? Possibly. But we already have Qualifications heading; maybe we can use Requirements for required qualifications and Qualifications for preferred? However they said "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. We can map: About the role (intro), Responsibilities (duties), Requirements (required qualifications), Qualifications (preferred qualifications), Skills (skills), Benefits, Pay, Schedule. That seems logical. We must not repeat job title as heading. So no heading for "Construction Administration Team Lead". Good. We must not put Job ID etc. We'll ignore. We must remove boilerplate: EEO, sponsorship statement? Actually sponsorship statement: "Sponsorship (visa) for US employment authorization is not available now or in the future for this position." That's substantive? It's a condition; maybe we should keep it under Requirements or Qualifications? It's a requirement about sponsorship. It's specific. We'll include it maybe under Requirements (since it's a condition). But we need to preserve all substantive information. So we should include that statement somewhere. Could be under Requirements as a note. Also "What We Believe", "Our Commitment", employee network groups etc. That's more about company culture; could be part of About the role? The intro already includes some culture statements. But we could include a separate section? Not in the list of headings. Could incorporate into About the role. We must not include duplicated lines. Ensure we capture all responsibilities, qualifications, skills, benefits, pay, schedule. Let's extract content. Intro paragraph: "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? 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. 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 can keep that as About the role paragraph(s). Might be long but okay. Responsibilities: list after "In the role of Construction Administration Team Lead, we'll count on you to:" then bullet-like sentences separated by line breaks. Let's extract each: - Direct and coordinate work of single or multidiscipline teams throughout the construction phase of the project lifecycle (from development and initiation to close-out) - Be responsible for construction administration aspects of complex small to medium projects or routine large projects - Manage and oversee several large construction administration projects concurrently - Establish and maintain client relations, and be involved with marketing, contracts and site visits - Lead work sessions for construction admin projects (RFIs and submittal processing) and provide coaching for PM staff and discipline leads - Select, train, develop and manage construction administration personnel - Coordinate CA staffing and workload through entire project life cycle, and ensure required response times are being met - Support the development of Site Specific Safety Plans verifying that Health & Safety protocols are followed - 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 - Perform other duties as needed We'll put each as

  . Required Qualifications: after "Required Qualifications" heading in text. Content: - Bachelor's degree in Engineering, Architecture, Construction Management, Construction Science or closely related field or equivalent work experience. - A minimum of 10 years of experience in various aspects of construction planning and management, including but not limited to construction contracts; document, time, cost, and quality management; change management; and site safety. - estimating, bidding, preparing and administering purchase orders and subcontracts, scheduling, cost control, etc. - Experience with Microsoft Office - Experience with construction management software such as Procore, Prolog, Primavera, Bluebeam, etc. - Must have strong people skills and the ability to interact with the Owner, Engineer, Contractor and other project stakeholders - An attitude and commitment to being an active participant of our employee-owned culture is a must - Sponsorship (visa) for US employment authorization is not available now or in the future for this position. Note: The line "estimating, bidding, preparing and administering purchase orders and subcontracts, scheduling, cost control, etc." seems like a continuation of previous bullet; we can keep as separate bullet. Preferred Qualifications: after "Preferred Qualifications". Content: - Preference given to local candidates - Experience and/or interest in sustainable design/LEED desired - PMP certification - A minimum of 5 years in project management - Registered Architect or Professional Engineer - Ability to lead a team on fast-paced Mission Critical construction projects - Experience with Microsoft Office (Word, Excel, Project) - Good planning and mentoring skills Note: Some overlap with skills. Skills: we could extract from the above but also there is explicit "Skills" maybe not in posting. However we can create Skills section using items like: - Ability to lead a team on fast-paced Mission Critical construction projects - Experience with Microsoft Office (Word, Excel, Project) - Good planning and mentoring skills - Experience with construction management software such as Procore, Prolog, Primavera, Bluebeam, etc. - Must have strong people skills and the ability to interact with the Owner, Engineer, Contractor and other project stakeholders But many already appear in qualifications. To avoid duplication, maybe we don't need separate Skills section; we can incorporate skills into Qualifications. However the instruction says we can include Skills if there is real specific content. There is, but we risk duplication. However we could still include Skills section focusing on soft skills and technical skills not captured elsewhere. But the qualifications already cover many. To be safe, we could omit Skills section and rely on Qualifications to cover skills. The instruction: "Prefer a few substantive sections over many thin ones." So better to omit Skills if it would be thin. But we have enough content for Skills? It might be thin if we separate out. Let's decide to omit Skills section and include those skill items within Qualifications (maybe under Required or Preferred). However we already have Required and Preferred sections; we could keep them as Requirements and Qualifications. That would be two sections. That's fine. Thus sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Benefits, Pay, Schedule. Now Benefits: from "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. (Stated benefits are for full-time regular positions. Temporary and part-time roles eligible for limited benefits.)"