Shop Driver

Here's a thinking process: 1. **Analyze the Request:** - User wants me to reformat a job posting into clean, well-structured semantic HTML. - Rules: - Use `

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

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat the job title as a heading (page already shows it) - 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 2. **Analyze the Input Text:** Let me extract the relevant parts from the provided job posting text. I need to identify: - Job title (already mentioned as "Shop Driver" but I shouldn't repeat it as a heading) - About the role / company description - Responsibilities/duties - Requirements/qualifications - Skills - Benefits - Pay/hourly rate - Schedule - Boilerplate to remove: EOE/M/F/D/V, drug-free workplace, pre-employment drug testing, equal opportunity statements, etc. (unless they have specific content, but the rules say remove EEO/equal-opportunity/scam-warning boilerplate) - Duplicated lines, application instructions Let's parse the text carefully: "STRUCTURAL integrates technology-driven solutions with specialty contracting services to improve, protect, and enhance the existing infrastructure of owners directly, and in partnership with designers and contractors. STRUCTURAL offers a wide range of specialty repair and maintenance services and is the largest concrete repair contractor in the United States, with roughly 2,500 employees working from locations nationwide and in select international markets. STRUCTURAL is the open-shop contracting business line of Structural Group. STRUCTURAL is currently looking for a Shop Driver to join our high-rise team performing work in New York City, NY. Qualified candidates have the opportunity to earn $25-$26 per hour (depending on relevant work experience and licenses) and enjoy benefits including medical, dental, 401(K), paid vacation and more! Qualifications Must have a clean driving record as specified by Structural Technologies. Previous experience driving & transporting construction equipment for a commercial construction company, rental operation or similar environment preferred. Correctly delivers materials & equipment to multiple jobsites in a timely & safe manner. May be required to lift, push, pull or carry objects up to 50 lbs. without assistance. Occasionally will be required to work overtime and off hours. Requires solid and timely communication skills with Management and Field Teams. Detail oriented and able to prioritize work flows. Exhibits a Safety 24/7 attitude in all situations. Extremely safety conscious. Sets example for others by demonstrating that Safety is a core value. Occasionally will perform light duty construction work and assist with cleanliness, stocking and inventory control of shop/warehouse and yard. Candidates must be team oriented and solution oriented, with a proactive, professional, positive attitude. Candidates must be safety-oriented in all situations and environments. Excellent compensation and benefits available for qualified candidates. STRUCTURAL is a drug-free workplace. We will conduct pre-employment drug testing on all employees. EOE/M/F/D/V STRUCTURAL is committed to a Safety 24/7 culture and offers competitive compensation and benefits including medical, dental insurance, 401(k), paid holidays & vacation, tuition reimbursement, career development and growth opportunities, and a caring work environment." Wait, there are two "benefits" / "compensation" sections. I need to parse carefully. Let's break it down by rule: - **Do NOT repeat the job title as a heading** -> The job title is "Shop Driver". I should not create an `

  ` for "Shop Driver" or "Job Title". I might include it in a `

  ` maybe, but the rules say "the page already shows it", so I probably shouldn't output a heading for it. Maybe I can put it in a `

  ` at the top, but the rules say use `

  ` for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It also says "Do NOT repeat the job title as a heading (the page already shows it)". So I'll omit a separate title heading. I might just start with About the role or something. - **Do NOT put Job ID / requisition numbers as headings** -> None present, or I'll fold into `

  `. - **Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions** -> Remove "EOE/M/F/D/V", "STRUCTURAL is a drug-free workplace. We will conduct pre-employment drug testing on all employees.", the second long benefits paragraph that seems repetitive, etc. - **IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text** -> So I only create sections that have actual content. No "N/A", "TBD", etc. - **Prefer a few substantive sections over many thin ones** -> Consolidate where possible. - **Use `

  ` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)** -> I can use these, but only if there's real content. - **Use `

  • ` for any list of duties/requirements/benefits** -> For lists. - **Use `

    ` for prose** -> For paragraphs of descriptive text. Now, let's identify the actual sections and content from the posting: **About the company/role**: "STRUCTURAL integrates technology-driven solutions with specialty contracting services to improve, protect, and enhance the existing infrastructure of owners directly, and in partnership with designers and contractors. STRUCTURAL offers a wide range of specialty repair and maintenance services and is the largest concrete repair contractor in the United States, with roughly 2,500 employees working from locations nationwide and in select international markets. STRUCTURAL is the open-shop contracting business line of Structural Group. STRUCTURAL is currently looking for a Shop Driver to join our high-rise team performing work in New York City, NY." This can be "About the role" or combined. I'll use `

    About the role

    ` and put the prose in `

    `. **Pay**: "Qualified candidates have the opportunity to earn $25-$26 per hour (depending on relevant work experience and licenses)" This is specific pay info. Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "$25-$26 per hour". So I should include a Pay section with that exact info. No placeholder. **Schedule**: "Occasionally will be required to work overtime and off hours." This mentions overtime and off hours, but not a formal schedule. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Occasionally will be required to work overtime and off hours." That's specific enough? I think I can include a Schedule section with that content, or fold it into Responsibilities. But the rule says "Prefer a few substantive sections over many thin ones." I'll see if it's substantial enough. "Occasionally will be required to work overtime and off hours." is a specific duty/condition. I might include it in Responsibilities or as a Schedule section if I want. But let's see: the Schedule heading might be empty or thin if I just put that. I'll probably fold it into Responsibilities or mention it there. Actually, the rule says "never emit a heading followed by filler/placeholder text". If I create a Schedule section with "Occasionally will be required to work overtime and off hours." that's not filler, it's actual content. But is it a "Schedule"? It's more of a duty. I'll likely put it under Responsibilities or Qualifications. I'll decide based on flow. **Benefits**: Multiple mentions: "enjoy benefits including medical, dental, 401(K), paid vacation and more!" and later "STRUCTURAL is committed to a Safety 24/7 culture and offers competitive compensation and benefits including medical, dental insurance, 401(k), paid holidays & vacation, tuition reimbursement, career development and growth opportunities, and a caring work environment." There's also "Excellent compensation and benefits available for qualified candidates." The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits. But there are two slightly different benefit descriptions. I need to preserve ALL substantive information; do NOT invent or summarize away detail. So I should include all specific benefits mentioned. However, the rule also says "Prefer a few substantive sections over many thin ones." and "include a section ONLY when the posting has real, specific content for it". Benefits section can have the list. But I need to be careful not to create a Benefits section with placeholder text. I'll create a Benefits section with the specific benefits listed, using `

    • ` for each. I'll combine the unique ones: medical, dental, 401(K), paid vacation, paid holidays, tuition reimbursement, career development/growth opportunities, caring work environment. The "more!" is vague, but I'll stick to what's explicitly stated. **Qualifications/Requirements**: The posting has a "Qualifications" section with many bullet points. The rules say use `
      • ` for any list of duties/requirements/benefits. I should create a "Requirements" or "Qualifications" section. The headings suggested: "Requirements, Qualifications". I'll probably use one, or maybe "Qualifications" since the posting says "Qualifications". I'll use `

        Qualifications

        ` and list them. **Skills**: The posting mentions skills implicitly: "solid and timely communication skills", "detail oriented and able to prioritize work flows", "safety-conscious". But no explicit "Skills" section heading. I could create a Skills section, but only if there's real content. There are specific skill mentions: communication, detail orientation, safety attitude. I'll probably fold them into Qualifications or Responsibilities to keep it few and substantive. **About the role**: Already identified. Let's restructure the content cleanly: I'll create the following sections (only if they have content): - About the role - Qualifications (or Requirements) - Responsibilities (duties) - Pay - Benefits I won't create Schedule unless there's a clear schedule, which there isn't beyond "overtime and off hours" which I'll put in Qualifications/Responsibilities. Let's list out all the specific content per section: **About the role**: "STRUCTURAL integrates technology-driven solutions with specialty contracting services to improve, protect, and enhance the