Senior Project Manager
for each heading only if there is real content. We must not repeat job title as heading. We need to extract content.
From posting:
- About The Company: description of company. Could map to "About the role"? Actually "About The Company" is about company, not role. But we have no explicit "About the role". Could we treat "About The Company" as "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings if appropriate. We need to include a section only when posting has real, specific content for it. So we need to map content to appropriate headings.
We have:
- Position Description: list of duties/responsibilities. That's responsibilities.
- Professional Experience Level/Other Qualifications: requirements/qualifications.
- Preferred (Not Required): education, CCM.
- Additional Preferred Experience: design build, BIM, LEED/CHPS, DSA.
- Preferred Licenses And Certificates: valid Certificate of Registration as an Architect or Professional Engineer.
- Compensation: salary range, bonus eligible after 6 months.
- Benefits Package: list of benefits.
- Work Environment: description of environment, physical demands.
- Solicitation: boilerplate to remove.
- EEOC Statement: remove.
Thus we can create sections:
- About the role? Could we use "About the role" for company description? Might be okay but better to use "About the role" for role overview. We have position description which is responsibilities. Could also include a brief overview: "Resolves complex construction project related issues..." but that's under responsibilities.
Maybe we can have sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Also maybe "Work Environment" not in list but we could omit as not requested heading. The instruction says use those headings as examples; we can also add other headings if needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should stick to those headings; but we can also include others if needed? Safer to stick to those.
Thus we need to map content:
- About the role: maybe a brief summary of the role (overall purpose). Could extract from first sentence of Position Description: "Resolves complex construction project related issues, disputes, and disagreements". Could also include overall purpose. We'll create a paragraph.
- Responsibilities: list of duties from Position Description (bullet list). We'll put each duty as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should stick to those headings; but we can also include others if needed? Safer to stick to those. Thus we need to map content: - About the role: maybe a brief summary of the role (overall purpose). Could extract from first sentence of Position Description: "Resolves complex construction project related issues, disputes, and disagreements". Could also include overall purpose. We'll create a paragraph. - Responsibilities: list of duties from Position Description (bullet list). We'll put each duty as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use for section headings (e.g. ...)". It implies we should use those headings for sections; but we could also add others if needed. Safer to stick to those. We could incorporate work environment details into Responsibilities or About the role? Might be better to add a "Work Environment" section as it's substantive. The instruction didn't forbid; it just gave examples. I'd include it.
But we must not create sections with filler text. We have real content.
Thus final HTML:
About the role
About the role
Enterris Associates is a trusted, full-service construction management firm specializing in program and project management, risk analysis and mitigation, claims support, compliance, and dispute resolution. We partner with the public sector and utility clients to drive the successful delivery of complex infrastructure projects. Our advisory services include testing and inspection, contract administration and oversight, compliance monitoring, and comprehensive construction and project management all tailored to help our clients navigate challenges and achieve their goals with confidence. Formally established in 2021 and built on the legacy of PQM founded in 2006, we bring nearly two decades of Architecture, Engineering, and Construction expertise to our clients. We deliver value through quality oversight, project management, compliance, and risk mitigation.
Responsibilities
- Resolves complex construction project related issues, disputes, and disagreements
- Develop, assign, and monitor performance of OARs relative to assigned construction projects
- Reviews status and overall construction project progress relative to submitted construction schedules
- Reviews change orders from all construction projects and assesses their impact on the district
- Assists Regional Directors and other Facilities management staff with bid and contract planning
- Assesses bid specifications according to District needs and probability of completion under stated timeline
- Reviews status and monitors variances of the construction project database relative to scheduling and cost control reporting
- Reviews and verifies submitted applications for payment and perform overall fiscal management of multiple construction projects
- Provides functional direction over areas of responsibility including construction project schedules, cost control, dispute resolution, contract administration, and quality control
- Reviews and monitors overall administration of contracts for Architects and related consultants
- Coordinates program activities with other District organizational branches and departments such as the Office of