Geek Squad Installation Helper

We need to output HTML fragment with sections: headings using

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 paragraph: "As a Geek Squad Installation Helper, you’ll travel from your Best Buy store to clients’ homes to assist with the delivery and basic installation of technology products alongside a seasoned Agent. You’ll provide our clients with service that exceeds their expectations by handling appointments with care, asking the right questions to enhance their experience and providing prompt follow-up on recommendations. This role, known internally as a Cadet, is a great opportunity to build a career with Geek Squad by learning about our products and services. It offers the chance to increase skills through training and on-the-job experience." That's prose; could be under "About the role" or maybe "Responsibilities"? Actually it's description of role. Could be "About the role". We'll put that as

. Then "What You’ll Do" bullet list: Perform a variety of duties for clients in their homes, including delivery, installation and networking, with a primary focus on home theater technology; Maintain contact with clients to reveal diagnostic discoveries and make recommendations for protecting their devices; Help manage inventory and vehicle maintenance; Provide feedback and training to store teams and assist with in-store repairs. That's a list of duties; we can put under

Responsibilities

with

• . Then "Basic Qualifications" list: Experience actively using and learning about consumer electronics; Ability to work successfully as part of a team; Ability to prioritize and multi-task in a fast-paced environment; Ability to work a flexible schedule, including holidays, nights and weekends; Must be at least 21 years old; Must have a current, valid driver's license; Must have no more than two moving violations and/or at-fault accidents within the past three years; Must have no DUI/DWI or reckless driving violations in the past three years; Ability to lift 75 pounds with or without reasonable accommodation and up to 150 pounds with help. That's qualifications; we can put under

  Requirements

  (or Qualifications). The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have both Basic Qualifications and Preferred Qualifications. Could combine into Requirements (basic) and maybe Skills (preferred). Let's decide: Use

  Requirements

  for basic qualifications. Use

  Preferred Qualifications

  for the preferred qualification (6 months of consumer electronics experience). Or we could put under Skills. But better to follow the posting: "Preferred Qualifications". Use heading "Preferred Qualifications". That's allowed? The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples, but we should stick to those. However we can still use "Preferred Qualifications" as a heading? Might be considered not in list but still a section heading. Safer to map preferred qualifications under "Skills" or "Qualifications". Since we already have Requirements for basic qualifications, we could put preferred under "Skills". But the preferred qualification is experience, not a skill per se. Could also put under "Qualifications". But we already used Requirements; maybe we can have both Requirements and Qualifications sections: Requirements = basic qualifications, Qualifications = preferred qualifications. That fits the examples. Thus:

  Requirements

  with basic qualifications list.

  Qualifications

  with preferred qualification: 6 months of consumer electronics experience (sales, operations or technology services). Now Benefits: The posting includes "What’s In It For You" with bullet list: Competitive pay, Great employee discount, Financial savings and retirement resources, Support for your physical and mental well-being. Also mentions leaves of absence, PTO, incentive pay etc. That's benefits info. So we can create

  Benefits

  with a list. Pay: The posting mentions "Competitive pay" but not specific numbers. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay" as a benefit, but not a specific amount. Is that enough to create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "states them" meaning actual content, not placeholder like "commensurate with experience". "Competitive pay" is a statement, albeit vague. It's still stating that there is competitive pay. I'd say we can include a Pay section with that statement. However they also say "Prefer a few substantive sections over many thin ones." Might be better to incorporate pay into Benefits section, as it's a benefit. Since Benefits already includes competitive pay, we could omit separate Pay section. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid having Pay as part of Benefits. But we already have Benefits section; we can include competitive pay there. So we may not need separate Pay. Schedule: The posting mentions ability to work a flexible schedule, including holidays, nights and weekends (under basic qualifications). That's a requirement, not schedule details. No explicit schedule like full-time/part-time? It says Position Type: Full time later. That's schedule info. The posting includes "Position Type: Full time". That's schedule info. So we could create a Schedule section with "Full time". However the instruction: never create Schedule section unless posting actually states them. It does state Position Type: Full time. So we can include Schedule section with that. But we also have "Ability to work a flexible schedule, including holidays, nights and weekends" as a requirement. Could be part of Requirements. Thus we will have sections: - About the role (intro paragraph) - Responsibilities (What You’ll Do) - Requirements (Basic Qualifications) - Qualifications (Preferred Qualifications) - Benefits (What’s In It For You) - Schedule (Position Type: Full time) We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: EEO, equal opportunity, application deadline, application instructions, etc. Also remove "About Us" maybe? The "About Us" section is generic corporate description; could be considered boilerplate? It's not required to keep; but it's substantive about company culture. 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 could be considered generic. However it's not duplicated. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Us" paragraph is substantive about company purpose. I'd keep it maybe under a section "About the company"? But we only have allowed headings; we could put it under "About the role"? Already used for intro. Could add another section "About Best Buy" but not in list. Safer to omit it? The instruction says preserve ALL substantive information; but also says prefer a few substantive sections over many thin ones. The About Us is somewhat generic but still substantive. However many job postings include it; but we might consider it boilerplate? Not sure. The instruction didn't list "About Us" as boilerplate to remove. It listed cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So About Us is not those. So we should keep it. Thus we could add a section "About the company" but not in the list of example headings. However we could put it under "About the role"? Already used for role description. Maybe we can add a heading "About Best Buy" as

  About Best Buy

  . 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 says e.g. So we can use other headings as long as they are descriptive. I'd keep it as a separate section. But to be safe, we could incorporate About Us into a paragraph after the intro, maybe as part of "About the role"? Could combine. Let's decide: We'll have sections:

  About the role

  with intro paragraph.

  Responsibilities

  with list.

  Requirements

  with basic qualifications list.

  Qualifications

  with preferred qualification.

  Benefits

  with list.

  Schedule

  with "Full time". Optionally

  About Best Buy

  with the About Us paragraph. But that adds many sections; maybe we can combine About Us into Benefits? No. Given instruction to prefer few substantive sections over many thin ones, maybe we should omit About Us as it's generic and not essential to the role. However they said preserve ALL substantive information; About Us is substantive about company purpose. But it's also generic fluff. I'd lean to keep it but maybe as a short paragraph without heading? Could just put as

  after other sections without heading. That's acceptable: we can have free

  not under heading. The instruction only says use headings for sections; doesn't forbid stray paragraphs. So we can keep About Us as a paragraph without heading. Thus final HTML:

  About the role

  As a Geek Squad Installation Helper, you’ll travel from your Best Buy store to clients’ homes to assist with the delivery and basic installation of technology products alongside a seasoned Agent. You’ll provide our clients with service that exceeds their expectations by handling appointments with care, asking the right questions to enhance their experience and providing prompt follow-up on recommendations. This role, known internally as a Cadet, is a great opportunity to build a career with Geek Squad by learning about our products and services. It offers the chance to increase skills through training and on-the-job experience.

  Responsibilities

  • Perform a variety of duties for clients in their homes, including delivery, installation and networking, with a primary focus on home theater technology
  • Maintain contact with clients to reveal diagnostic discoveries and make recommendations for protecting their devices
  • Help manage inventory and vehicle maintenance
  • Provide feedback and training to store teams and assist with in-store repairs

  Requirements

  • Experience actively using and learning about consumer electronics
  • Ability to work successfully as part of a team
  • Ability to prioritize and multi-task in a fast-paced environment
  • Ability to work a flexible schedule, including holidays, nights and weekends
  • Must be at least 21 years old
  • Must have a current, valid driver's license
  • Must have no more than two moving violations and/or at-fault accidents within the past three years
  • Must have no DUI/DWI or reckless driving violations in the past three years
  • Ability to lift 75 pounds with or without reasonable accommodation and up to 150 pounds with help

  Qualifications

  • 6 months of consumer electronics experience (sales, operations or technology services)

  Benefits

  • Competitive pay
  • Great employee discount
  • Financial savings and retirement resources
  • Support for your physical and mental well-being
  • Different types of leaves of absence (LO