After School Children

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Job Title line: "Children's Cooking Teacher CHULA VISTA". Not used as heading. We need to extract sections: - About the role: maybe the introductory paragraph: "Are you ready to TURNIP the BEET on what Kids Eat®? SFC San Diego LLC dba Sticky Fingers Cooking® is looking for enthusiastic part-time Chef Teacher to help us Cultivate COOLinary Curiosity in Kids®! If you're passionate about cooking, have experience teaching or coaching kids, and are looking for a fun, flexible, and meaningful part-time job, we want to meet you!" That's about the role. - Why You'll Love This Job: bullet points: Make an Impact..., Flexibility..., Supportive Team..., Fun Atmosphere..., This is a temporary position with potential for year-round part-time employment based on performance and business needs. Could be part of About the role or maybe Benefits? But we have Benefits section later. - What You'll Do: list of duties: Lead Hands-On Cooking Classes..., Spark Creativity..., Stay Organized..., Communicate via text..., Be the Face of Fun... That's responsibilities. - Who You Are: list of qualifications/experience: Experienced teaching or coaching kids..., Available to teach..., Punctual..., Must arrive..., Varies per school..., Able to commit..., Have or willing to obtain ServSafe..., Lift up to 30 lbs..., Must have reliable transportation..., Must pass background checks... That's requirements/qualifications. - What We Offer: includes Competitive Pay details, reimbursements, sick leave, ongoing support, tools provided, chance to join team. That's Benefits and Pay. - A Day in the Life: description. - About Sticky Fingers Cooking®: company description. We need to decide sections: About the role (intro + why you'll love). Responsibilities (What You'll Do). Requirements (Who You Are). Qualifications maybe overlapping; but we can combine Requirements and Qualifications? The instruction says use headings for those categories if content exists. We could have Requirements and Qualifications separate if distinct. But we can also combine if not enough distinct. However we have both "Who You Are" (experience, availability, etc.) and maybe "Qualifications" could be certifications etc. But we can treat "Who You Are" as Requirements, and maybe "Qualifications" as certifications (ServSafe). But we have also "What We Offer" includes Pay, Benefits, etc. We need to include Pay and Schedule sections only if posting actually states them. Pay: they state Competitive Pay ($50 per a one-hour class + food reimbursement + grocery shopping time per class + cell phone/internet reimbursement each month). Also they give hourly rates: $20/hour grocery shopping time, $17.75/hour for trainings, $5 cellphone/internet reimbursement monthly, $14 reimbursement per class for groceries, sick leave accrual. So we have pay details. So we can include a Pay section. Schedule: they mention classes typically held on weekdays between 1PM-4 PM, Available to teach 1 hour classes (on campus approx 90 mins) at least 2 days a week between 1-4 PM, Mondays-Fridays. Must arrive 15-20 minutes prior. So schedule info exists. So we can include Schedule section. Benefits: they list supportive team, tools provided, ongoing support, chance to join team, sick leave, reimbursements (some are pay). But we can have Benefits section for non-pay perks: supportive team, tools provided, ongoing support, chance to join team, maybe also sick leave? But sick leave is more of a benefit. We'll include Benefits. We need to avoid boilerplate like EEO etc. Remove that. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics: numbers, times, etc. We need to format using

for headings,

