Construction Manager

We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about purpose, mission, etc. Could treat as "About the role" or maybe "About CESO". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - Intro paragraph: "Are you seeking purpose, challenge, and talented colleagues? We develop leaders and empower our associates to use their skills and talents to positively impact the world through service – to our coworkers, clients, and communities. We subscribe to the mission of “empowering our people to impact communities by bringing clients’ visions to life,” so if this speaks to you, let’s connect! At CESO, the Construction Manager oversees multiple construction projects for multiple clients and acts as an extension of the owner’s design and construction staff. This position oversees the work of general contractors, engineers, internal client departments, and third-party vendors to ensure projects are delivered in accordance with scope, schedule, budget, and quality expectations." That's a description of role; could be "About the role". Could also be "Responsibilities" but we have a separate list of responsibilities later. So we can put intro as "About the role" paragraph. Then we have "Primary Responsibilities" list: many bullet-like sentences each ending with period. They are not formatted as list but each line is a sentence. We need to use

  • for any list of duties/requirements/benefits. So we should convert each responsibility into
  • . The list includes: - Review construction documentation, including drawings, schedules, scopes, and reports, to support achievement of project objectives. - Conduct detailed reviews of vendor proposals and awards in coordination with the client following completion of negotiations. - Follow established standards and procedures for project reporting, documentation, and recordkeeping. - Assume overall responsibility for project start-up activities. - Perform on-site reviews of construction progress to monitor compliance with the approved project schedule. - Schedule, lead, and document weekly project meetings throughout the construction phase. - Ensure all contract terms and specifications are met by inspecting work in progress at regular intervals to verify compliance. - Independently conduct punch-list inspections and required site visits. - Review monthly pay applications to ensure billings are accurate, complete, and processed in a timely manner. - Proactively communicate project-related issues, including cost and schedule impacts, to internal leadership and client contacts. - Ensure all close-out documentation and punch-list items are completed and resolved prior to authorizing final release of retainage. - Ensure compliance with all applicable federal, state, and municipal laws, ordinances, building codes, and company policies related to construction. - Establish and communicate project safety requirements and expectations. - Perform other duties as assigned. That's a list. Then "Position Requirements" paragraph: "Bachelor's degree in Construction Management, Engineering or related field, with a minimum of 4 years of experience directly managing projects in a design and construction related field is preferred;Or 10 years related experience and/or training is required.Computer skills necessary to enter daily timesheet data and use Microsoft Outlook for email correspondence.Proficient knowledge of Microsoft Suite products, Deltek, Newforma, and SmartSheet.Travel up to 50% to project sites, inspections, or meetings required." We can treat as Requirements section. Could split into bullet list? It's a paragraph with semicolons. Could be a

    . The instruction: Use

    • for any list of duties/requirements/benefits. This is a list of requirements but not clearly bullet. Could still be

      . But we could also break into

      • for each requirement: Bachelor's degree..., 4 years experience..., Or 10 years..., Computer skills..., Proficient..., Travel up to 50%... Might be better to use list for clarity. However the instruction says "Use
        • for any list of duties/requirements/benefits". So if we treat requirements as a list, we should use
          • . The content includes multiple items separated by semicolons. We'll split. Then "Benefits And Perks" section: list of benefits: - Flexible and Hybrid Work Schedule - Paid Time Off – Credited to You 100% Upfront - 401K with a Company Match - Rewards and Recognition Program - Training and Development to Foster Professional Growth - Paid Holidays - Medical / Dental / Vision Coverage - Welcome Box - Casual Dress Code - Reimbursement for Professional Licenses - Paid Time Off for Community Team Service Events - Voluntary or Supplemental Short-Term / Long-Term Disability - Employee Assistance Program - Company Paid Bonding and Recovery - Employee Events such as Lunches and Outings to Foster a Positive Work Environment We should output as
            • . Then pay: "$85,897 - $167,023 a year The pay band shown reflects the minimum and maximum base salary for this position at CESO. Actual pay is determined by several factors, including location, experience, education, skills, and internal equity. Our pay structures are benchmarked against industry and market data to stay competitive. Each offer is based on a full review of a candidate’s background, qualifications, and fit for the role. Below are the typical new hire pay ranges for this position based on location: Brentwood, TN: $95,442 - $120,893 Cincinnati, OH: $90,669 - $114,848 Columbus, OH: $90,669 - $114,848 Dayton, OH: $90,669 - $114,848" We need to include Pay section only if posting actually states them. It does. So we should have a Pay section with heading

              Pay

              and then content. Should we list as

              or

              ? It's prose with numbers. Use

              . Could also list location-specific ranges as

              . But instruction: Use
              • for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits, but could be list. However we can keep as

                . It's fine. Schedule: Not mentioned explicitly. There's "Flexible and Hybrid Work Schedule" under benefits, but not a separate schedule section. So we should not create a Schedule section unless posting actually states them. It does not give schedule details like full-time, hours. So we omit Schedule. We also need to remove boilerplate: EEO, E-Verify, drug-free workplace, criminal background checks, AI tools, contact us, etc. Also remove duplicated lines. Also remove "CESO is a principle-centered organization..." etc. That's more fluff but maybe considered boilerplate? It's about culture; could be considered part of About the role? Might be okay to keep as part of About the role? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture paragraph is not exactly boilerplate but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The culture paragraph is substantive? It's about mission, values. Might be okay to keep as part of About the role. But we already have an intro about mission. The later paragraph: "CESO is a principle-centered organization that aligns with strong service values, integrity, and authenticity. We develop and inspire through training and coaching on the job. At CESO, we believe that work should be more rewarding than just a paycheck. In addition to a comprehensive benefit and compensation program, we create memories and friendships through our employee and service events." This is also substantive about culture. Could be included in About the role or maybe a separate section like "About CESO". But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Could put culture under About the role as well. So we can combine intro and culture into About the role paragraph(s). Use

                for prose; could have multiple

                under same heading? Probably okay. We also have "Qualifications" and "Skills" sections not present explicitly; we have Requirements which includes education, experience, computer skills, travel. Could treat as Requirements. Could also split into Qualifications (education/experience) and Skills (computer skills, travel). But we should not create thin sections. Prefer few substantive sections. So we can have Requirements covering all. We also have "Benefits And Perks" heading; we will use Benefits. Thus final HTML:

                About the role

                Are you seeking purpose, challenge, and talented colleagues? We develop leaders and empower our associates to use their skills and talents to positively impact the world through service – to our coworkers, clients, and communities. We subscribe to the mission of “empowering our people to impact communities by bringing clients’ visions to life,” so if this speaks to you, let’s connect! At CESO, the Construction Manager oversees multiple construction projects for multiple clients and acts as an extension of the owner’s design and construction staff. This position oversees the work of general contractors, engineers, internal client departments, and third-party vendors to ensure projects are delivered in accordance with scope, schedule, budget, and quality expectations. CESO is a principle-centered organization that aligns with strong service values, integrity, and authenticity. We develop and inspire through training and coaching on the job. At CESO, we believe that work should be more rewarding than just a paycheck. In addition to a comprehensive benefit and compensation program, we create memories and friendships through our employee and service events.

                Responsibilities

                • Review construction documentation, including drawings, schedules, scopes, and reports, to support achievement of project objectives.
                • Conduct detailed reviews of vendor proposals and awards in coordination with the client following completion of negotiations.
                • Follow established standards and procedures for project reporting, documentation, and recordkeeping.
                • Assume overall responsibility for project start-up activities.
                • Perform on-site reviews of construction progress to monitor compliance with the approved project schedule.
                • Schedule, lead, and document weekly project meetings throughout the construction phase.
                • Ensure all contract terms and specifications are met by inspecting work in progress at regular intervals to verify compliance.
                • Independently conduct punch-list inspections and required site visits.
                • Review monthly pay applications to ensure billings are accurate, complete, and processed in a timely manner.
                • Proactively communicate project-related issues, including cost and schedule impacts, to internal leadership and client contacts.
                • Ensure all close-out documentation and punch-list items are completed and resolved prior to authorizing final release of retainage.
                • Ensure compliance with all applicable federal, state