Construction Manager (Owner's Rep)

We need to output only HTML fragment, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We have About The Role (we can map to About the role). Responsibilities: we have Key Responsibilities. Requirements: we have Required Qualifications. Qualifications: we have Preferred Qualifications. Skills: maybe we can combine? The posting includes many skill-like items; but we can create a Skills section if there is specific content. However we already have Requirements and Qualifications; maybe we can put skills under Requirements? But rule: Use headings only when posting has real specific content. We can create a Skills section if we have skill-specific bullet list. The posting includes "Strong coordination and stakeholder management skills", "Ability to influence and drive action across multiple teams without direct authority", "Excellent communication and relationship-building abilities", etc. Those are skills. Could create a Skills section. But we also have Requirements and Qualifications sections; we could put skill bullets there. However we need to avoid duplication. Let's decide: Use sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Schedule? The posting mentions Work Arrangement: 100% Onsite, Travel: Up to 50% across North America. That's schedule/travel info. Could be Schedule section. But we need to check if we have specific schedule info: "Work Arrangement: 100% Onsite", "Travel: Up to 50% across North America". That's schedule/travel. So we can create a Schedule section with that info. Benefits: we have benefits listed. Pay: we have pay range. So include Pay and Benefits sections. We must not repeat job title as heading. Do not put Job ID etc. Remove boilerplate: EEO, legal, etc. Also remove "Apply today if you have experience..." maybe that's application instruction; we should remove application instructions. Also remove "Job Type & Location" maybe duplicate. Also remove "Workplace Type" maybe duplicate. Also remove "Application Deadline". Also remove "About TEKsystems" etc. Also remove "Why Join Us?" maybe we can keep as part of About the role? It's not a standard heading; but we could incorporate into About the role or maybe a separate section? The headings list does not include "Why Join Us". So we should not create a heading for it; we can incorporate its content into About the role or maybe drop? The rule: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the "Why Join Us?" content somewhere. Since we don't have a heading for it, we can include it as a paragraph under About the role or maybe under a generic section? But we must use headings only from list; we can still have paragraphs without heading. So we can add a

after About the role heading that includes the Why Join Us content. Similarly "What We're Looking For" could be incorporated into About the role or maybe a separate section? Not in list; we can incorporate. We need to ensure we keep all substantive info: responsibilities list, required qualifications, preferred qualifications, pay range, benefits list, work arrangement, travel, location, contract type, potential for long-term extension, etc. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove "Apply today if you have experience..." (application instruction). Also remove "Job Type & Location" maybe considered metadata but we need to keep location and contract type etc. We can keep location and contract type in a short paragraph maybe under About the role or separate? The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can have a short paragraph with location, contract type, travel, etc. We must not repeat the job title as a heading. So no heading for Construction Manager. We must output only HTML fragment. Let's structure:

About the role

Location: Cheyenne, WY. Work Arrangement: 100% Onsite. Travel: Up to 50% across North America. Employment Type: Contract with potential for long-term extension and conversion.

[Paragraph describing role: We are seeking an experienced Construction Manager to support large-scale data center projects in Cheyenne, Wyoming. This role is focused on construction execution, turnover, closeout, warranty management, and operational handoff of mission-critical facilities. The ideal candidate will have a strong background in construction project delivery, contractor coordination, and successfully transitioning completed projects into operations. This is a highly collaborative role requiring close partnership with contractors, operations teams, consultants, commissioning teams, and cross-functional stakeholders. If you enjoy driving projects to completion, managing details, building relationships, and ensuring a seamless turnover process, we'd love to hear from you.]

[What We're Looking For bullet? Could be a list? It's a list of traits. Could be

• ... but we need to decide if we want a separate section? Not in headings list, but we can still have a
  without heading. It's okay. We'll include as a list under About the role maybe after the description.
  • Thrives in fast-paced construction environments.
  • Enjoys detailed, execution-focused work.
  • Takes ownership of project delivery and turnover activities.
  • Builds strong partnerships with contractors and operational teams.
  • Focuses on solving problems through collaboration and influence.
  • Passionate about delivering high-quality projects safely and successfully.
  Then

  Responsibilities

  with
  of responsibilities. Then

  Requirements

  with
  of required qualifications. Then

  Qualifications

  with
  of preferred qualifications. Then

  Skills

  maybe we can include skill bullets from required qualifications? But we already have required and preferred qualifications; we could put skill bullets there. However we have not used Skills heading yet; we could create Skills section with skill-based bullets like "Strong coordination and stakeholder management skills", "Ability to influence and drive action across multiple teams without direct authority", "Excellent communication and relationship-building abilities", "Willingness to work onsite daily in Cheyenne, WY and travel as needed." But some of those are already in qualifications. To avoid duplication, maybe we can omit Skills section and just keep Requirements and Qualifications. The rule: Prefer a few substantive sections over many thin ones. So we can skip Skills if content overlaps. Then

  Pay

  with

  Pay range: $60.00 - $95.00/hr. Individual compensation offered ... etc. We need to preserve all substantive info about pay: mention that compensation depends on qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Also mention eligibility requirements apply to some benefits and may depend on job classification and length of employment. Benefits subject to change... We'll include that in Pay section or Benefits? Probably Pay section includes pay range and note about compensation factors. Benefits section includes benefits list. Then

  Benefits

  with
  of benefits. Then

  Schedule

  maybe we already included work arrangement and travel in About the role paragraph; but we could also create Schedule section with that info. However we already placed location, work arrangement, travel in About the role paragraph. To avoid duplication, we could keep Schedule section with that info and remove from About the role. But we need to preserve all info; we can put it in Schedule section. Let's decide: Put location, contract type, etc in About the role? The About the role paragraph already has description; we can add a short paragraph after About the role heading that includes location, contract, travel. Then we may not need Schedule section. However the rule says include a section ONLY when posting has real specific content for it. We have schedule info (Work Arrangement: 100% Onsite, Travel: Up to 50% across North America). That's specific. So we could create a Schedule section with that info. But we also need to include location and contract type maybe elsewhere. Could put location and contract type in About the role paragraph. Then Schedule section for work arrangement and travel. That seems fine. Thus:

  About the role

  Location: Cheyenne, WY. Employment Type: Contract with potential for long-term extension and conversion.

  Description...

  What We're Looking For...

  Responsibilities

  ...

  Requirements

  ...

  Qualifications

  ...

  Schedule

  Work Arrangement: 100% Onsite. Travel: Up to 50% across North America.

  Pay

  The pay range for this position is $60.00 - $95.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.

  Benefits

  ...
  We must ensure we don't include boilerplate like "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's part of benefits description; we should keep it as part of Benefits section maybe as a paragraph before the list. The rule: preserve ALL substantive information. So we need to include that sentence. We'll add a

  before the list. Now let's extract the exact content. From posting: About The Role paragraph: "We are seeking an experienced Construction Manager to support large-scale data center projects in Cheyenne, Wyoming. This role is focused on construction execution, turnover, closeout, warranty management, and operational handoff of mission-critical facilities. The ideal candidate will have a strong background in construction project delivery, contractor coordination, and successfully transitioning completed projects into operations. This is a highly collaborative role requiring close partnership with contractors, operations teams, consultants, commissioning teams, and cross-functional stakeholders. If you enjoy driving projects to completion, managing details, building relationships, and ensuring a seamless turnover process, we'd love to hear from you." What We're Looking For bullet list: "We're Looking For Someone Who Thrives in fast-paced construction environments.Enjoys detailed, execution-focused work.Takes ownership of project delivery and turnover activities.Builds strong partnerships with contractors and operational teams.Focuses on solving problems through collaboration and influence.Is passionate about delivering high-quality projects safely and successfully." We need to split into list items. Key Responsibilities list (each sentence ends with period). Let's extract: - Manage onsite construction, commissioning support, turnover, and project closeout activities for data center projects. - Coordinate with contractors, consultants, designers, vendors, and internal stakeholders to ensure successful project execution. - Drive completion of punch list items, turnover documentation, training validation, and operational sign-offs. - Manage project closeout packages and ensure all handover requirements are completed accurately and on schedule. - Track and coordinate warranty-related issues following project turnover. - Conduct regular site walks to monitor progress, validate project milestones, and confirm turnover readiness. - Support project planning, scope development, and construction sequencing activities. - Assist in maintaining project schedules and identifying schedule risks and mitigation plans. - Manage construction cost changes and support budget forecasting activities. - Review project status, quality metrics, schedule performance, and construction progress. - Facilitate communication and collaboration between contractors, QA/QC teams, commissioning teams, and operations partners. - Support Method of Procedure (MOP) reviews for work performed in live data center environments. - Promote a