Jobs · Management · New Hampshire

Assistant Construction Site Supervisor

The Contractor Consultants · Somersworth, NH · 1 mo ago
Management$65k–$75k/yrFull-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. We have: - Job Overview: includes company, salary/pay rate, location, job type, mandatory licences. We should not repeat job title as heading. We can include a short

for metadata? The instruction: "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." So we can include a

with company, location, salary, etc. But we also have a Pay section: we have salary/pay rate: $65,000 - $75,000. So we can create a Pay section with that. Also Benefits: we have performance-based completion bonus potential, accrued PTO, company vehicle or allowance, career growth opportunities, opportunity to work on prestigious projects. So Benefits section. Schedule: not mentioned explicitly; full time is mentioned but schedule not detailed. Should we include Schedule? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It states "Full Time" but not schedule details like hours. Might be considered schedule info? It says "Job/Employment Type: Full Time". That's schedule type. Could we include Schedule section with "Full Time"? Probably yes, as it's specific. However we need to avoid filler like "not specified". It's specified as Full Time, so we can include Schedule section with that. About the role: we have "The Opportunity" paragraph describing role. Could be About the role section. Responsibilities: we have "How You Will Make An Impact" bullet list. Requirements: we have "Required Qualifications & Experience". Could be Requirements or Qualifications. We have both Required and Preferred qualifications. Could combine into Qualifications section with required and preferred? But we have headings: Requirements, Qualifications, Skills. We need to decide which to use. The posting has "Required Qualifications & Experience" and "Preferred Qualifications & Experience". Could treat as Qualifications section with subpoints? But we need to use

  • for any list of duties/requirements/benefits. So we can list required qualifications as list items, and preferred as list items maybe under same section or separate? Could have two subheadings? Not allowed; only headings from list. Could use Qualifications heading and include both required and preferred as list items, maybe differentiate with text. Or we could have Requirements heading for required, and Qualifications heading for preferred. But we also have Skills: maybe we can extract skills from qualifications: "Strong hands-on background...", "Demonstrated ability...", etc. Those are more like qualifications/skills. Could put them under Skills. Better: Use sections: About the role (from The Opportunity), Responsibilities (How You Will Make An Impact), Requirements (Required Qualifications & Experience), Qualifications (Preferred Qualifications & Experience), Benefits (Compensation & Benefits), Pay (Salary/Pay Rate), Schedule (Job/Employment Type: Full Time). Also maybe Skills not needed if we already have Requirements and Qualifications. But we could still include Skills if we have distinct skill list; but we can omit to avoid thin sections. We must not include boilerplate like About Us, EEO, etc. So we drop About Us and EEO. We must preserve all substantive information. So we need to include the content from About Us? It's considered boilerplate? It's company description; maybe considered substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Us is not explicitly listed as boilerplate, but it's company description. Might be considered substantive? However the instruction says "Prefer a few substantive sections over many thin ones." About Us could be a section but we don't have a heading for it in allowed list. Allowed headings are only those listed. So we cannot add About Us heading. So we must drop it or fold into something else? Could we put it under About the role? Probably not. Safer to drop it as it's not required headings. The instruction: "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." It doesn't forbid dropping other info. But we must preserve ALL substantive information. About Us might be considered substantive. However we cannot create a heading for it because not in allowed list. Could we incorporate it into a

    under some existing section? Maybe under About the role? But About the role is about the role, not company. Could we add a

    after the sections? The instruction says output ONLY the HTML fragment, no /. It didn't forbid extra

    not under headings. But we should follow the structure: use headings for sections,

    • for lists,

      for prose. We could have a

      for company overview after the sections. That would preserve info. However the instruction: "Prefer a few substantive sections over many thin ones." Adding a stray

      might be okay. But better to incorporate into About the role? Might be okay to add a

      after the sections describing company. Let's see if any other info: "PBC Hotel Construction Group is a premier builder..." That's substantive. We'll include as a

      after the sections, maybe with no heading. Now craft HTML: We'll start with a

      for metadata: Company, Location, Pay? But we have Pay section later. We'll include company and location maybe in a

      at top. Let's decide:

      Company: PBC Hotel Construction Group
      Location: Rochester, NH
      Employment Type: Full Time

      But we already have Schedule section for Full Time; we could avoid duplication. However we need to preserve all info; duplication is okay? Better not duplicate. We'll put company and location in a

      and then Schedule section will have Full Time. But that duplicates employment type. Could instead put company and location in

      and not duplicate employment type elsewhere; Schedule section can be omitted if we put employment type in

      . But we need Schedule section only if posting states schedule; we have it. Could we put schedule in

      and not have Schedule heading? The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings if we have content. It doesn't say we must use them for every piece. So we could put employment type in a

      and not have Schedule heading. That's okay. Thus we will have:

      Company: PBC Hotel Construction Group

      Location: Rochester, NH

      Then sections:

      About the role

      You will serve as a vital field leader, assisting the Site Supervisor in directing daily trade activities for high-end hotel development projects. This role allows you to sharpen your construction management skills while ensuring top-tier quality control across active job sites. You will have the opportunity to drive project momentum and solve real-time field challenges in a supportive, collaborative environment.

      Responsibilities

      • Assist with daily onsite subcontractor supervision to maintain consistent project momentum and accountability.
      • Monitor subcontractor installations for quality, accuracy, and full compliance with hotel brand standards.
      • Enforce proper trade sequencing to ensure all construction phases stay on schedule.
      • Identify field deficiencies and work closely with subcontractors to execute swift corrective actions.
      • Communicate daily project priorities and field requirements between subcontractors and the Site Supervisor.
      • Perform minor hands-on fixes and tasks as needed to eliminate bottlenecks and keep job sites moving safely.

      Requirements

      • Strong hands-on background and technical familiarity with multi-trade construction practices.
      • Demonstrated ability to coordinate and monitor external subcontractors on active commercial or residential job sites.
      • Solid understanding of construction sequencing, quality control methods, and plan accuracy.
      • Exceptional organizational, communication, and problem-solving skills in a fast-paced environment.

      Qualifications

      • Previous supervisory or team leadership experience within commercial, residential, or hotel construction.
      • Familiarity with reading blueprints, technical drawings, and trade specifications.
      • Working knowledge of jobsite safety protocols and basic trade operations.

      Benefits

      • Performance-based completion bonus potential.
      • Accrued Paid Time Off (PTO) with 2 weeks guaranteed after year one.
      • Company vehicle provided or a flexible vehicle and gas allowance option.
      • Clear career growth opportunities within a collaborative, family-like team culture.
      • Opportunity to work on prestigious, custom-built hospitality projects.

      Pay

      $65,000 - $75,000

      We might also add a

      for Schedule if we want, but we omitted. The posting says Full Time; we could add a Schedule section with that. Let's add Schedule section to be safe, but we already have employment type not duplicated elsewhere. We'll add:

      Schedule

      Full Time

      Now we have duplicated Full Time? Not elsewhere. Good. Now we need to ensure we didn't include any boilerplate like "About Us" or EEO. We omitted. Check that we preserved all substantive information: - Company: included in

      . - Location: included. - Salary/Pay Rate: Pay section. - Job/Employment Type: Schedule section. - Mandatory Licences & Certifications: None Required - we omitted because it's minor metadata? It's a line saying None Required. Could be considered minor metadata; we can drop or include in a

      . The instruction: fold minor metadata into a short

      or drop it. So we could add a

      for that. Let's add a

      after company/location: "

      Mandatory Licences & Certifications: None Required

      " That preserves. - The Opportunity content: About the role section. - How You Will Make An Impact: Responsibilities. - Required Qualifications & Experience: Requirements. - Preferred Qualifications & Experience: Qualifications. - Compensation & Benefits: Benefits section. - About Us: we omitted; but is that substantive? It's company description. Might be considered substantive but we have no heading for it. Could we incorporate into a

      after Benefits? Let's add a

      with that description to preserve. It's not a heading, just a paragraph. That should be okay. Thus add after Benefits maybe:

      PBC Hotel Construction Group is a premier builder dedicated to high-end residential and hotel projects, operating with a culture rooted in collaboration and excellence. We foster a supportive, family-like environment where team members are empowered to grow their careers through hands-on experience and professional development.

      We must not include the EEO statement that follows. So we stop before that. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now output HTML fragment only. Let's craft final HTML:

      Company: PBC Hotel Construction Group

      Location: Rochester, NH

      Mandatory Licences & Certifications: None Required

      About the

Similar jobs