General Contracting Superintendent III

for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short

or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Who We Are: description of Seneca Companies, OWL Services, etc. This is "About the company" maybe "About the role"? Actually "Who We Are" is about the company. Could be "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" for description of role? But we have "Who We Are" which is about the company. Could map to "About the role"? Might be better to use "About the role" for description of job duties? Actually "What You’ll Do" is responsibilities. "Who We Are" is about the company. There's no explicit "About the role" heading in posting, but we can create a section if we have substantive content. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to decide which sections we have content for. We have: - About the company: "Who We Are" paragraph. Could be considered "About the role"? Not exactly. But we could treat it as "About the role" (maybe they want description of role). However the instruction list includes "About the role" as an example heading. We could use that for the "Who We Are" paragraph (since it's about the organization). Or we could skip that section if not matching exactly. But we likely should include an "About the role" section with the company overview. - Responsibilities: "What You’ll Do:" with bullet points percentages. That's responsibilities. Should be a section with heading

Responsibilities

• list. - Requirements: "What We’re Looking For:" includes Education, Experience, Licenses/Certifications, Technical Abilities, Autonomy/Direction, Supervise projects up to $5 million, Tools and Equipment. That's qualifications/requirements. Could be split into Requirements and Qualifications? The instruction list includes Requirements, Qualifications, Skills. We need to decide how to map. The posting has Education, Experience, Licenses/Certifications, Technical Abilities, Autonomy/Direction, Tools and Equipment. Could treat as Requirements (Education, Experience, Licenses/Certifications) and Qualifications (Technical Abilities, Autonomy/Direction, Tools and Equipment) or Skills (Technical Abilities, Tools and Equipment). But we need to avoid thin sections. Perhaps combine into one "Requirements" section with subpoints? But we must use
  • for any list of duties/requirements/benefits. So we can have a
    with items for each bullet. We also have "Why Choose OWL Services?" which lists benefits: Company Vehicle with Fuel Card, Per Diem & Competitive Pay, Unlimited/Flex Paid Time Off, Health, Dental, and Vision Insurance with optional offerings of HSA and FSA, 401k with Company Match, Tuition Reimbursement, Company Paid Life Insurance, Free Employee Assistance Program (EAP) and Wellness Program. That's benefits. So we need a Benefits section. Pay: The posting mentions "Competitive Pay" but not specific numbers. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Competitive Pay" but not a specific amount. Is that considered stating pay? It says "Competitive Pay" which is vague but still mentions pay. However the instruction says never create Pay section unless posting actually states them. It does state "Competitive Pay". Should we include Pay section? The instruction also says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive Pay" is somewhat vague but not exactly placeholder like "commensurate with experience". It's a phrase indicating pay is competitive but not a number. Might be considered filler? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Competitive Pay". So we could include Pay section with that phrase. However we also have Benefits section that includes many items; we could combine Pay into Benefits? But they said prefer few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they gave separate headings examples. However we can decide to include Benefits only, and mention Competitive Pay within Benefits list. That would avoid a thin Pay section. The instruction: "Prefer a few substantive sections over many thin ones." So we could merge Pay into Benefits. But we need to follow the heading list: they gave examples but not mandatory to use all. So we can have sections: About the role, Responsibilities, Requirements, Benefits. Possibly also Qualifications? But we can incorporate qualifications into Requirements. We also have "Working Hazards" and "Physical/Mental Exertion". Those are not in the heading list but could be part of Requirements or maybe omitted? The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to include that info somewhere. Could be part of Requirements (maybe under "Working Conditions") but we don't have a heading for that. Could we create a custom heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those examples. Safer to stick to those headings. However we need to preserve all substantive info; we could include Working Hazards and Physical/Mental Exertion under Requirements as additional list items. Also there is a sentence: "This job description is intended to describe the general nature and level of work being performed..." etc. That's boilerplate legal; we should remove. Also "Requisition #4092" is minor metadata; we can fold into a short

    or drop it. Probably drop it. Also "Job Title: Superintendent III" we should not repeat as heading. Also "Job Description: Acts as lead person..." That's actually a summary of role; could be part of About the role or Responsibilities. But we already have "What You’ll Do:" which details responsibilities. The earlier "Job Description:" sentence is somewhat redundant; we can incorporate into About the role maybe. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

    About the role

    Seneca Companies, an OWL Services Affiliated Company. OWL Services is the premier sales, installation, program management and service provider to retail, commercial, fleet, aviation and marine, and emergency power generation companies across the U.S. With 33 offices and distribution centers and more than 1,400 field service professionals, OWL delivers on a service platform that includes construction, compliance and testing, maintenance and repair, modernization and re-imaging, and EV charging solutions to keep businesses and people moving 24 hours a day, 7 days a week, 365 days a year. OWL Services’ companies have received numerous awards over the years for exemplary customer service. Most recently it was the recipient of EVgo’s Deployment Excellence Award in its first-ever class of awardees in the National EV Charging Recognition Program.

    Maybe also include the brief job description sentence: "Acts as lead person on construction projects and oversee its organization, scheduling, and implementation. Executes daily coordination of general contracting projects other construction related activities. Assists field personnel on site as necessary and monitors field activity. Assists in procurement of equipment, material, labor, sub-contractors and other project related activities for construction projects." That could be part of About the role or Responsibilities. Since we have Responsibilities detailed, we could put that summary in About the role as an overview. Thus About the role paragraph could include both company overview and role summary. Next:

    Responsibilities

    • 15%: Confer with project managers, owners, contractors, or design professionals to discuss and resolve matters, such as work procedures, complaints, or construction problems.
    • 15%: Plan, schedule, or coordinate construction project activities to meet deadlines.
    • 15%: Prepare and submit progress reports, project tracking reports, and work ahead schedules.
    • 15%: Inspect or review projects to monitor compliance with building and safety codes, or other regulations. Inspect or review projects to monitor compliance with environmental regulations.
    • 15%: Monitor all personnel onsite to ensure compliance with OSHA safety practices.
    • 15%: Travel and rotation schedules.
    • 5%: Handles special projects as assigned by Project Manager.
    • 5%: Other duties as assigned.
    Note: The last two bullets are 5% each. Next:

    Requirements

    • Education: Requires a high school diploma, knowledge of construction/carpentry practices as would normally be acquired through secondary education.
    • Experience: 4+ years of experience in general contracting commercial supervision; 1 year of field experience as a Superintendent or similar, secondary education in construction or related discipline or experience in a similar industry.
    • Licenses/Certifications: Journeyman or Master Carpenter Preferred but not required. Requires valid driver's license.
    • Technical Abilities: Knowledge of the general contracting industry and underground petroleum fueling system basics is a plus.
    • Autonomy/Direction: Translates directions from Managers and Project Managers into working orders for site personnel. Works with minimal supervision and is required to demonstrate mid-level decision-making with minimal assistance of a manager. Supervise projects up to $5 million with some supervision.
    • Tools and Equipment: Ability to perform manual construction work and equipment operation as described. Knowledge and experience with computer programs (Procore, Outlook).
    • Working Hazards: Works in an environment with potential exposure to fumes, dirt, noise, equipment movement dangers, vibrations, dangerous chemical/solvents, electrical shock, and inclement temperature extremes.
    • Physical/Mental Exertion: Ability to perform heavy physical labor exerting up to 100 pounds of force on an occasional basis and up to 50 pounds of force on a frequent basis performing such tasks as climbing, balancing, stooping, kneeling, crouching, crawling, reaching, standing, walking, pushing, pulling, lifting, grasping and fingering.
    We could also include "Supervise projects up to $5 million with some supervision." Already in Autonomy/Direction. Now Benefits:

    Benefits

    • Company Vehicle with Fuel Card
    • Per Diem & Competitive Pay
    • Unlimited/Flex Paid Time Off
    • Health, Dental, and Vision Insurance with optional offerings of HSA and FSA
    • 40