Ice Cream Server - Astoria

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Intro paragraph about company mission etc. Could be "About the role" or maybe "About the company"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description of role and company mission. - Responsibilities: list of duties. - Requirements: list of requirements. - Qualifications: maybe combine with requirements? The posting includes "Job Requirements" list. Could treat as Requirements. Qualifications maybe not separate; but we could include if there is content like "Food handlers certificate required". That's a qualification. Could put under Qualifications. - Skills: maybe not explicit; but we could infer from responsibilities: people skills, dexterity, etc. However we should not invent content. Only include if posting actually states them. The posting mentions "strong people skills", "genuine passion for ice cream", "self-starters", "thrive independently and as part of a team", "positive energy". Those could be skills. But they are in the description before responsibilities. Could put under Skills. - Benefits: posting mentions "Competitive Pay + Tips", "Flexible Scheduling", "Free Ice Cream (One menu-item while on shift)", "Positive team environment", "Career development and growth opportunities", "Opportunity to be part of a growing, fun brand!". Also "Van Leeuwen Ice Cream is committed to pay transparency...". So we can include Benefits section with those bullet points. - Pay: posting says "Part Time Scoopers at Van Leeuwen's scoop shops make $17.00 per hour + an average of an additional $7 per hour in tips! Tips are based on averages and subject to seasonal fluctuation." Also "Hourly Range $17—$17 USD". So we can include Pay section with that info. - Schedule: posting says "Our team members must have availability to work at least three shifts per week and be available to work past 12am." Also "Available to work 3 days a weeks (including nights and weekends past 12 am)". So schedule section. We must not include sections with placeholder or vague like "commensurate with experience". Not present. We must not include duplicated lines. Remove boilerplate like EEO etc. The posting includes EEO statements at end: "Van Leeuwen Ice Cream is committed to pay transparency and equity..." and "Van Leeuwen Ice Cream complies with Equal Employment Opportunity laws..." and "As an equal opportunity employer...". Those are boilerplate/legal; we should remove them. Also "Here at Van Leeuwen, Good Ice Cream Is For Everyone!" maybe borderline but it's part of mission; could be included in About the role? It's not boilerplate; it's a statement about inclusivity. Might keep as part of About the role. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact details like "$17.00 per hour + an average of an additional $7 per hour in tips!" etc. We need to use

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

  for prose. We must output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  We started Van Leeuwen Ice Cream in a yellow truck on the streets of NYC in 2008 with a mission to make good ice cream that makes you feel good. Nowadays, people can spend so much time on what’s “healthy” they don’t stop to consider what’s healthy. As far as we’re concerned, happiness is healthiness. We strive to ensure every scoop, store and employee feels and creates one community to contribute to the overall brand. Van Leeuwen Ice Cream is hiring part-time Scoopers to join our Astoria ice cream shop in Queens, NY! Our Scoopers are the ultimate Van Leeuwen ambassadors, bringing our high standards and hospitality to life in every guest interaction. We’re looking for self-starters who thrive independently and as part of a team in a fast-paced, high-energy environment. The ideal candidate brings positive energy, strong people skills and a genuine passion for ice cream! Here at Van Leeuwen, Good Ice Cream Is For Everyone! As an equal opportunity employer, we strive to foster a welcoming, diverse environment for every employee and customer. We pride ourselves on the creativity that goes into our ice cream and is built in our stores (by YOU) that help us meet our missions and values.

  But note: The equal opportunity employer statement is boilerplate/legal? It's part of EEO. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that sentence. Also "Here at Van Leeuwen, Good Ice Cream Is For Everyone!" maybe okay as it's not EEO but a mission statement. However the sentence after that is EEO. We'll remove the EEO sentence. Keep the "Here at Van Leeuwen, Good Ice Cream Is For Everyone!" as part of About the role. Thus About the role paragraph: combine mission, hiring, role description, ideal candidate traits, and the Good Ice Cream line. Now Responsibilities: list each duty. From posting: - Greet every guest warmly, with enthusiasm and genuine hospitality - Able to scoop and serve guests all menu items while maintaining quality and presentation standards - Serve as a Van Leeuwen Ambassador, educating guests on flavors, ingredients and special offerings - Prepare all fresh, house made menu items daily - Accurately operate our Square POS System for a seamless guest checkout process - Ability to become familiar with all food safety procedures and follow them as required - Maintain store cleanliness, following proper sanitation guidelines - Complete daily tasks, including stocking, inventory, and cleaning - Follow Van Leeuwen's established safety, grooming, uniform, and employee conduct standards We'll put each as
