Baker - Prime Social Reserve Naples
Cameron Mitchell Restaurants · Naples, FL · 1 mo ago
ManufacturingFull-time
We need to output HTML fragment with sections only if real content. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
Content: Title: BAKER (but we don't repeat as heading). There's a "What is Your Role?" then summary. Could treat as About the role.
We have "Summary: It is the responsibility of a baker to make raving fans..." That's about role.
Then "At Cameron Mitchell Restaurants, we put our associates first and strive to continually offer great benefits and perks listed below:" then list: Opportunities for career growth, 80% of all positions promoted from within, Dining discounts..., Health benefits..., Inclusive, fun, and creative environment, Flexible scheduling, paid time off, and closed 7 major holidays!, Competitive Pay.
That's benefits and maybe pay.
Then "What We Are Looking For" list: Genuine approach to hospitality, Individuals who exemplify leadership, kindness, and positivity, “Yes, is the Answer!” Mentality, Those that value teamwork, family, and community. Those are maybe Skills or Requirements.
Then "ESSENTIAL FUNCTIONS OF THE POSITION INCLUDE, BUT ARE NOT LIMITED TO:" then list of duties: reports to work on time, uniform, hygiene, preps food, ensures guest experience, displays proper food safety, knows emergency procedures, maintains sanitation, accomplishes duties adhering to safety, reports unsafe condition, newly hired subject to E-Verify. That's responsibilities.
We also have "Cameron Mitchell Restaurants is an Equal Opportunity Employer..." which is boilerplate to remove.
We need sections: About the role (summary), Responsibilities (essential functions), Requirements (maybe what we are looking for?), Benefits (list of benefits), Pay (competitive pay mentioned), Schedule (flexible scheduling mentioned). However we should only include sections if there is real specific content. For Pay: "Competitive Pay" is vague but it's stated. The rule says: 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. "Competitive Pay" is stated, though vague but it's actual statement. Should we include? It says "Competitive Pay" as a benefit line. It's not a specific number but it's stated. I'd include Pay section with that phrase.
Schedule: "Flexible scheduling, paid time off, and closed 7 major holidays!" That's schedule info. So include Schedule.
Benefits: list includes many items: Opportunities for career growth, 80% of all positions promoted from within, Dining discounts at any of our 60+ restaurants, Health benefits for eligible associates, Inclusive, fun, and creative environment, Flexible scheduling, paid time off, and closed 7 major holidays!, Competitive Pay. Some of these overlap with schedule/pay. But we can still list them under Benefits.
We need to avoid duplication. Could separate: Benefits: Opportunities for career growth, 80% promoted from within, Dining discounts, Health benefits, Inclusive fun environment. Schedule: Flexible scheduling, paid time off, closed 7 major holidays. Pay: Competitive Pay.
Now About the role: The summary paragraph.
Responsibilities: essential functions list.
Requirements/Skills: "What We Are Looking For" list. Could be Requirements or Skills. We need to decide which heading to use. The list includes qualities: genuine approach to hospitality, leadership, kindness, positivity, "Yes, is the Answer!" mentality, teamwork, family, community. Those are more like Skills/Attributes. Could put under Skills. Or Requirements. We need to pick one heading; we can't have both if content similar. Let's use Skills for those attributes. Requirements could be left out if not specific. There's no explicit requirements like experience or education. So we omit Requirements.
Thus sections: About the role (
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting.
Content: Title: BAKER (but we don't repeat as heading). There's a "What is Your Role?" then summary. Could treat as About the role.
We have "Summary: It is the responsibility of a baker to make raving fans..." That's about role.
Then "At Cameron Mitchell Restaurants, we put our associates first and strive to continually offer great benefits and perks listed below:" then list: Opportunities for career growth, 80% of all positions promoted from within, Dining discounts..., Health benefits..., Inclusive, fun, and creative environment, Flexible scheduling, paid time off, and closed 7 major holidays!, Competitive Pay.
That's benefits and maybe pay.
Then "What We Are Looking For" list: Genuine approach to hospitality, Individuals who exemplify leadership, kindness, and positivity, “Yes, is the Answer!” Mentality, Those that value teamwork, family, and community. Those are maybe Skills or Requirements.
Then "ESSENTIAL FUNCTIONS OF THE POSITION INCLUDE, BUT ARE NOT LIMITED TO:" then list of duties: reports to work on time, uniform, hygiene, preps food, ensures guest experience, displays proper food safety, knows emergency procedures, maintains sanitation, accomplishes duties adhering to safety, reports unsafe condition, newly hired subject to E-Verify. That's responsibilities.
We also have "Cameron Mitchell Restaurants is an Equal Opportunity Employer..." which is boilerplate to remove.
We need sections: About the role (summary), Responsibilities (essential functions), Requirements (maybe what we are looking for?), Benefits (list of benefits), Pay (competitive pay mentioned), Schedule (flexible scheduling mentioned). However we should only include sections if there is real specific content. For Pay: "Competitive Pay" is vague but it's stated. The rule says: 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. "Competitive Pay" is stated, though vague but it's actual statement. Should we include? It says "Competitive Pay" as a benefit line. It's not a specific number but it's stated. I'd include Pay section with that phrase.
Schedule: "Flexible scheduling, paid time off, and closed 7 major holidays!" That's schedule info. So include Schedule.
Benefits: list includes many items: Opportunities for career growth, 80% of all positions promoted from within, Dining discounts at any of our 60+ restaurants, Health benefits for eligible associates, Inclusive, fun, and creative environment, Flexible scheduling, paid time off, and closed 7 major holidays!, Competitive Pay. Some of these overlap with schedule/pay. But we can still list them under Benefits.
We need to avoid duplication. Could separate: Benefits: Opportunities for career growth, 80% promoted from within, Dining discounts, Health benefits, Inclusive fun environment. Schedule: Flexible scheduling, paid time off, closed 7 major holidays. Pay: Competitive Pay.
Now About the role: The summary paragraph.
Responsibilities: essential functions list.
Requirements/Skills: "What We Are Looking For" list. Could be Requirements or Skills. We need to decide which heading to use. The list includes qualities: genuine approach to hospitality, leadership, kindness, positivity, "Yes, is the Answer!" mentality, teamwork, family, community. Those are more like Skills/Attributes. Could put under Skills. Or Requirements. We need to pick one heading; we can't have both if content similar. Let's use Skills for those attributes. Requirements could be left out if not specific. There's no explicit requirements like experience or education. So we omit Requirements.
Thus sections: About the role (About the role
), Responsibilities (Responsibilities
), Skills (Skills
), Benefits (Benefits
), Pay (Pay
), Schedule (Schedule
).
Now format: Use
for prose. For lists use
- .
We need to preserve all substantive information. Let's extract exact phrasing.
About the role: The posting: "What is Your Role? To make “Raving Fans” of our Associates, Guests, Purveyors, Partners, and the Communities in which we do business. Summary: It is the responsibility of a baker to make raving fans of the five major groups of people we do business with by preparing all items in the pantry (fillings, tarts, cakes, pies, breads, etc.) while maintaining a sanitary workstation. The baker is responsible for following restaurant policies and procedures while contributing to the profits and revenues of the restaurant."
We can combine into a paragraph. Should we keep the quotes? Keep as is.
Responsibilities: list items from ESSENTIAL FUNCTIONS. Let's capture each bullet:
- Reports to work on time as indicated on the work schedule.
- Uniform meets restaurant requirements and is maintained and cleaned.
- Practices positive personal hygiene and cleanliness habits during all work shifts.
- Preps all food to ensure that all items are prepared according to company specifications, recipes, procedures, plate presentation, and quality standards.
- Ensures our guests have a superior dining experience by correctly prepping food products.
- Displays proper food safety techniques in handling and preparation. This includes proper personal hygiene, hand washing, gloves, knife skills, etc.
- Knows emergency procedures for the restaurant.
- Maintains the highest degree of sanitation, cleanliness, and food safety for the work area to include prep tables, countertops, refrigeration units, floors, walls, and shelving.
- Accomplishes all job duties while adhering to all safety guidelines and practices throughout the shift.
- Immediately reports any unsafe condition or unsafe act, accident, or injury.
- All newly hired associates will be subject to E-Verify Employment Eligibility Verification.
We should keep as list items.
Skills: list from "What We Are Looking For":
- Genuine approach to hospitality
- Individuals who exemplify leadership, kindness, and positivity
- “Yes, is the Answer!” Mentality
- Those that value teamwork, family, and community
We could rephrase but preserve meaning. Keep as is.
Benefits: list from "At Cameron Mitchell Restaurants, we put our associates first and strive to continually offer great benefits and perks listed below:" then items:
- Opportunities for career growth
- 80% of all positions promoted from within
- Dining discounts at any of our 60+ restaurants
- Health benefits for eligible associates
- Inclusive, fun, and creative environment
- Flexible scheduling, paid time off, and closed 7 major holidays!
- Competitive Pay
But we separated flexible scheduling etc into Schedule and Pay. However the benefits list includes them; we could still include them under Benefits but then duplicate. Better to split: Benefits list excludes flexible scheduling and competitive pay (maybe keep them under Benefits as well? but rule says prefer few substantive sections over many thin ones. Could keep Benefits as the list including those, and not have separate Pay/Schedule sections. But we need to include Pay and Schedule only if posting actually states them. It does state them, but we could incorporate them into Benefits. However the instruction: "Prefer a few substantive sections over many thin ones." So maybe better to have Benefits section that includes all those items, and not have separate Pay and Schedule sections. But the rule also says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid having them combined. It says use headings for those categories if we want. But we can choose to not create separate Pay/Schedule if we think it's thin. However the posting explicitly mentions "Flexible scheduling, paid time off, and closed 7 major holidays!" and "Competitive Pay". Those are specific enough to warrant sections? They are brief but still stated. The instruction says prefer a few substantive sections over many thin ones. So maybe we should combine them into Benefits to avoid many thin sections. However the user gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They expect us to possibly use those headings if content exists. But they also say prefer a few substantive sections over many thin ones. So we need to decide.
If we make Benefits, Pay, Schedule each as separate sections, we have three thin sections (each with maybe 1-2 items). That's many thin sections. Better to combine Pay and Schedule into Benefits, making Benefits more substantive. Then we have About the role, Responsibilities, Skills, Benefits. That's four sections, more substantive.
Thus we will not create separate Pay or Schedule headings. We'll include flexible scheduling and competitive pay within Benefits list.
Thus Benefits list will include:
- Opportunities for career growth
- 80% of all positions promoted from within
- Dining discounts at any of our 60+ restaurants
- Health benefits for eligible associates
- Inclusive, fun, and creative environment
- Flexible scheduling, paid time off, and closed 7 major holidays!
- Competitive Pay
Now we need to ensure we don't repeat any content. Also we need to remove boilerplate: EEO, E-Verify? Actually E-Verify is a substantive requirement (All newly hired associates will be subject to E-Verify Employment Eligibility Verification.) That's part of responsibilities (maybe a requirement). We'll keep it under responsibilities.
Now produce HTML.
Structure:
About the role
What is Your Role? To make “Raving Fans” of our Associates, Guests, Purveyors, Partners, and the Communities in which we do business. Summary: It is the responsibility of a baker to make raving fans of the five major groups of people we do business with by preparing all items in the pantry (fillings, tarts, cakes, pies, breads, etc.) while maintaining a sanitary workstation. The baker is responsible for following restaurant policies and procedures while contributing to the profits and revenues of the restaurant.
Responsibilities
- Reports to work on time as indicated on the work schedule.
- Uniform meets restaurant requirements and is maintained and cleaned.
- Practices positive personal hygiene and cleanliness habits during all work shifts.
- Preps all food to ensure that all items are prepared according to company specifications, recipes, procedures, plate presentation, and quality standards.
- Ensures our guests have a superior dining experience by correctly prepping food products.
- Displays proper food safety techniques in handling and preparation. This includes proper personal hygiene, hand washing, gloves, knife skills, etc.
- Knows emergency procedures for the restaurant.
- Maintains the highest degree of sanitation, cleanliness, and food safety for the work area to include prep tables, countertops, refrigeration units, floors, walls, and shelving.
- Accomplishes all job duties while adhering to all safety guidelines and practices throughout the shift.
- Immediately reports any unsafe condition or unsafe act, accident, or injury.
- All newly hired associates will be subject to E-Verify Employment Eligibility Verification.
Skills
- Genuine approach to hospitality
- Individuals who exemplify leadership, kindness, and positivity
- “Yes, is the Answer!” Mentality
- Those that value teamwork, family, and community
Benefits
- Opportunities for