• for lists,

  for prose. We must not repeat job title as heading. No Job ID. We must output only HTML fragment. Let's craft sections:

  About the role

  Are you ready to TURNIP the BEET on what Kids Eat®? SFC San Diego LLC dba Sticky Fingers Cooking® is looking for enthusiastic part-time Chef Teacher to help us Cultivate COOLinary Curiosity in Kids®! If you're passionate about cooking, have experience teaching or coaching kids, and are looking for a fun, flexible, and meaningful part-time job, we want to meet you!

  Why You'll Love This Job:

  • Make an Impact: Teach kids about cooking, nutrition, and healthy eating habits that will last a lifetime.
  • Flexibility: Perfect for your schedule—classes are typically held on weekdays between 1 PM‑4 PM.
  • Supportive Team: We provide all the tools, training, and recipes you need to succeed.
  • Fun Atmosphere: Enjoy creating a hands‑on, dynamic learning experience for kids aged 5‑12.
  • This is a temporary position with the potential for year‑round part‑time employment based on performance and business needs.
  But note: we already used

  for "Why You'll Love This Job:" maybe better as heading? But we only allowed those specific headings. Could embed as

  with bold? But we can't add other headings. We'll keep as

  then list. Now Responsibilities:

  Responsibilities

  • Lead Hands‑On Cooking Classes: Teach kids how to chop, mix, measure, and create healthy, exciting recipes from around the world.
  • Spark Creativity: Introduce kids to new ingredients, cuisines, and cultures in an engaging, interactive way.
  • Stay Organized: Prepare for classes using provided curricula, shop for fresh ingredients, and set up fun, safe kitchen environments.
  • Communicate via text and phone calls with the Admin Team to ensure students are accounted for, etc.
  • Be the Face of Fun: Inspire and encourage kids as they gain confidence in the kitchen.
  Requirements:

  Requirements

  • Experienced teaching or coaching kids of various ages and backgrounds.
  • Available to teach 1‑hour classes (on campus approx 90 mins) at least 2 days a week between 1‑4 PM, Mondays‑Fridays.
  • Punctual, reliable, and comfortable managing groups of 8‑12 kids.
  • Must arrive on campus 15‑20 minutes prior to scheduled class time.
  • Able to commit to teaching sessions that run 8‑12 weeks.
  • Have or willing to obtain a ServSafe Food Handler Certification.
  • Lift up to 30 lbs to store and transport materials.
  • Must have a reliable means of transportation.
  • Must pass state and FBI background checks as a condition of employment.
  Qualifications: maybe we could separate certifications? But we already included ServSafe in Requirements. Could add a Qualifications heading for any additional qualifications like "Must have reliable transportation" etc. But that's overlapping. To avoid thin sections, maybe we skip Qualifications and keep Requirements only. However instruction says we can include sections only when posting has real specific content. We have content for Qualifications maybe like "Have or willing to obtain a ServSafe Food Handler Certification." That's a qualification. But we already put it under Requirements. Could we split? Might be okay to have both Requirements and Qualifications but risk thin. Better to combine into one section called Requirements (or Qualifications). Since they listed both headings, we need to pick one. I'd choose Requirements as it covers experience, availability, etc. We'll omit Qualifications. Skills: maybe not explicitly listed; we could infer but not explicit. Better to omit. Benefits:

  Benefits

  • Supportive Team: We provide all the tools, training, and recipes you need to succeed.
  • Fun Atmosphere: Hands‑on, dynamic learning experience for kids aged 5‑12.
  • Ongoing Support.
  • All tools and equipment provided, including our special Chef tool kit valued at $175.
  • Chance to join a team that's passionate about making a difference.
  • Sick leave at the rate of 1 hour per 30 worked.
  But note some of these overlap with earlier sections (Supportive Team, Fun Atmosphere). Might be duplication. However we need to preserve all substantive information; duplication is okay if it's in posting. But we should avoid repeating same sentences? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication. However we should try to avoid redundant sections. But we already used Supportive Team and Fun Atmosphere in Why You'll Love This Job. Could we keep them only there and not repeat in Benefits? But Benefits section should contain unique benefits like tools provided, sick leave, ongoing support, chance to join team, maybe also reimbursements (but those are pay). To avoid duplication, we can adjust Benefits to list items not already covered: Ongoing Support, All tools and equipment provided (Chef tool kit $175), Chance to join a team passionate about making a difference, Sick leave accrual. We'll keep those. Pay:

  Pay

  • Competitive Pay: $50 per one‑hour class + food reimbursement + grocery shopping time per class + cell phone/internet reimbursement each month.
  • Each class is roughly 1.4 hours on campus (includes 15 minutes preparation prior and 5‑15 minutes clean up after).
  • $20.00/hour for grocery shopping time.
  • $17.75/hour for trainings and staff meetings.
  • $5 cellphone/internet reimbursement (monthly).
  • $14 reimbursement per class for groceries purchased.
  • Sick leave accrual: 1 hour per 30 worked (also listed under Benefits but we can keep here as part of compensation).
  But sick leave already in Benefits; we could keep only in Benefits. Let's keep sick leave in Benefits only, not duplicate. So Pay section excludes sick leave. Schedule:

  Schedule

  • Classes typically held on weekdays between 1 PM‑4 PM.
  • Available to teach 1‑hour classes (on campus approx 90 mins) at least 2 days a week between 1‑4 PM, Mondays‑Fridays.
  • Must arrive on campus 15‑20 minutes prior to scheduled class time.
  We might also include "A Day in the Life" description as prose under maybe About the role or separate? Could be a separate section but not in allowed headings. Could incorporate into About the role as extra paragraph. But we already have About the role with intro and why you'll love. We could add another

  for "A Day in the Life". That's permissible as prose. Similarly "About Sticky Fingers Cooking®" could be another

  under About the role or separate? Not a heading. We'll add as prose. Thus final HTML:

  About the role

  Are