Tire Service Technician - Huber Heights

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - Intro: "Part-Time Tire Technician At Discount Tire, we change more than tires..." etc. This is about the role. - "Why It’s Different Here" bullet points: People First, Career Mode, Sports Energy, Sundays Off, Weekly Pay. - "A Day In The Life": description. - "Your Everyday Work Includes": list of duties. - "Why You’ll Thrive Here": list of attributes. - "Perks & Benefits": list. - "Who We Are": company description. - EEO boilerplate to remove. We need to produce sections: maybe About the role (intro + Why It's Different Here + A Day In The Life?), Responsibilities (Your Everyday Work Includes), Requirements/Qualifications/Skills (Why You’ll Thrive Here attributes), Benefits (Perks & Benefits), Pay (Weekly Pay), Schedule (Sundays Off). Also maybe About the company (Who We Are) could be About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings. We need to avoid repeating job title as heading. Also no Job ID. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. We need to 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. We have specific content for Pay: Weekly Pay: Get a paycheck every Friday. No more waiting every two weeks. Schedule: Sundays Off: Faith, family, friends, and work-life balance. Benefits: list includes Sundays off, Weekly pay, Paid training, Employee referral bonuses, Tuition assistance and scholarship opportunities, Employee Assistance Program, Employee discounts on tires, wheels, accessories, and more, 401(k) with company match up to 6%. We also have other benefits like "Sports Energy", "Career Mode", "People First". Those could be part of About the role or Benefits? They are more cultural aspects. Could be part of About the role. We need to decide sections: - About the role: could include intro paragraph, Why It's Different Here (People First, Career Mode, Sports Energy, Sundays Off, Weekly Pay) maybe but we already have Pay and Schedule separate. Might be redundant. Perhaps we keep About the role as a brief overview: "Part-Time Tire Technician ... backbone of our success..." plus "Why It’s Different Here" bullet points (People First, Career Mode, Sports Energy, Sundays Off, Weekly Pay). But we already have Pay and Schedule sections; we could still include them in About the role but that would duplicate. Better to separate Pay and Schedule as their own sections, and About the role includes intro and cultural aspects except Pay and Schedule. - Responsibilities: "Your Everyday Work Includes" list: Busting tires..., Delighting customers..., Growing... - Requirements / Qualifications / Skills: "Why You’ll Thrive Here" list: Team mindset, Servant leader energy, Hands-on stamina, Strength, Automotive enthusiasm, Preferred: Driver’s license and a high school diploma or equivalent. Could split into Requirements (strength, license, diploma) and Skills (team mindset, servant leader, hands-on stamina, automotive enthusiasm). But we can combine into one section "Requirements" or "Qualifications". The instruction allows multiple headings; we can choose a few substantive sections. Perhaps we do:

  About the role

  with paragraph(s) covering intro and cultural aspects (People First, Career Mode, Sports Energy). Not include Pay and Schedule.

  Responsibilities

  with
  • list.

    Requirements

    with
    • list (Strength, Driver’s license, high school diploma, maybe also Automotive enthusiasm as preferred? Could include as preferred.)

      Benefits

      with
      • list (Sundays off, Weekly pay, Paid training, Employee referral bonuses, Tuition assistance and scholarship opportunities, Employee Assistance Program, Employee discounts..., 401(k) with company match up to 6%).

        Pay

        with

        Weekly pay: Get a paycheck every Friday. No more waiting every two weeks.

        Schedule

        with

        Sundays off: Faith, family, friends, and work-life balance. We also have "Who We Are" company description. Could be part of About the role or separate section "About the company". Not in list of headings but we could still include as About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. We could incorporate company description into About the role paragraph. Thus About the role will include: introductory paragraph, Why It's Different Here (People First, Career Mode, Sports Energy), and Who We Are description. We must not repeat job title as heading. We must not include boilerplate EEO. Now produce HTML fragment. We need to ensure proper nesting:

        About the role

        then

        ... maybe multiple paragraphs. We need to escape any special characters? Not needed. Let's craft content. About the role paragraph: "Part-Time Tire Technician At Discount Tire, we change more than tires. We make dreams come true. As a Part-Time Tire Technician, you are the backbone of our success, keeping customers safe while building a career and life you love. We are a people-first team who cares for each other, serves customers the right way, and wins together in a promote-from-within culture. We’re proud to be recognized as a Glassdoor Best Places to Work 2026 and named one of Forbes’ America’s Best Large Employers for 2026." Then maybe a second paragraph for Why It's Different Here bullet points? But we need to use

        • for any list. So we can make a list for People First, Career Mode, Sports Energy, Sundays Off, Weekly Pay? But we already have Pay and Schedule separate. However the Why It's Different Here includes Sundays Off and Weekly Pay. To avoid duplication, we could still list them but then we would duplicate content. Better to exclude Pay and Schedule from that list and keep them separate. So we can list People First, Career Mode, Sports Energy as bullet points under About the role. Thus:
          • People First: Caring teammates, trusted experts, clean stores, and safety in everything we do
          • Career Mode: Every store leader starts in the bays and earns the keys. Translation: real promotion path
          • Sports Energy: We fuel fans, teams, and athletes through local and national pro sports partnerships
          Then maybe include Who We Are description as another paragraph. Now Responsibilities: list from "Your Everyday Work Includes": - Busting tires: Install, rotate, balance, repair, and clean new tires and wheels - Delighting customers: Providing an inviting, easy, and safe customer experience - Growing: Learn by doing with hands-on, on-the-job training and development We need to preserve the colon phrasing; we can keep as list items. Now Requirements: list from "Why You’ll Thrive Here" plus Preferred. We could separate into Requirements (mandatory) and Preferred (optional). But we can combine. List items: - Team mindset: Former athlete, military team member, or hands-on leader who loves to work with people - Servant leader energy: Calm under pressure, positive can-do attitude, and integrity - Hands-on stamina: On your feet, lifting, moving, and hustling with your teammates - Strength: Ability to lift at least 50 pounds - Automotive enthusiasm: It’s a plus but not required (we will train you) - Preferred: Driver’s license and a high school diploma or equivalent We could also note that Automotive enthusiasm is preferred but not required. Now Benefits: list from "Perks & Benefits": - Sundays off - Weekly pay - Paid training - Employee referral bonuses - Tuition assistance and scholarship opportunities - Employee Assistance Program - Employee discounts on tires, wheels, accessories, and more - 401(k) with company match up to 6% Now Pay: paragraph: "Weekly pay: Get a paycheck every Friday. No more waiting every two weeks." Schedule: paragraph: "Sundays off: Faith, family, friends, and work-life balance." We must ensure we don't duplicate Sundays off and Weekly pay in Benefits and also separate sections. The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state them, so we can have them. However we also have them in Benefits list; that would duplicate content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but duplication might be considered redundant but not wrong. However better to avoid duplication: we could keep Benefits list without Sundays off and Weekly pay, and then have Pay and Schedule sections separate. But the Benefits list originally includes those items; if we remove them, we are omitting substantive information. So we need to keep them somewhere. We could keep them in Benefits list and also have Pay and Schedule sections that just restate them? That would duplicate. Perhaps we can keep Benefits list as is, and not have separate Pay and Schedule sections, but the instruction says we should create Pay/Schedule/Benefits sections only if posting actually states them. It does state them, but we could choose to include them under Benefits and not have separate Pay/Schedule sections. However the instruction says "Prefer a few substantive sections over many thin ones." Having separate Pay and Schedule sections might be thin (just one sentence each). So maybe better to incorporate Pay and Schedule into Benefits section, and not create separate Pay/Schedule headings. But the instruction says "use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but does not require using all. It says "Prefer a few substantive sections over many thin ones." So we could omit Pay and Schedule headings if they'd be thin, and include that info under Benefits. However the Benefits section already includes Sundays off and Weekly pay as items; that is substantive. So we can just have Benefits section with those items. That would satisfy preserving all info. Then we don't need separate Pay and Schedule sections. That seems preferable. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits. We need to ensure we don't create Pay/Schedule sections. Now check if any other sections like Qualifications or Skills needed? We have Requirements covering both. Now produce HTML. We must not include any markdown code fences. Let's craft. HTML:

          About the role

          Part-Time Tire Technician At Discount Tire, we change more than tires. We make dreams come true. As a Part-Time Tire Technician, you are the backbone of our success, keeping customers safe while building a career and life you love. We are a people-first team who cares for each other, serves customers the right way, and wins together in a promote-from-within culture. We’re proud to be recognized as a Glassdoor Best Places to Work 202