Pastry Baker

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat the job title as a heading. 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. IMPORTANT: 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. We need to parse the posting. Given description: Starting Hourly Rate: $16.50, based on experience, interview, and skills test Location: Production Hub – North Liberty Reports to: Pastry Team Leader Employment Type: Full-Time and Part Time, Non-Exempt About New Pioneer Food Co-op ... (description) About The Role ... (description) Requirements (actually they have "What You Will Do" list, then "What Success Looks Like", then "What You’ll Bring"). Compensation & Benefits: description. Why Join New Pioneer: description. We need to map to sections: About the role (maybe "About The Role" heading). Responsibilities: maybe "What You Will Do". Requirements: maybe "What You’ll Bring" (experience, ability). Qualifications maybe not separate. Skills maybe part of requirements. Benefits: "Compensation & Benefits". Pay: Starting hourly rate given. Schedule: maybe not explicit; they mention flexible availability including early mornings, weekends, holidays. That could be schedule info. But we should only include Schedule section if posting actually states them. It does mention flexible availability including early mornings, weekends, and holidays. That's schedule info. So we can include Schedule. We need to avoid filler placeholder text. The posting includes Starting Hourly Rate: $16.50, based on experience, interview, and skills test. That's specific. So Pay section can include that. Benefits: "This position offers competitive hourly pay aligned with market benchmarks for similar cooperative production and food service roles, along with benefits that may include medical, dental, vision, paid time off, staff discounts, and retirement plan options for eligible team members." That's specific enough. We need to output HTML fragment only, no /, no markdown fences. We need to use

  for section headings. Use

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

    for prose. We need to decide which sections to include: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule maybe. Also maybe "About New Pioneer Food Co-op" could be considered "About the company" but not in list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "About New Pioneer Food Co-op" could be considered part of "About the role"? Not exactly. But we could include it under "About the role" maybe as a brief intro. However 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." It doesn't forbid having a section about the company, but the allowed headings list doesn't include "About the company". However we could still include a section with heading

    About New Pioneer Food Co-op

    if we want, but the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. But we could also add other headings if needed, but better to stick to those. Thus we need to fit the company description somewhere. Could be part of "About the role" as a preamble. Or we could drop it? But we must preserve ALL substantive information; cannot drop company description. So we need to include it somewhere. Perhaps we can include a

    before any headings, as introductory prose. That's allowed: we can have prose outside sections. The instruction: "Use

    for section headings ... Use

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

      for prose." It doesn't forbid having prose before headings. So we can put a

      with the company description, then sections. Thus structure:

      About New Pioneer Food Co-op ...

      Then

      About the role

      with prose describing the role. Then

      Responsibilities

      with
      • list of duties (What You Will Do). Then

        Requirements

        with
        • list of what you’ll bring (experience, ability, etc.) maybe also include "What Success Looks Like"? That's more about performance expectations; could be part of Responsibilities or Requirements. But we can treat "What Success Looks Like" as part of Responsibilities or maybe as a separate section? Not in allowed headings. Could incorporate into Responsibilities as prose. We need to preserve all substantive information. So we need to include "What Success Looks Like" details. Could be a

          under Responsibilities after the list. Then

          Benefits

          with
          • list of benefits (medical, dental, vision, paid time off, staff discounts, retirement plan options). Then

            Pay

            with

            Starting hourly rate: $16.50, based on experience, interview, and skills test. Then

            Schedule

            with

            Flexible availability including early mornings, weekends, and holidays. Also employment type: Full-Time and Part Time, Non-Exempt. Could include that. We also have location and reports to; those are minor metadata; we can fold into a short

            maybe after the company description or before sections. The instruction: "fold minor metadata into a short

            or drop it." So we can include a

            with Location: Production Hub – North Liberty; Reports to: Pastry Team Leader; Employment Type: Full-Time and Part Time, Non-Exempt. We must not repeat the job title as a heading. The job title is "Pastry Baker". Not used as heading. We must not include boilerplate like EEO etc. Not present. Now ensure we don't create sections with filler placeholder text. All sections have specific content. Now produce HTML fragment. We need to ensure proper nesting:

            About the role

            then

            ...

            maybe. For lists:
            • ...
            . We need to avoid extra whitespace? Not important. Let's craft. First, company description paragraph: New Pioneer Food Co-op is a community owned, value driven local food marketplace rooted in cooperation, sustainability, and shared success. We exist to strengthen the local food system while creating welcoming spaces for staff, members, and partners to thrive. Then metadata paragraph: Location: Production Hub – North Liberty. Reports to: Pastry Team Leader. Employment Type: Full-Time and Part Time, Non-Exempt. Then About the role heading and paragraph: The Pastry Baker supports daily production in the Pastry while helping create the high quality, fresh pastry New Pioneer is known for. This role participates in pastry preparation and baking, recipe scaling and measuring, rotation and storage, sanitation, and pre-pack and display support, contributing to consistent production for the co-op's retail, deli, and catering needs. Pastry Bakers play an important role in upholding the craft, quality, and food safety standards that define New Pioneer Pastry while supporting the overall success of the production team. Then Responsibilities heading and list: Prepare and bake pastry items following recipes, prep lists, and production deadlines Accurately scale pastry recipes and measure dry and liquid ingredients by weight and volume Prepare batters, mixes, fruit fillings, and custards, and support baking of specialty cakes, pies, and pastries Support basic cake decorating and lettering following New Pioneer standards Properly rotate and store prepared and received items to maintain quality, freshness, and health code compliance Maintain cleanliness and sanitation of workstations, ovens, walk-ins, and storage areas Complete pre-pack items with fresh and accurately labeled product Then maybe a paragraph for What Success Looks Like: Pastry is produced consistently to recipe, quality, and presentation standards; production deadlines and daily prep lists are met reliably; workstations, ovens, and storage areas remain clean, sanitary, and organized; pre-packaged items are fresh, properly identified, and accurately priced; team members contribute positively to production culture and workflow. Then Requirements heading and list (What You’ll Bring): Pastry baking, bakery, or food service experience preferred Willingness to learn recipe scaling, measuring, fillings, custards, and basic decorating Ability to work in a fast paced, team oriented production environment Strong attention to detail and reliability Commitment to food safety and sanitation standards Ability to lift up to 50 pounds regularly, stand for extended periods, and work near ovens and in walk-ins Flexible availability including early mornings, weekends, and holidays But note flexible availability also appears in schedule; we might duplicate. Could keep in Requirements as ability, but also schedule section. Might be okay. Then Benefits heading and list: Medical Dental Vision Paid time off Staff discounts Retirement plan options for eligible team members But the text says "benefits that may include medical, dental, vision, paid time off, staff discounts, and retirement plan options for eligible team members." So we list those. Then Pay heading and paragraph: Starting hourly rate: $16.50, based on experience, interview, and skills test. Then Schedule heading and paragraph: Flexible availability including early mornings, weekends, and holidays. Employment type: Full-Time and Part Time, Non-Exempt. But we already included employment type in metadata paragraph; we could avoid duplication. Perhaps we put employment type only in metadata paragraph, and schedule only about flexible availability. Let's keep metadata paragraph separate, schedule only about flexible availability. Thus metadata paragraph: Location: Production Hub – North Liberty. Reports to: Pastry Team Leader. Employment Type: Full-Time and Part Time, Non-Exempt. Schedule paragraph: Flexible availability including early mornings, weekends, and holidays. Now ensure we haven't missed any substantive info: "About New Pioneer Food Co-op" covered. "About The Role" covered. "What You Will Do" covered as responsibilities list. "What Success Looks Like" covered as prose after responsibilities. "What You’ll Bring" covered as requirements list. "Compensation & Benefits" covered as benefits list and pay. "Why Join New Pioneer" covered? That's a paragraph at end: "Why Join New Pioneer At New Pioneer, every role contributes to a shared mission of building stronger communities through food, service, and cooperation. As a Pastry Baker, you help craft the fresh, high quality pastry our shoppers and members count on every day." That's substantive; we need to preserve it. Where to put? Could be a separate section maybe "About the