Restaurant Manager

We need to output HTML fragment with sections: maybe About the role, Responsibilities, Requirements, Benefits, Pay, etc. Must not repeat job title as heading. Must not include Job ID etc. Must include only sections with real specific content. Must not include placeholder like "commensurate with experience". Must not include boilerplate like EEO etc. Must remove cookie/navigation/legal/EEO etc. Must preserve all substantive info. Let's parse the posting: - Compensation Range $60,000 - $65,000 / year - Hiring – Restaurant Manager - Hiring Immediately - Why Flower Child? (section heading maybe "About the role"? Actually "Why Flower Child?" is a heading but we need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can treat "Why Flower Child?" as About the role (or maybe Benefits). It includes Competitive Pay and incentive opportunity, Medical, Dental, Vision Coverage within 30 days, Retirement savings program with company match, 50% dining discount at all Fox Restaurant Concept locations, Additional discounts at The Cheesecake Factory and North Italia, Gym, fitness studio & nutrition discounts offered through Gympass, Tuition reimbursement, Paid time off. Those are benefits. - Who we are: description of Flower Child, part of Fox Restaurant Concepts, menu, mission, etc. That's About the role or maybe About the company. Could be About the role. - What you’ll do: list of duties/responsibilities: Must have 2+ years high-volume restaurant management experience, Demonstrate an understanding of business operations and financials, Manage shifts..., Create memorable dining experiences..., Understand flavors..., Ensure product quality..., Perform calmly..., Manage on-the-fly requests..., Understand POS systems..., Coach, lead and develop restaurant team, Drive continuous improvement. - Also there is "Fox Restaurant Concepts, an entity of the Cheesecake Factory, is an Equal Opportunity & E- Verify Employer. Proof of eligibility to work in the United States is required. To notify of a non-compliant job posting, please send a notice to HRCommunications@foxrc.com" This is boilerplate EEO etc. Must remove. - Also "Hiring Immediately" maybe schedule? Not exactly schedule. Could be "Schedule: Full-time, immediate start"? Not given. We shouldn't create schedule unless posting actually states them. It says "Hiring Immediately" but not schedule details. Probably we should not create a Schedule section because no specific schedule info (like full-time, part-time, shift times). So omit. - Pay: we have compensation range. So we can create a Pay section with that. - Benefits: we have many benefits listed. - Requirements: maybe the "Must have 2+ years high-volume restaurant management experience" is a requirement. Also "Demonstrate an understanding of business operations and financials" maybe skill. But we can put under Requirements or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have: - About the role: could include "Who we are:" description and maybe "Why Flower Child?" but that is benefits. Actually "Why Flower Child?" is more about benefits and incentives. So we could put that under Benefits. - Responsibilities: the list under "What you’ll do:" is responsibilities. - Requirements: maybe "Must have 2+ years high-volume restaurant management experience" is a requirement. Also maybe "Understand POS systems and OpenTable" could be skill. But we can treat as Requirements. - Skills: maybe "Demonstrate an understanding of business operations and financials", "Understand flavors, aromas, and characteristics of food ingredients", "Perform calmly and effectively in a high-volume environment", "Manage on-the-fly requests with ease and poise", "Coach, lead and develop restaurant team", "Drive continuous improvement". Those could be skills. - Benefits: list of benefits. - Pay: compensation range. We should not include sections with placeholder text. All content is specific. We must not repeat job title as heading. So no

Restaurant Manager

. Good. We must not include Job ID etc. We must not include EEO etc. We must output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Flower Child is a part of Fox Restaurant Concepts, an ever evolving and growing line of innovative concepts founded in 1998. Our menu is devoted to veggies, grains, fruits, and healthy proteins, and we’re focused on real food. At Flower Child, we’re committed to happiness and great service. If you’re passionate about convenient, nutritious eating and you love to make people smile, this is the place for you.

Responsibilities

• Must have 2+ years high-volume restaurant management experience
• Demonstrate an understanding of business operations and financials
• Manage shifts which include daily decision making, scheduling, and planning
• Create memorable dining experiences by exceeding guest expectations
• Understand flavors, aromas, and characteristics of food ingredients
• Ensure product quality and restaurant cleanliness
• Perform calmly and effectively in a high-volume environment
• Manage on-the-fly requests with ease and poise
• Understand POS systems and OpenTable (or other digital/online reservation systems)
• Coach, lead and develop restaurant team
• Drive continuous improvement

But note that the first bullet "Must have 2+ years high-volume restaurant management experience" is more a requirement than a responsibility. However it's in the "What you’ll do:" list. The instruction says preserve all substantive information; we can keep it there. But maybe better to split: Requirements section for that bullet, Responsibilities for the rest. Let's see. We have "What you’ll do:" includes that bullet as first item. It could be considered a requirement but it's listed under duties. We could keep it under Responsibilities as it's part of what you'll do. However the instruction says "Use

