Seasonal Sanitation Operator

We need to output HTML fragment with sections only when content exists. No job title heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Content: - Intro about company, but not needed? It's part of description maybe "About the role"? Actually "About the role" could be a short paragraph describing role. The posting includes description of Sanitation Operators responsibilities. So we can have "About the role" paragraph summarizing: Sanitation Operators clean and sanitize inside store, parking lot, area around building, etc. Also mention flexible seasonal staffing, entry-level, no experience needed. - Responsibilities: list of duties: sweep all required areas inside and outside; mopping; spray parking lots and wash shop windows; clean, sanitize and stock bathrooms; ensure customer area clean and tables/chairs sanitized; keep supplies in stockroom orderly. - Requirements: maybe "No previous experience necessary", "Must be 18 years of age or over", "Has a steadfast commitment to nurture an equitable, unbiased culture where our peeps are empowered to showcase their originality." That's more like a value statement. Also "Effective communication skills, both written and verbal", "Must be authorized to work in the US without sponsorship." Also maybe "Physical demands" could be part of Requirements? But there is a separate "PHYSICAL DEMANDS AND WORKING CONDITIONS" section. We could treat that as Requirements or maybe as a separate section like "Physical Demands". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put physical demands under Requirements or Qualifications. Probably Requirements. - Qualifications: maybe none separate; but we could combine with Requirements. - Skills: maybe "Effective communication skills" etc. - Benefits: "Weekly Pay", "Career opportunities- we are growing!" Also "WHY KRISPY KREME?" includes culture, belonging, loving communities, loving planet. Those could be Benefits? But they are more about company. However we have to include Benefits section only if posting actually states them. It does state "Weekly Pay" and "Career opportunities- we are growing!" Also maybe "Perks". So we can include Benefits with those items. - Pay: The posting mentions "Weekly Pay" but not specific amount. The rule: do NOT create Pay section unless posting actually states them. It states "Weekly Pay" but not amount. Is that enough? It says "Weekly Pay" as a perk. That is a statement about pay frequency, not amount. The rule says: 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. It does state "Weekly Pay". That's a statement about pay, albeit not amount. I'd say we can include Pay section with that statement. However we also have Benefits section that could include "Weekly Pay" as a benefit. Might be duplication. Better to put Pay section with "Weekly Pay" and Benefits with "Career opportunities- we are growing!" and maybe other culture points. - Schedule: Not mentioned explicitly. There's mention of flexible, seasonal staffing model, peak seasons. No specific schedule. So we should not create Schedule section. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes EEO statement at end: "Krispy Kreme is an Equal Opportunity Employer: ..." That's boilerplate; remove. Also "About Krispy Kreme" description maybe not needed? It's about company; could be considered "About the role"? Might be okay to include as part of About the role? But the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." The "About Krispy Kreme" is not minor metadata; it's company overview. Could be considered part of "About the role"? Might be okay to include as a paragraph under About the role. However we should preserve all substantive information; not invent or summarize away detail. The company overview is substantive but not about the role. However we have no heading for company overview; we could include it as a paragraph before sections? The instruction: output only HTML fragment; we can include

paragraphs not under headings? Probably we should stick to the allowed headings; any content not fitting could be placed under appropriate heading or omitted if not relevant. The company overview may be considered "About the role"? Not exactly. But we could treat it as "About the role" includes both role description and company context. That might be acceptable. We must not include duplicated lines. Ensure we don't repeat. Let's extract content: About the role paragraph: "Since its founding in 1937, Krispy Kreme’s focus has remained the same - making fresh doughnuts using our founder’s original recipe. The brand’s iconic Hot Light lets consumers know when doughnuts are being made in the shop so they can stop in and enjoy them hot, right off the line. Our Sanitation Operators have the responsibility of cleaning and sanitizing the inside of the store, the parking lot, and the area around the building. We love creating a welcoming environment for our customers, and that begins with the cleanliness of our locations. During peak seasons, we rely on a flexible, seasonal staffing model to ensure our A-Glazing customers receive friendly, efficient service and a well-maintained store appearance. No previous experience is required for this entry-level opportunity—you just need the motivation to learn, grow, and thrive in a dynamic, fast-paced, team-oriented environment. Join us for a fun and rewarding seasonal experience!" That seems good. Responsibilities list: bullet points from "A TASTE OF WHAT YOU WILL BE DOING:" and following lines. List: - Sweep all required areas inside and outside of the store. - Responsible for mopping all required areas inside the store. - You will be tasked with spraying the parking lots and washing our shop windows. - Clean, sanitize and stock our bathrooms. - Make sure our customer area is clean and all tables and chairs are sanitized. - Keep the supplies in the stockroom in an orderly fashion. We could combine first two as separate items. Requirements: list: - No previous experience necessary - Must be 18 years of age or over. - Has a steadfast commitment to nurture an equitable, unbiased culture where our peeps are empowered to showcase their originality. - Effective communication skills, both written and verbal. - Must be authorized to work in the US without sponsorship. Physical demands could be added as requirements but maybe better as separate? Since we don't have a heading for physical demands, we could include under Requirements as a sublist? But we should not invent headings. We could add a paragraph under Requirements describing physical demands. However the physical demands details are substantive; we should preserve them. We could add a

