Server
for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide what goes in
vs
. For lists of duties/requirements/benefits we use - . For prose paragraphs we use
.
We need to avoid duplication.
Let's structure:
About the role
Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests.
Maybe also include "We are looking for energetic, food loving, and craft beverage appreciating folks who embody Heads Up Hospitality and teamwork." That could be part of About the role or Requirements. Let's put in About the role as prose.
Responsibilities
- Provide an excellent dining experience for guests.
- Learn and convey knowledge of food and beverage menus, ingredients, sourcing, and wood‑fire cooking techniques.
But we need to ensure we don't invent. The posting says: "Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests." That's both training and responsibility. We can split.
Maybe better: Responsibilities: Provide excellent dining experience; maintain knowledge of menu etc.
But we need to be careful not to add beyond what's given. The posting says they are immersed in training program to become knowledgeable... to provide excellent dining experience. So responsibilities could be: Provide excellent dining experience; maintain knowledge of menu etc. That's derived but okay.
Alternatively we could put that as About the role.
Let's think: The posting includes: "We are looking for energetic, food loving, and craft beverage appreciating folks who embody Heads Up Hospitality and teamwork." That's more like qualifications/requirements.
"If you enjoy teamwork, have an eagerness to learn about food and beverage, have the ability to stay positive and upbeat during a busy shift, and have a desire to make people happy, we need you on our team and hope you will apply today!" That's also qualifications/skills.
"Must be 18 to apply." That's a requirement.
"Hourly rates plus tips average $18-$28/hour." That's pay.
Benefits list.
Schedule: "Flexible schedules, No late nights."
Thus we can create sections:
- About the role: maybe a brief summary: "Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests."
- Responsibilities: maybe not needed if we covered in About the role. But we need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. So we could combine some.
We could have:
About the role (description of role and training)
Requirements (age, attributes)
Skills (teamwork, eagerness to learn, positivity, desire to make people happy)
Benefits (list)
Pay (hourly rate)
Schedule (flexible, no late nights)
We could omit Responsibilities and Qualifications if they overlap.
But we need to include sections only when posting has real specific content. We have content for each.
Let's craft:
About the role
Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests.
Requirements
- Must be 18 years of age or older.
- Energetic, food‑loving, and craft beverage appreciating.
- Embodies Heads Up Hospitality and teamwork.
Skills
- Enjoy teamwork.
- Eagerness to learn about food and beverage.
- Ability to stay positive and upbeat during a busy shift.
- Desire to make people happy.
Benefits
- Culture of Respect and Teamwork
- Flexible schedules
- No late nights
- Paid Time Off
- Excellent health, dental, vision insurance for those who qualify
- New Parent Leave
Pay
Hourly rates plus tips average $18‑$28/hour.
Schedule
Flexible schedules with no late nights.
Check for duplication: We have "Flexible schedules" and "No late nights" both in Benefits and Schedule. Might be duplication. The posting says: "We offer some of the best benefits in the industry: Culture of Respect and Teamwork Flexible schedules No late nights Paid Time Off Excellent health, dental, vision insurance for those who qualify. New Parent Leave". So those are benefits. Schedule could be derived from those benefits but we might still include Schedule section as separate. However to avoid duplication, we could omit Schedule section and keep schedule info under Benefits. But the instruction: include a section ONLY when the posting has real, specific content for it. The posting does mention flexible schedules and no late nights as part of benefits. It does not have a separate "Schedule" heading with details. So we could treat schedule as part of Benefits. However we could still create a Schedule section if we consider that the posting gives schedule info (flexible schedules, no late nights). It's specific content. But it's also listed under benefits. The instruction: Prefer a few substantive sections over many thin ones. Having both Benefits and Schedule may be thin. Better to keep schedule under Benefits and not create a separate Schedule section.
Thus we will have sections: About the role, Requirements, Skills, Benefits, Pay.
We need to ensure we don't miss any substantive info: The description of Tazza Kitchen (About Tazza Kitchen) is also substantive. Should we include an "About the company" section? Not in the list of allowed headings, but we could put under About the role? The allowed headings include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". However we could incorporate that info into About the role or maybe a separate section not listed? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add other headings like "About the company". We could incorporate that info into About the role or maybe a
without heading? But we need to preserve all substantive information. The About Tazza Kitchen paragraph is substantive. We could include it as a
under About the role heading (maybe after the role description). That would preserve it.
Thus About the role section will contain two paragraphs: role description and company description.
Let's craft:
About the role
Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests.
Tazza Kitchen is a high energy eatery centered on made from scratch wood‑fired cooking, thoughtfully sourced ingredients, craft beverages, and the heads up hospitality of an incredible team of people. We recognize that people come first and that includes our employees. We are committed to hiring the most diverse and qualified staff possible because we know that having the right people in place will make us all successful. We celebrate diversity and are committed to creating an inclusive, supportive environment that people are proud to be a part of.
That preserves all.
Now Requirements: Must be 18 to apply; energetic, food loving, craft beverage appreciating folks who embody Heads Up Hospitality and teamwork.
We could break into list items.
Skills: teamwork, eagerness to learn about food and beverage, ability to stay positive and upbeat during a busy shift, desire to make people happy.
Benefits list as given.
Pay: Hourly rates plus tips average $18-$28/hour.
We should not include Schedule separate.
Check for any other substantive info: "Part-time and full-time servers". That's about employment type. Could be included in About the role or maybe Requirements? It's substantive. We could add a sentence in About the role: "We are hiring part‑time and full‑time servers to expand our Front of House team." That's
for prose. We need to decide what goes in
vs
- . For lists of duties/requirements/benefits we use
- . For prose paragraphs we use
. We need to avoid duplication. Let's structure:
About the role
Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests.
Maybe also include "We are looking for energetic, food loving, and craft beverage appreciating folks who embody Heads Up Hospitality and teamwork." That could be part of About the role or Requirements. Let's put in About the role as prose.Responsibilities
- Provide an excellent dining experience for guests.
- Learn and convey knowledge of food and beverage menus, ingredients, sourcing, and wood‑fire cooking techniques.
About the role
Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests.
Requirements
- Must be 18 years of age or older.
- Energetic, food‑loving, and craft beverage appreciating.
- Embodies Heads Up Hospitality and teamwork.
Skills
- Enjoy teamwork.
- Eagerness to learn about food and beverage.
- Ability to stay positive and upbeat during a busy shift.
- Desire to make people happy.
Benefits
- Culture of Respect and Teamwork
- Flexible schedules
- No late nights
- Paid Time Off
- Excellent health, dental, vision insurance for those who qualify
- New Parent Leave
Pay
Hourly rates plus tips average $18‑$28/hour.
Schedule
Flexible schedules with no late nights.
Check for duplication: We have "Flexible schedules" and "No late nights" both in Benefits and Schedule. Might be duplication. The posting says: "We offer some of the best benefits in the industry: Culture of Respect and Teamwork Flexible schedules No late nights Paid Time Off Excellent health, dental, vision insurance for those who qualify. New Parent Leave". So those are benefits. Schedule could be derived from those benefits but we might still include Schedule section as separate. However to avoid duplication, we could omit Schedule section and keep schedule info under Benefits. But the instruction: include a section ONLY when the posting has real, specific content for it. The posting does mention flexible schedules and no late nights as part of benefits. It does not have a separate "Schedule" heading with details. So we could treat schedule as part of Benefits. However we could still create a Schedule section if we consider that the posting gives schedule info (flexible schedules, no late nights). It's specific content. But it's also listed under benefits. The instruction: Prefer a few substantive sections over many thin ones. Having both Benefits and Schedule may be thin. Better to keep schedule under Benefits and not create a separate Schedule section. Thus we will have sections: About the role, Requirements, Skills, Benefits, Pay. We need to ensure we don't miss any substantive info: The description of Tazza Kitchen (About Tazza Kitchen) is also substantive. Should we include an "About the company" section? Not in the list of allowed headings, but we could put under About the role? The allowed headings include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". However we could incorporate that info into About the role or maybe a separate section not listed? The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not add other headings like "About the company". We could incorporate that info into About the role or maybe a
without heading? But we need to preserve all substantive information. The About Tazza Kitchen paragraph is substantive. We could include it as a
under About the role heading (maybe after the role description). That would preserve it. Thus About the role section will contain two paragraphs: role description and company description. Let's craft:
About the role
Servers are immersed in a training program to become knowledgeable about our food and beverage menus, ingredients, sourcing, and wood fire cooking techniques to provide an excellent dining experience for our guests.
Tazza Kitchen is a high energy eatery centered on made from scratch wood‑fired cooking, thoughtfully sourced ingredients, craft beverages, and the heads up hospitality of an incredible team of people. We recognize that people come first and that includes our employees. We are committed to hiring the most diverse and qualified staff possible because we know that having the right people in place will make us all successful. We celebrate diversity and are committed to creating an inclusive, supportive environment that people are proud to be a part of.
That preserves all. Now Requirements: Must be 18 to apply; energetic, food loving, craft beverage appreciating folks who embody Heads Up Hospitality and teamwork. We could break into list items. Skills: teamwork, eagerness to learn about food and beverage, ability to stay positive and upbeat during a busy shift, desire to make people happy. Benefits list as given. Pay: Hourly rates plus tips average $18-$28/hour. We should not include Schedule separate. Check for any other substantive info: "Part-time and full-time servers". That's about employment type. Could be included in About the role or maybe Requirements? It's substantive. We could add a sentence in About the role: "We are hiring part‑time and full‑time servers to expand our Front of House team." That's