• . Requirements: list: - Must be 18 years of age or older - Genuine passion for ice cream and desserts - Possess dexterity to prepare and serve guests all menu items in accordance with established service and build-out standards - Able to push/pull/lift 50 lbs of weight regularly - Stand for extended periods of time regularly - Walk up and down stairs regularly - Stand, bend and reach for prolonged periods of time - Ability to thrive in a fast-paced environment - Available to work 3 days a weeks (including nights and weekends past 12 am) - Reliable, on time and ready for every shift - Food handlers certificate required Note: "Available to work 3 days a weeks (including nights and weekends past 12 am)" appears also in schedule; but we can keep in Requirements as it's a requirement. Might duplicate; but we should not duplicate lines. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should avoid duplicated lines. The schedule info appears also in schedule section; we need to decide where to place it. Probably better to put schedule info under Schedule section, and not duplicate in Requirements. However the requirement list includes that line; we could keep it in Requirements and not duplicate in Schedule, but then Schedule would be missing that info. However schedule section expects schedule specifics; we could include schedule details like "must have availability to work at least three shifts per week and be available to work past 12am." That's similar but not identical. The requirement line says "Available to work 3 days a weeks (including nights and weekends past 12 am)". The schedule line from earlier: "Our team members must have availability to work at least three shifts per week and be available to work past 12am." Slightly different wording but same meaning. To avoid duplication, we could keep one version. Perhaps keep the requirement line under Requirements, and schedule section could include other schedule details like shift timing? But there is no other schedule detail. The schedule section could be omitted if we consider the requirement covers schedule. However the instruction says include a section ONLY when the posting has real, specific content for it. The posting does have schedule info (availability to work at least three shifts per week and past 12am). So we should have a Schedule section with that content. To avoid duplication, we could paraphrase slightly but must preserve all substantive information; we cannot summarize away detail. We need to keep the exact info. If we include both, we would duplicate the same info (just reworded). That's duplication. Better to keep the exact phrase from the posting under Schedule, and not include it under Requirements. But the Requirements list includes that line; we could remove it from Requirements to avoid duplication, but then we lose that requirement info. However the requirement is also a requirement; we could keep it under Requirements and not duplicate in Schedule, but then Schedule would be missing that info. However the schedule info is also a requirement; maybe we can treat schedule as separate but we can include the same sentence; duplication is not allowed. The instruction says remove duplicated lines. So we must not have the same line appear twice. We need to decide where to place it. Which section is more appropriate? The line is about availability to work 3 days a week including nights and weekends past 12 am. That's both a requirement and schedule info. Could place under Requirements (as it's a requirement) and then Schedule section could be omitted or include other schedule details like shift length? There's no other schedule detail. The posting also says "must have availability to work at least three shifts per week and be available to work past 12am." That's essentially same. So we could keep one version under Requirements and not have a Schedule section. But the instruction says include a section ONLY when the posting has real, specific content for it. If we omit Schedule, we are not including a schedule section despite having schedule info; but we could argue that schedule info is covered under Requirements. However the instruction expects us to create sections like Schedule when there is schedule info. But we must avoid duplication. Perhaps we can keep the schedule info under Schedule and remove it from Requirements, but then we lose a requirement. However the requirement is about availability; it's still a requirement but we could note that it's covered under Schedule. But the instruction says preserve ALL substantive information; we cannot omit it. So we need to keep it somewhere. If we put it under Schedule, we still preserve it. Then we can remove it from Requirements list to avoid duplication. That would still preserve the info. The Requirements list would then lack that line, but the info is still present under Schedule. Is that acceptable? The requirement about availability is still preserved, just under a different heading. The instruction didn't say we must keep the exact categorization; just preserve all substantive information. So moving it to Schedule is okay as long as we don't lose it. However the Requirements list originally had many items; removing one might make the list thinner but still okay. Alternatively, we could keep both but slightly rephrase to avoid exact duplication. The instruction says "Remove duplicated lines". If we rephrase, it's not a duplicated line. But we must preserve the substantive information; we could keep both but with different wording. However the requirement line is exactly "Available to work 3 days a weeks (including nights and weekends past 12 am)". The schedule line is "Our team members must have availability to work at least three shifts per week and be available to work past 12am." They are not identical but convey same meaning. They are not duplicated lines exactly; they are different phrasing. So we could keep both; they are not exact duplicates. The instruction likely means exact duplicate lines, not similar meaning. So we can keep both. That would preserve all info