Jobs · Management · South Carolina

Roofing Laborer

Baker Roofing Company · Charleston, SC · 1 mo ago
ManagementFull-time
We need to output only HTML fragment, no or . Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. We have: - About the role: The first paragraph about company and role? Actually "Baker Roofing Company - Roofing Laborer For more than 110 years..." includes company description and maybe "Why Join Baker Roofing?" bullet list. That could be "About the role" or "Benefits". The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Content: - Company description: "For more than 110 years, Baker Roofing Company has been a trusted leader..." That's about the company, could be "About the role". Also "Gain hands-on experience..." etc. - "Why Join Baker Roofing?" bullet list: Weekly Pay, Annual Paid Holidays & Paid Time Off, Medical, Dental & Vision Insurance, 401K Matching Program..., Employee Stock Ownership Program (ESOP), Employee Assistance Program (EAP), Comprehensive Safety Training from Day One, Paid On-the-Job Training & Career Development. That's benefits. So Benefits section. - Pay: The bullet list includes Weekly Pay but no amount. It says "Weekly Pay" but no specifics. According to rule: do NOT include Pay section unless posting actually states them (specific). "Weekly Pay" alone is not a specific amount; it's just stating they pay weekly. Might be considered not specific enough. The instruction: 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. Benefits we have specifics (list). Pay: only "Weekly Pay" with no amount; could be considered not specific. Safer to omit Pay section. - Schedule: Not mentioned. So omit. - Responsibilities: The "What You'll Do" list: Prepare job sites..., Remove debris..., Assist with installing..., Apply adhesives..., Safely operate..., Follow company..., Work collaboratively..., Perform other duties... That's responsibilities. - Requirements: There's a "Requirements" heading in the posting: "To perform this job successfully..." then lists Minimum Qualifications, Education, Experience, Driver's License. Also "Skills & Qualifications" list. So we can have Requirements section covering minimum qualifications, maybe also Skills? But we also have Skills section separate. The instruction: Use headings for Skills as separate. So we can split: Requirements (education, experience, driver's license) and Skills (the list after "Skills & Qualifications"). - Qualifications: Could be same as Requirements? But we already have Requirements. The instruction says we can have Qualifications section if there is specific content. The posting has "Minimum Qualifications" and "Skills & Qualifications". Might treat "Qualifications" as the combination of education/experience/license. But we already used Requirements for that. Could also have Qualifications duplicate. Better to follow the posting: Use Requirements for the "Minimum Qualifications" (education, experience, driver's license). Use Skills for the "Skills & Qualifications" list. Possibly also a Qualifications section for something else? Not needed. - About the role: Could include company overview and maybe "Gain hands-on experience..." and "Why Join Baker Roofing?"? But we already used Benefits for the bullet list. The "Why Join Baker Roofing?" is benefits. The earlier paragraph about company and "Gain hands-on experience..." could be About the role. Thus sections: - About the role: company description and maybe the introductory sentences about gaining experience, develop skills, career growth. - Responsibilities: the "What You'll Do" list. - Requirements: education, experience, driver's license. - Skills: the list under "Skills & Qualifications". - Benefits: the bullet list under "Why Join Baker Roofing?" (including Weekly Pay? Might include Weekly Pay as a benefit but we decided not to include Pay section; but Weekly Pay is a benefit detail; we could include it under Benefits as a bullet: Weekly Pay. Since Benefits section can include any benefit details, including pay frequency. The rule about Pay section is separate; we can still mention Weekly Pay inside Benefits. That's okay. Thus Benefits section will have items: Weekly Pay, Annual Paid Holidays & Paid Time Off, Medical, Dental & Vision Insurance, 401K Matching Program (100% match up to 3% and 50% match at 4% and 5%), Employee Stock Ownership Program (ESOP), subject to applicable waiting and vesting periods, Employee Assistance Program (EAP), Comprehensive Safety Training from Day One, Paid On-the-Job Training & Career Development. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact phrasing? We can keep as list items. Now we need to output HTML fragment: use

for each section heading, then content: either

for prose,

  • for lists. We must not repeat job title as heading. The job title is "Roofing Laborer". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: Disclaimer, Equal Opportunity Employer, accommodation contact, EOE line, etc. Also remove "Apply today and start building your future with Baker Roofing Company!" maybe considered application instruction; remove. Also remove "Principals only. Recruiters, please do not contact this job posting." etc. Also remove "Position Summary" heading? Not needed as we have our own headings. We need to preserve all substantive information: company description, gain hands-on experience, etc. Let's extract substantive paragraphs: First paragraph: "Baker Roofing Company - Roofing Laborer For more than 110 years, Baker Roofing Company has been a trusted leader in commercial roofing, residential construction, metal fabrication, and restoration. With over 29 locations across the Southeast, we're committed to quality craftsmanship, employee development, and a family-focused culture built on safety and teamwork. Gain hands-on experience, develop valuable industry skills, and build a career with opportunities to grow from Roofing Laborer to Roofer, Foreman, and beyond." We can treat that as About the role (maybe two paragraphs). We'll put in

    . Then "Why Join Baker Roofing?" bullet list: we will put under Benefits. Then "Position Summary As a Roofing Laborer, you will assist Roofers and Foremen to prepare job sites and install roofing systems including metal, shingles, single-ply (TPO, PVC, and EPDM), slate, asphalt, aluminum, wood, and related materials." That could be part of About the role or Responsibilities? It's a summary of duties; but we have a detailed Responsibilities list later. We could include this sentence in About the role as overview. Or we could treat it as part of Responsibilities. Since we already have a detailed list, we could keep this sentence as part of About the role to avoid duplication. But we must preserve all substantive information; we can include it in About the role as a paragraph. Then Requirements section: includes "To perform this job successfully, an individual must be able to perform each essential duty satisfactorily. The lists below are representative of the knowledge, skill and/or ability required." Then Minimum Qualifications: Education: High school/GED preferred, but not required; Experience: General construction experience preferred; Driver’s License: Required. We'll put that as a list. Then Skills & Qualifications list: "A strong commitment to safety.Attention to detail and quality craftsmanship.Strong teamwork and communication skills.The ability to work efficiently in a fast-paced, physically demanding environment.Ability to prioritize tasks and follow directions.Basic knowledge of construction tools and materials.Ability to use a tape measure and perform basic measurements.Problem-solving skills with a willingness to ask questions and communicate concerns." We'll split into list items. Then "What You'll Do" list: we will put under Responsibilities. Then Physical Demands and Work Environment: Are those considered part of Requirements? Possibly they are additional requirements. The instruction: we have sections for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands and Work Environment could be considered part of Requirements or maybe a separate section like "Working Conditions". Not in allowed headings. We could fold them into Requirements as additional details. Since we must preserve all substantive information, we can include them under Requirements as a list or paragraphs. The allowed headings are limited; we cannot create new headings like Physical Demands. So we need to incorporate that info into existing sections, likely Requirements (or maybe Qualifications). We'll put them under Requirements as a list. Thus Requirements will include: Education, Experience, Driver's License, Physical Demands, Work Environment. We'll make sub-lists? Could just make a single list with items. But we need to avoid losing detail. We'll create a

      with items for each bullet. Now Benefits: we have list. Now we must not include Pay section. Now we must not include Schedule. Now we must not include Qualifications heading if we already used Requirements for qualifications; but we could still have Qualifications section if we want to separate education/experience from skills. However we already have Skills separate. The posting has "Minimum Qualifications" and "Skills & Qualifications". So we could have Qualifications for Minimum Qualifications, and Skills for Skills & Qualifications. Then Requirements could be something else? But the instruction says we can use Requirements heading. It didn't forbid having both Requirements and Qualifications. But we need to avoid thin sections. We have substantive content for both Minimum Qualifications and Skills & Qualifications. So we could have: - Requirements: maybe the "To perform this job successfully..." sentence? Not needed. Better: Use Requirements for Minimum Qualifications (education, experience, driver's license). Use Skills for Skills & Qualifications. Use Qualifications maybe for something else? Not needed. Thus we will have sections: About the role, Responsibilities, Requirements, Skills, Benefits. Check if any other content like "Position Summary" could be part of About the role. Now we need to remove boilerplate: Disclaimer, Equal Opportunity Employer, accommodation contact, EOE line, "Principals only. Recruiters, please do not contact this job posting." Also remove "Apply today and start building your future with Baker Roofing Company!" (application instruction). Also remove "If you require reasonable accommodation..." etc. Now produce HTML. Let's craft:

      About the role

      For more than 110 years, Baker Roofing Company has been a trusted leader in commercial roofing, residential construction, metal fabrication, and restoration. With over 29 locations across the Southeast, we're committed to quality craftsmanship, employee development, and a family-focused culture built on safety and teamwork. Gain hands-on experience, develop valuable industry skills, and build a career with opportunities to grow from Roofing Laborer to Roofer, Foreman, and beyond. As a Roofing Laborer, you will assist Roofers and Foremen to prepare job sites and install roofing systems including metal, shingles, single-ply (TPO, PVC, and EPDM), slate, asphalt, aluminum, wood, and related materials.

      Responsibilities

      • Prepare job sites and maintain a clean, safe work environment.
      • Remove debris from roofs and surrounding work areas.
      • Assist with installing insulation, vapor barriers, and roofing materials.
      • Assist with installing and repairing roofing systems using materials such as metal, shingles, slate, asphalt, aluminum, wood, and single-ply systems.

Similar jobs