Construction Manager - Federal Sector - NDER
Procon Consulting · Hammond, IN · 1 mo ago
$10/hrTemporary
We need to output HTML fragment with sections: About the role? The posting includes description about Procon and role. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, equal opportunity, etc. Also remove application instructions (cover letter and resume). Also remove navigation/legal etc.
We need to preserve all substantive info.
Let's parse content:
- Intro: "Procon is a top-ranked construction management and technology consulting firm with 25 years of experience delivering high‑impact projects across the U.S. and worldwide. An ENR Top 100 CM/PM firm for five consecutive years, we specialize in program management, project controls, commissioning, and technology—and offer an excellent platform to grow your career while shaping the future of the built environment. Procon Consulting is seeking a Construction Manager to support construction projects in Hammond, IN, with occasional travel to the Chicago Loop, IL. This position is responsible for managing renovation, mechanical system upgrade, and tenant fit-out projects from planning through closeout while ensuring successful project delivery, budget and schedule performance, and client satisfaction. The ideal candidate has 8+ years of construction management experience, including renovations and building systems projects, with additional experience managing work in high-rise buildings preferred. This role requires various skills and experience as listed below. This position does not offer employment visa sponsorship. Candidates must be authorized to work in the United States without current or future sponsorship."
That's about the role. Could be "About the role" section.
Then "Requirements Qualifications and Skills" heading in original but we need separate sections: Requirements, Qualifications, Skills. However the content lumps them. We need to split into appropriate sections based on content.
Let's extract:
Requirements (maybe bullet list):
- Bachelor's degree in Building Construction Management, Architecture, Engineering, Planning, or a closely related field.
- Minimum 8 years of experience as an Owner's Representative, Construction Manager, Project Manager, Project Facilitator, or Construction Contractor.
- Experience managing projects valued at $10 million or greater.
- Strong field construction experience with the ability to effectively manage on-site activities.
- Experience working with complex organizations including federal, state, and local government agencies, hospitals, universities, or similar institutional clients.
- Experience reviewing design document submittals, cost estimates, project schedules, and construction documentation.
- Experience with estimating, cost verification, project financial management, and change order negotiations.
- Thorough understanding of project management and construction management principles.
- Excellent written, verbal, and interpersonal communication skills with the ability to effectively facilitate meetings.
- Strong organizational, analytical, and time management skills with the ability to prioritize multiple projects.
- Proficiency with Microsoft Office Suite and industry software including Microsoft Excel, Microsoft Project, Primavera P6, Procore, Kahua, or similar project management platforms.
- Ability to work a hybrid schedule, including 2–3 days per week in Hammond, IN and 2–3 days per week in the Chicago Loop.
- Flexibility to work occasional evening hours as project schedules require.
Qualifications: maybe same as requirements? But we can treat "Qualifications" as education and experience? However we already used education as requirement. Could separate: Qualifications: Bachelor's degree..., Minimum 8 years..., Experience managing projects valued at $10 million or greater. Skills: Proficiency with software, communication, organizational, etc. But we need to avoid duplication.
Better: Use sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role (intro). Responsibilities (list). Requirements (maybe education + experience). Qualifications (maybe same as requirements? but we need distinct). Could combine but we must not create empty sections. If we cannot differentiate, we could merge Requirements and Qualifications into one section called "Requirements and Qualifications". But spec says use headings exactly those names if we include them. However we can decide to not include Qualifications if content overlaps heavily; but we need to include only when posting has real specific content for it. The posting lumps "Requirements Qualifications and Skills". It doesn't separate qualifications distinctly. So we could treat that whole block as "Requirements". Then we could have a separate "Skills" section for the software and soft skills. That seems reasonable.
Thus sections:
- About the role (intro paragraph)
- Responsibilities (list)
- Requirements (education, experience, etc.)
- Skills (software proficiency, communication, organizational, etc.)
- Benefits (salary commensurate with experience, competitive salaries, comprehensive benefits package including full medical/dental insurance and 401(K) plan)
- Pay? The posting says "Salary commensurate with experience." That's not a specific number; we should not create Pay section if content is just "commensurate with experience" (which is placeholder). The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have actual benefits: medical/dental insurance and 401(K). Pay: only "Salary commensurate with experience." That's placeholder; we should not create Pay section. Schedule: we have hybrid schedule details: Ability to work a hybrid schedule, including 2–3 days per week in Hammond, IN and 2–3 days per week in the Chicago Loop. Flexibility to work occasional evening hours as project schedules require. That's specific schedule info, so we can create Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
We must not include Pay.
Now format:
About the role
... (intro paragraph)
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Schedule
- ... ...