Demonstrator

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - About the role / The Role and Why It's Important - Responsibilities (What You'll Do) - Requirements / Qualifications (Your Skills, Education And Experience) - Physical Requirements - Working Environment - Maybe Benefits? But the posting doesn't mention benefits explicitly. - Pay? Not mentioned. - Schedule? It says "Daytime Shifts" in the beginning, but that's minimal. Rules: - Use

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

• for lists,

  for prose. - Do NOT repeat job title as 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. - 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. Now, let's parse the content: The posting starts with "Additional Considerations (if Any) Daytime Shifts" - this seems like a header. Then "At Hy-Vee our people are our strength..." - that's about the company. "Job Description Job Title: Demonstrator Department: General FLSA: Hourly Revision Date: 07/2026" - metadata, should be folded into a short

  or dropped. Since it's minor metadata, I'll include a brief paragraph. "About Hy-Vee" - company description. "The Role and Why It's Important" - about the role. "What You'll Do" - responsibilities list. "Your Skills" - skills/requirements. "Reporting Relationships" - reporting structure. "Education And Experience" - education/experience. "Physical Requirements" - physical requirements. "Working Environment" - working environment. "Are you ready to smile, apply today. Employment is contingent upon the successful completion of a pre employment drug screen." - application instruction and drug screen note. Should remove application instructions, but drug screen is a requirement? Might be part of requirements. Also "Additional Considerations (if Any) Daytime Shifts" - schedule info: daytime shifts. Could be a Schedule section. But the rule: never create Schedule section unless posting actually states them. It says "Daytime Shifts" - that's a schedule mention. Could include a Schedule section with that info. Benefits? Not mentioned. Pay? Not mentioned. Now, I need to structure sections with h3 headings. Possible sections: - About the Role (or About Hy-Vee and The Role) - Responsibilities - Requirements (or Qualifications) - could combine Skills, Education, Reporting, Physical, Working Environment? But better to separate if substantive. The rules say: use h3 for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I should create sections only when there is real content. Let's map: 1. About the Role: includes "About Hy-Vee" and "The Role and Why It's Important". Could be one section with two paragraphs. 2. Responsibilities: "What You'll Do" list. 3. Requirements: could include "Your Skills", "Education And Experience", "Reporting Relationships", "Physical Requirements", "Working Environment". But these are distinct. Might create separate sections for each if they have enough content. But the rule: prefer a few substantive sections over many thin ones. However, each of these has specific content. Physical Requirements and Working Environment are distinct. Reporting Relationships is a short list. Education and Experience is short. Skills is a list. I could group under "Qualifications" or "Requirements" with sub-lists? But the HTML should be flat with h3 headings. Could have multiple h3 sections. Let's see typical structure: About the Role, Responsibilities, Qualifications (including Skills, Education, Experience), Physical Requirements, Working Environment, Schedule (if any). Reporting Relationships could be part of Qualifications or separate. I'll create: - About the Role - Responsibilities - Qualifications (including Skills, Education & Experience, Reporting Relationships) - Physical Requirements - Working Environment - Schedule (daytime shifts) But the rule: never create Schedule unless posting actually states them. It does state "Daytime Shifts". So include. Also, the metadata: Job Title, Department, FLSA, Revision Date. Should fold into a short

  at top or bottom. I'll put at top in a paragraph. Now, remove boilerplate: "Are you ready to smile, apply today." - application instruction, remove. "Employment is contingent upon the successful completion of a pre employment drug screen." - that's a condition of employment, could be part of Requirements or a note. I'll include in Qualifications or a separate note. Also "Additional Considerations (if Any) Daytime Shifts" - that's the schedule. Now, write HTML. I'll start with a paragraph for metadata. Then sections. Let's draft:

  Job Title: Demonstrator | Department: General | FLSA: Hourly | Revision Date: 07/2026

  About the Role

  At Hy-Vee, we believe the shortest distance between two people is a smile. We're seeking people with a passion for customer service, a willingness to learn, and a commitment to being part of a team that strives to make our customers' lives easier, healthier and happier.

  Our Demonstrators bring products to life for customers, offering samples, sharing knowledge, and making the shopping experience more engaging and fun. In this role, you'll prepare and present product demonstrations, answer customer questions, and make suggestions that help customers discover new favorites. If you are personable, enthusiastic, and love sharing your passion for great products with others, we'd love to have you on our team.

  Responsibilities

  • Provide prompt, friendly customer service by greeting customers with a smile, learning their names, and making every interaction a positive one
  • Prepare product for sampling and offer samples to customers throughout your shift
  • Answer customer product-related questions and explain products, making suggestions on preparation and use
  • Organize items needed for the demonstration and ensure adequate supplies are available
  • Stock supplies needed for the demonstration and keep the work area clean and organized at all times
  • Practice proper sanitation procedures throughout your shift
  • Answer the telephone promptly and provide friendly, helpful service to customers who call
  • Work with co-workers as a team to ensure customer satisfaction and a pleasant work environment
  • Assist in other areas of the store as needed and take on special projects as assigned
  • Maintain strict adherence to personal hygiene, dress standards, and all Hy-Vee policies and store guidelines
  • Report to work when scheduled and on time

  Qualifications

  Skills

  • Follow detailed written or verbal instructions and work through tasks with a few concrete variables
  • Perform simple addition and subtraction, copy figures, and count and record accurately
  • Engage confidently with customers, offer helpful advice, and make product recommendations in a friendly, professional manner

  Education & Experience

  • High school diploma or equivalent experience required
  • Less than six months of similar or related work experience preferred

  Reporting Relationships

  • Accountable and reports to: Store Director; Store Manager; Assistant Managers of Store Operations, Perishables, and Health Wellness Home; Service Managers

  Physical Requirements

  • Physical activity is incidental to the core duties of the role
  • Occasionally walk the floor or facility to observe operations, staff, or product
  • Where applicable to the role: ability to occasionally handle product for demonstration purposes
  • No regular lifting, carrying, or physical exertion required

  Working Environment

  This is a fast-paced role in a retail store environment where you will be on your feet throughout your shift. You will have daily exposure to dirt and noise, with occasional potential for electrical hazards. Safety is always a priority, and training is provided to help ensure a safe and supportive work environment.

  Schedule

  Daytime shifts.

  Additional Requirements

  Employment is contingent upon the successful completion of a pre-employment drug screen.

  But the rule: use

  for section headings. Should I use h4 for subsections? The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid h4, but it says use h3 for section headings. Could use h3 for all top-level sections. For subsections like Skills, Education, Reporting, maybe they are part of Qualifications. Could make them separate h3 sections? But that would be many thin sections. The rule: prefer a few substantive sections over many thin ones. So grouping under Qualifications with h3 and then using h4 or just lists with bold? But the output should be semantic HTML. Using h4 is okay, but the rule didn't mention h4. However, it's not prohibited. But to be safe, I could make them separate h3 sections: Skills, Education & Experience, Reporting Relationships. But they are thin. The rule says never emit a heading followed by filler/placeholder text. These have real content. But they are small. Could combine into one Qualifications section with sub-lists. I think using h3 for Qualifications and then using

  for subsections is acceptable. But the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists Skills as an example of a section heading. So maybe they expect Skills as a separate h3 section. Similarly, Education and Experience could be separate. But the rule also says "Prefer a few substantive sections over many thin ones." So I need to judge. Given the content, I'll create separate h3 sections for Skills, Education & Experience, Reporting Relationships? That might be too many. But the example includes Skills as a possible heading. However, the posting has "Your Skills" as a heading. Could make it a section. Let's see: The posting has "Your Skills", "Education And Experience", "Reporting Relationships", "Physical Requirements", "Working Environment". Each has content. I'll make each an h3 section. But then "Qualifications" is not a heading in the posting. The rule says use h3 for section headings like Qualifications. But we can use the headings from the posting. I'll do: - About the Role - Responsibilities - Skills - Education & Experience - Reporting Relationships - Physical Requirements - Working Environment - Schedule - Additional Requirements (drug screen) But the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule is stated (Daytime Sh