• for any list of duties/requirements/benefits". So we can put that bullet under either. But to avoid duplication, we need to decide. We could create a Requirements section for the experience requirement, and Responsibilities for the rest. Let's extract: Requirements: - Must have 2+ years high-volume restaurant management experience Responsibilities (remaining): - Demonstrate an understanding of business operations and financials - Manage shifts which include daily decision making, scheduling, and planning - Create memorable dining experiences by exceeding guest expectations - Understand flavors, aromas, and characteristics of food ingredients - Ensure product quality and restaurant cleanliness - Perform calmly and effectively in a high-volume environment - Manage on-the-fly requests with ease and poise - Understand POS systems and OpenTable (or other digital/online reservation systems) - Coach, lead and develop restaurant team - Drive continuous improvement Skills: maybe we could separate some as skills, but we can also put them under Responsibilities. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Responsibilities and Skills into one Responsibilities section. But we also have Benefits and Pay and About the role. Thus we could have sections: About the role, Responsibilities, Benefits, Pay. We need to include Requirements? The posting does have a specific requirement (2+ years experience). If we omit Requirements section, we would lose that specific info unless we put it elsewhere. We could put it under Responsibilities as a bullet, but it's not a responsibility but a requirement. However the instruction says we can use
  • for any list of duties/requirements/benefits. So we can include it under Responsibilities (though it's a requirement). That would preserve the info. But we might want to separate to be semantically correct. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe better to have fewer sections: About the role, Responsibilities (including requirement), Benefits, Pay. Thus we will not create a separate Requirements section. Now Benefits: list all benefits from "Why Flower Child?" section. Let's extract: - Competitive Pay and incentive opportunity (but we already have Pay section; maybe we can mention incentive opportunity under Benefits? But we have Pay section for compensation range; we could still include "incentive opportunity" under Benefits as part of benefits. However we should avoid duplication. The posting says "Competitive Pay and incentive opportunity" under Why Flower Child? plus we have separate Compensation Range. We could treat "Competitive Pay and incentive opportunity" as part of Benefits, but we already have Pay section with range. To avoid duplication, we could keep Pay section for the range, and Benefits for other benefits (medical, dental, vision, retirement, dining discount, additional discounts, Gympass, tuition reimbursement, paid time off). The "Competitive Pay and incentive opportunity" could be omitted as it's redundant with Pay section. But we must preserve ALL substantive information; we cannot omit "incentive opportunity". However we could include it under Benefits as "incentive opportunity". But we already have Pay section; we could mention that the pay is competitive and includes incentive opportunity. But we must not invent or summarize away detail. We could keep the phrase "Competitive Pay and incentive opportunity" as a bullet under Benefits, and also have Pay section with the range. That's not duplication; it's additional info. It's okay. Thus Benefits bullets: - Competitive Pay and incentive opportunity - Medical, Dental, and Vision Coverage within 30 days of employment - Retirement savings program with company match - 50% dining discount at all Fox Restaurant Concept locations - Additional discounts at The Cheesecake Factory and North Italia - Gym, fitness studio & nutrition discounts offered through Gympass - Tuition reimbursement - Paid time off Now Pay section: just the compensation range: $60,000 - $65,000 / year. Now About the role: we have "Who we are:" paragraph. Also maybe we could include the mission statement: "Our menu is devoted to veggies, grains, fruits, and healthy proteins, and we’re focused on real food. At Flower Child, we’re committed to happiness and great service. If you’re passionate about convenient, nutritious eating and you love to make people smile, this is the place for you." That's from Who we are. Thus About the role paragraph: combine the two sentences: "Flower Child is a part of Fox Restaurant Concepts, an ever evolving and growing line of innovative concepts founded in 1998. Our menu is devoted to veggies, grains, fruits, and healthy proteins, and we’re focused on real food. At Flower Child, we’re committed to happiness and great service. If you’re passionate about convenient, nutritious eating and you love to make people smile, this is the place for you." Now Responsibilities: we need to list all bullets from "What you’ll do:" (including the first bullet about experience). Let's list them exactly as in posting: - Must have 2+ years high-volume restaurant management experience - Demonstrate an understanding of business operations and financials - Manage shifts which include daily decision making, scheduling, and planning - Create memorable dining experiences by exceeding guest expectations - Understand flavors, aromas, and characteristics of food ingredients - Ensure product quality and restaurant cleanliness - Perform calmly and effectively in a high-volume environment - Manage on-the-fly requests with ease and poise - Understand POS systems and OpenTable (or other digital/online reservation systems) - Coach, lead and develop restaurant team - Drive continuous improvement We must preserve the exact wording. Ensure we keep parentheses. Now Benefits: list as above. Now Pay: just a paragraph. Now we