under Requirements summarizing physical demands: "Exerting up to 50 pounds of force occasionally, and/or up to 20 pounds of force frequently, and/or up to 10 pounds of force constantly to move objects. Exposure to internal and external environmental conditions; shop – fluctuating temperatures and noise levels; exposure to known allergens including but not limited to nuts; noise of a production and/or processing area." Also note reasonable accommodations. We could also add a separate section "Qualifications" but we don't have distinct qualifications beyond requirements. Could combine. Skills: maybe "Effective communication skills" already listed; but we could separate skills: effective communication skills (written and verbal). Also maybe "commitment to nurture equitable culture" is more of a requirement. We could make Skills section with "Effective communication skills (written and verbal)". But we already have that in Requirements; duplication not ideal. Better to keep Requirements include communication skills, and Skills maybe empty -> we should not create empty heading. So we omit Skills. Benefits: list: - Weekly Pay - Career opportunities - we are growing! - Loving People: Leadership Mix etc? That's more culture; but could be considered benefit. However the instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The "WHY KRISPY KREME?" section includes specific content about Loving People, Belonging, Loving Communities, Loving Planet. Those are specific. Could be considered Benefits? Might be better to put under Benefits as bullet points describing company culture and perks. However the heading "Benefits" is allowed; we can include those as benefits. But we already have Weekly Pay and Career opportunities under Benefits; we could also add the culture points. Pay: we could have Pay section with "Weekly Pay". But then Benefits would duplicate Weekly Pay. Better to put Weekly Pay under Pay, and Benefits include career opportunities and culture points. Thus: Pay:

Weekly Pay

Benefits:

• Career opportunities – we are growing!
• Loving People: Our global culture is best captured by our Leadership Mix, a dozen behaviors that define how we work with one another across the world and give back to our communities.
• Belonging happens once each Krispy Kremer knows their bold authentic self is welcomed, dignified, and loved, where their wonderfully original identities flourish and thrive.
• Loving Communities: At Krispy Kreme, sharing joy is at the center of everything we do, and we strive to inspire this in our communities. Our brand purpose truly shines through our Acts of Joy and community fundraising initiatives. In the U.S., we have been donating unsold doughnuts to local food banks, with a goal of bringing a smile to our consumers as they enjoy a small, sweet treat. We partner with Feeding America and Convoy of Hope, who in turn partner with organizations nationwide to distribute donations to people in need through diverse types of programs and services. In 2022, we helped community groups raise $40 million globally. Last year in the U.S., we supported more than 83,000 fundraising events, raising nearly $37 million.
• Loving Planet: We have been conducting a multi-year global GHG emissions assessment to establish an emissions baseline, using this foundation to soon set goals for greenhouse gas emission reductions. We are working on reducing food waste through donation efforts, animal feed, and composting programs.

We need to ensure we don't include boilerplate like EEO statement. Also remove duplicated lines. Check for any duplicated lines: The posting includes "The above statements are intended to describe the general nature of work performed by the employees assigned to this job and are not the official job description for the position. The official job description will be provided during the application/interview process." That's boilerplate; remove. Also "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." That's part of physical demands; we can keep. Now construct HTML. We'll start with

About the role

then

...

Then

Responsibilities

with li items. Then

Requirements

with li items (including physical demands as a paragraph? Could be li as well). Physical demands could be a li: "Exerting up to 50 pounds of force occasionally, and/or up to 20 pounds of force frequently, and/or up to 10 pounds of force constantly to move objects; exposure to internal and external environmental conditions (shop – fluctuating temperatures and noise levels); exposure to known allergens including but not limited to nuts; noise of a production and/or processing area. Reasonable accommodations may be made