Catering Lead Coordinator
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, EEO, etc. The posting includes:
- Intro: "Love your job and get paid to do it. Our teams are made up of people who love living a healthy lifestyle, serving others and making the world a better place. We cook from scratch all day, every day because when it comes to good food, we don't believe in shortcuts. Join our team and help us change the world. We are Modern Market - a farm fresh eatery that serves awesome food in a fast paced, open kitchen setting. We love food and we love providing an excellent guest experience to each person that walks through our door. Wonder what you get, in addition to a great team to work with? LIVING WAGES - We wouldn't work for minimum wage and don't expect someone with your talents to either. FREE FOOD - We eat our food every day and think you should too. You'll receive a free meal during your full shifts as well as 20% off outside your working hours. BENEFITS - Full time team members are eligible for a full benefits package that's rock solid! Our favorite benefits, however, is still the free food."
- Then "Now Hiring: Front of House / Service Team" (maybe heading but we shouldn't repeat job title as heading; but we can treat as section heading? The instruction: do NOT repeat the job title as a heading (the page already shows it). So we shouldn't use heading for "Front of House / Service Team". We can maybe treat as part of About the role.
- Then description: "Our Service team helps our guest find the right meal, for them, by suggesting menu items and ideas for the best dining experience possible for then. You will also work in partnership with the kitchen to make the dining experience exceptional. You will also support to keep the dining room squeaky clean."
- Then: "We hire PEOPLE and we train them once they are onboard - so, if you have restaurant experience, great! If you don’t, great! If any of the above sounds like you… Join our Team! We are looking for people who: are FRIENDLY! have ENTHUSIASM! show GUEST FOCUS! are ready and EXCITED to LEARN! want to be part of a TEAM!"
- Then EEO line etc to remove.
- Also hashtags etc.
We need to extract sections: About the role (intro + description), Responsibilities (maybe the duties: help guest find right meal, suggest menu items, work with kitchen, keep dining room clean), Requirements/Qualifications/Skills (friendly, enthusiasm, guest focus, ready to learn, team player, restaurant experience optional). Benefits: living wages, free meal during full shifts, 20% off outside work, full benefits package for full-time, free food favorite. Pay: not explicitly given besides "living wages" but not a specific number; we should not create Pay section unless posting actually states them. It says "LIVING WAGES - We wouldn't work for minimum wage and don't expect someone with your talents to either." That's a statement about pay but not a specific number. The instruction: 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. Does "living wages" count as stating them? It's vague but it's a statement about pay. Might be considered stating that they pay living wages, which is a specific claim. However, they didn't give a number. The instruction says avoid filler like "commensurate with experience". "Living wages" is not a placeholder but a claim. I'd include a Pay section with that statement.
Schedule: not mentioned. So no Schedule section.
Benefits: we have details: free meal during full shifts, 20% off outside work, full benefits package for full-time, free food favorite. So we can include Benefits section.
Now we need to format: Use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail.
We need to avoid repeating job title as heading. So we will not have a heading for "Front of House / Service Team". We'll incorporate that into About the role maybe.
We need to remove boilerplate: EEO line, hashtags, etc.
Let's craft sections:
About the role: combine intro description and maybe the "Now Hiring: Front of House / Service Team" line as prose.
Responsibilities: bullet list of duties: help guest find right meal, suggest menu items and ideas for best dining experience, work in partnership with kitchen to make dining experience exceptional, support to keep dining room squeaky clean.
Requirements/Skills: bullet list of desired traits: friendly, enthusiasm, guest focus, ready and excited to learn, want to be part of a team, restaurant experience (optional but we can note that experience is a plus but not required). The posting says: "We hire PEOPLE and we train them once they are onboard - so, if you have restaurant experience, great! If you don’t, great!" So we can note that restaurant experience is a plus but not required. We'll include as bullet: Restaurant experience (preferred but not required). Also "Friendly", "Enthusiasm", "Guest focus", "Ready and excited to learn", "Want to be part of a team". Could combine as list.
Qualifications: maybe same as skills; but we can combine into one section "Requirements" or "Skills". The instruction says we can have sections like Requirements, Qualifications, Skills. We need to avoid thin sections. So maybe just one section "Requirements" that includes both required and preferred.
Benefits: bullet list: Living wages (competitive pay above minimum wage), Free meal during full shifts, 20% discount on meals outside working hours, Full benefits package for full-time team members (health, etc? but we just state "full benefits package that's rock solid"), Free food (favorite benefit). We should not invent details beyond what's given. So we list exactly: Living wages (they wouldn't work for minimum wage), Free meal during full shifts, 20% off outside working hours, Full benefits package for full-time team members, Free food (highlighted as favorite benefit). We'll keep as bullet.
Pay: we could include a Pay section with statement about living wages. But we already have living wages in Benefits. Might be redundant. Better to have Pay section with that statement, and Benefits section for other benefits. However, the instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section that includes living wages as a benefit. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state living wages, so we could have Pay section. But we could also treat living wages as a benefit. To avoid thin sections, maybe combine into Benefits. However, they said "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits might be thin if each only has one bullet. Better to have a single Benefits section that includes living wages as a benefit. But the instruction also says use headings for Benefits, Pay, Schedule separately if they exist. It doesn't forbid combining, but we should follow the headings list if we have content. Since we have content for both pay and benefits, we could have both sections. But we risk thin sections. However, we can make each substantive: Pay section could have a paragraph about living wages; Benefits section could have list of free meal, discount, full benefits, free food. That seems reasonable.
Thus we will have sections: About the role (prose), Responsibilities (ul), Requirements (ul), Benefits (ul), Pay (p). No Schedule.
We must not include empty sections.
Now craft HTML.
We need to ensure we don't include any markdown fences.
Let's write:
About the role
Love your job and get paid to do it. Our teams are made up of people who love living a healthy lifestyle, serving others and making the world a better place. We cook from scratch all day, every day because when it comes to good food, we don't believe in shortcuts. Join our team and help us change the world. We are Modern Market - a farm fresh eatery that serves awesome food in a fast paced, open kitchen setting. We love food and we love providing an excellent guest experience to each person that walks through our door. Now Hiring: Front of House / Service Team. Our Service team helps our guest find the right meal, for them, by suggesting menu items and ideas for the best dining experience possible. You will also work in partnership with the kitchen to make the dining experience exceptional. You will also support to keep the dining room squeaky clean.
But note we already used responsibilities for those duties; we might duplicate. Better to keep About the role as intro only, and responsibilities separate.
Thus About the role: intro paragraph about company, mission, etc. Then responsibilities separate.
Let's craft:
About the role
Love your job and get paid to do it. Our teams are made up of people who love living a healthy lifestyle, serving others and making the world a better place. We cook from scratch all day, every day because when it comes to good food, we don't believe in shortcuts. Join our team and help us change the world. We are Modern Market - a farm fresh eatery that serves awesome food in a fast paced, open kitchen setting. We love food and we love providing an excellent guest experience to each person that walks through our door.
Then responsibilities:
Responsibilities
- Help guests find the right meal by suggesting menu items and ideas for the best dining experience.
- Work in partnership with the kitchen to make the dining experience exceptional.
- Support keeping the dining room squeaky clean.
Requirements/Skills:
Requirements
- Friendly and enthusiastic attitude.
- Strong guest focus.
- Ready and excited to learn.
- Desire to be part of a team.
- Restaurant experience is a plus but not required.
Benefits:
Benefits
- Living wages – competitive pay above minimum wage.
- Free meal during full shifts.
- 20% discount on meals outside working hours.
- Full benefits package for full‑time team members.
- Free food (highlighted as a favorite benefit).
Pay: maybe we already included living wages in Benefits; but we could still have Pay section with statement about living wages. However, we already have living wages in Benefits; duplicating might be redundant. The instruction says preserve ALL substantive information; not to invent or summarize away detail. Duplicating is okay but might be considered redundant but not wrong. However, they prefer few substantive sections over many thin ones. Having Pay section with just living wages might be thin. Better to incorporate living wages into Benefits as we did. So we skip Pay section.
Thus final HTML includes About the role, Responsibilities, Requirements, Benefits.
Check for any other substantive content: "We hire PEOPLE and we train them once they are onboard - so, if you have restaurant experience, great! If you don’t, great! If any of the above sounds like you… Join our Team!" This is covered in requirements (friendly, enthusiasm, etc.) and the note about restaurant experience. The "Join our Team!" is call to action, which we should remove as application instructions? The instruction says remove application instructions. "Join our Team!" is basically a call to
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive information, not invent or summarize away detail. We need to avoid repeating job title as heading. So we will not have a heading for "Front of House / Service Team". We'll incorporate that into About the role maybe. We need to remove boilerplate: EEO line, hashtags, etc. Let's craft sections: About the role: combine intro description and maybe the "Now Hiring: Front of House / Service Team" line as prose. Responsibilities: bullet list of duties: help guest find right meal, suggest menu items and ideas for best dining experience, work in partnership with kitchen to make dining experience exceptional, support to keep dining room squeaky clean. Requirements/Skills: bullet list of desired traits: friendly, enthusiasm, guest focus, ready and excited to learn, want to be part of a team, restaurant experience (optional but we can note that experience is a plus but not required). The posting says: "We hire PEOPLE and we train them once they are onboard - so, if you have restaurant experience, great! If you don’t, great!" So we can note that restaurant experience is a plus but not required. We'll include as bullet: Restaurant experience (preferred but not required). Also "Friendly", "Enthusiasm", "Guest focus", "Ready and excited to learn", "Want to be part of a team". Could combine as list. Qualifications: maybe same as skills; but we can combine into one section "Requirements" or "Skills". The instruction says we can have sections like Requirements, Qualifications, Skills. We need to avoid thin sections. So maybe just one section "Requirements" that includes both required and preferred. Benefits: bullet list: Living wages (competitive pay above minimum wage), Free meal during full shifts, 20% discount on meals outside working hours, Full benefits package for full-time team members (health, etc? but we just state "full benefits package that's rock solid"), Free food (favorite benefit). We should not invent details beyond what's given. So we list exactly: Living wages (they wouldn't work for minimum wage), Free meal during full shifts, 20% off outside working hours, Full benefits package for full-time team members, Free food (highlighted as favorite benefit). We'll keep as bullet. Pay: we could include a Pay section with statement about living wages. But we already have living wages in Benefits. Might be redundant. Better to have Pay section with that statement, and Benefits section for other benefits. However, the instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section that includes living wages as a benefit. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state living wages, so we could have Pay section. But we could also treat living wages as a benefit. To avoid thin sections, maybe combine into Benefits. However, they said "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits might be thin if each only has one bullet. Better to have a single Benefits section that includes living wages as a benefit. But the instruction also says use headings for Benefits, Pay, Schedule separately if they exist. It doesn't forbid combining, but we should follow the headings list if we have content. Since we have content for both pay and benefits, we could have both sections. But we risk thin sections. However, we can make each substantive: Pay section could have a paragraph about living wages; Benefits section could have list of free meal, discount, full benefits, free food. That seems reasonable. Thus we will have sections: About the role (prose), Responsibilities (ul), Requirements (ul), Benefits (ul), Pay (p). No Schedule. We must not include empty sections. Now craft HTML. We need to ensure we don't include any markdown fences. Let's write:
About the role
Love your job and get paid to do it. Our teams are made up of people who love living a healthy lifestyle, serving others and making the world a better place. We cook from scratch all day, every day because when it comes to good food, we don't believe in shortcuts. Join our team and help us change the world. We are Modern Market - a farm fresh eatery that serves awesome food in a fast paced, open kitchen setting. We love food and we love providing an excellent guest experience to each person that walks through our door. Now Hiring: Front of House / Service Team. Our Service team helps our guest find the right meal, for them, by suggesting menu items and ideas for the best dining experience possible. You will also work in partnership with the kitchen to make the dining experience exceptional. You will also support to keep the dining room squeaky clean.
But note we already used responsibilities for those duties; we might duplicate. Better to keep About the role as intro only, and responsibilities separate. Thus About the role: intro paragraph about company, mission, etc. Then responsibilities separate. Let's craft:About the role
Love your job and get paid to do it. Our teams are made up of people who love living a healthy lifestyle, serving others and making the world a better place. We cook from scratch all day, every day because when it comes to good food, we don't believe in shortcuts. Join our team and help us change the world. We are Modern Market - a farm fresh eatery that serves awesome food in a fast paced, open kitchen setting. We love food and we love providing an excellent guest experience to each person that walks through our door.
Then responsibilities:Responsibilities
- Help guests find the right meal by suggesting menu items and ideas for the best dining experience.
- Work in partnership with the kitchen to make the dining experience exceptional.
- Support keeping the dining room squeaky clean.
Requirements
- Friendly and enthusiastic attitude.
- Strong guest focus.
- Ready and excited to learn.
- Desire to be part of a team.
- Restaurant experience is a plus but not required.
Benefits
- Living wages – competitive pay above minimum wage.
- Free meal during full shifts.
- 20% discount on meals outside working hours.
- Full benefits package for full‑time team members.
- Free food (highlighted as a favorite benefit).