Fast Casual Restaurant Manager

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate like EEO, navigation, etc. Also remove duplicated lines. Must preserve all substantive info. Let's parse the posting. Text: "PDQ = People Dedicated to Quality. Our restaurants offer food made from scratch that our guests feel good about eating and our Team Members are proud to serve. We keep things simple and do them the right way, because that’s the only way we know how. Servin' up chicken with no added steroids, no added hormones, and no nonsense. Because we are People Dedicated to Quality, our hospitality and food are Just Made, Better. We promise this to our Guests, our Team Members and the Communities we are part of. NOW HIRING: Fast Casual Restaurant Managers Requirements: At least 1 year of hands on Kitchen experience (preferably in a leadership role)Previous GM experience is helpful but not preferred1+ year of Restaurant Manager experience or 3+ years as a Shift Leader experienceFast Casual experience preferredExperience hiring & training hourly team members A PDQ Manager: Assists the Operating Director in providing direction, training and the skill to ensure that the Guests’ expectations are exceededEnsures Team Members are treated fairly and with respect and that each shift reaches its business goals. Is fully proficient in all aspects of the kitchen. Manages both Front and Heart of the House operations. Operates the business in accordance with strict PDQ standards. Cultivates a diverse culture for our Team Members where they are safe, secure and free from harassment. As a part of the PDQ team we offer: Career Development and Growth OpportunitiesMedical, Dental, VisionVacationCompetitive payComprehensive training program Equal Opportunity Employer PDQ (PDQ) is a well established, fast casual restaurant concept that has growth opportunities for team members in a casual dining restaurnat company. At People Dedicated to Quality you can grow your career with us. In this RM role, you will manage restaurant front of house / service teams along with assistant manager roles and duties working as a member of the restaurant management (AM) team. #7total #pdqchicken1011managerfasttrack #pdqchicken" We need to remove boilerplate: "Equal Opportunity Employer", maybe also the hashtags at end. Also remove duplicated lines? There's some duplication: "PDQ = People Dedicated to Quality." appears at start, later "PDQ (PDQ) is a well established...". Might keep some but need to preserve substantive info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all meaningful content, but we can remove boilerplate like EEO, navigation, legal, scam-warning, duplicated lines. Duplicated lines: maybe the phrase "PDQ = People Dedicated to Quality." appears twice? Actually appears at start and later "At People Dedicated to Quality you can grow your career with us." Not exact duplicate. The phrase "PDQ (PDQ) is a well established..." maybe not duplicate. We'll keep. We need to structure into sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - About the role: maybe the introductory paragraph describing PDQ, mission, etc. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (maybe summarizing the company mission). We'll include the initial paragraph about PDQ, food made from scratch, etc. - Responsibilities: The bullet list after "A PDQ Manager:" includes responsibilities: Assists the Operating Director..., Ensures Team Members..., Is fully proficient..., Manages both Front and Heart..., Operates..., Cultivates... We'll put those as

• . - Requirements: The list after "Requirements:" includes: At least 1 year of hands on Kitchen experience (preferably in a leadership role), Previous GM experience is helpful but not preferred, 1+ year of Restaurant Manager experience or 3+ years as a Shift Leader experience, Fast Casual experience preferred, Experience hiring & training hourly team members. We'll put as list. - Qualifications: Might overlap with requirements; but we could treat requirements as qualifications. However we need separate sections only if there is distinct content. The posting doesn't have separate qualifications beyond requirements. Could combine? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we have both Requirements and Qualifications with same content, that would be duplication. Better to have only Requirements (or Qualifications) whichever fits. The posting uses "Requirements:" heading. So we will use Requirements. - Skills: Not explicitly listed; maybe "Experience hiring & training hourly team members" could be skill, but it's already in requirements. Could create Skills section for things like "hiring & training", "kitchen proficiency", "front/back of house". But those are already in responsibilities. Might be redundant. Better to not create Skills if no distinct skill list. - Benefits: The posting says: "As a part of the PDQ team we offer: Career Development and Growth OpportunitiesMedical, Dental, VisionVacationCompetitive payComprehensive training program". That's a list of benefits. We'll create Benefits section with those items. - Pay: The posting mentions "Competitive pay" within benefits, but not a specific number. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay" as part of benefits. That is a statement about pay, albeit vague. Should we create a Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive pay". So we could include a Pay section with that statement. However they also said "Prefer a few substantive sections over many thin ones." Since we already have Benefits section that includes "Competitive pay", maybe we can keep it within Benefits and not create separate Pay section. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, but we could still include them as part of Benefits. However they said "Prefer a few substantive sections over many thin ones." So better to not create a separate Pay section if the info is already covered in Benefits. But the instruction about sections: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could have Pay section if we have pay info. Since we have "Competitive pay", we could make a Pay section with that line. But then Benefits would lose that item. However we could still keep Benefits with other items and Pay separate. That would be two sections, each with content. That's okay. - Schedule: No mention of schedule. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to ensure we don't include boilerplate like "Equal Opportunity Employer". Also remove hashtags at end. Now we need to output HTML fragment only, no /, no markdown fences. Let's craft:

  About the role

  PDQ = People Dedicated to Quality. Our restaurants offer food made from scratch that our guests feel good about eating and our Team Members are proud to serve. We keep things simple and do them the right way, because that’s the only way we know how. Servin' up chicken with no added steroids, no added hormones, and no nonsense. Because we are People Dedicated to Quality, our hospitality and food are Just Made, Better. We promise this to our Guests, our Team Members and the Communities we are part of.

  Responsibilities

  • Assists the Operating Director in providing direction, training and the skill to ensure that the Guests’ expectations are exceeded
  • Ensures Team Members are treated fairly and with respect and that each shift reaches its business goals
  • Is fully proficient in all aspects of the kitchen
  • Manages both Front and Heart of the House operations
  • Operates the business in accordance with strict PDQ standards
  • Cultivates a diverse culture for our Team Members where they are safe, secure and free from harassment

  Requirements

  • At least 1 year of hands on Kitchen experience (preferably in a leadership role)
  • Previous GM experience is helpful but not preferred
  • 1+ year of Restaurant Manager experience or 3+ years as a Shift Leader experience
  • Fast Casual experience preferred
  • Experience hiring & training hourly team members

  Benefits

  • Career Development and Growth Opportunities
  • Medical, Dental, Vision
  • Vacation
  • Comprehensive training program

  Pay

  Competitive pay

  We need to ensure we didn't miss any substantive info: The line "As a part of the PDQ team we offer: Career Development and Growth OpportunitiesMedical, Dental, VisionVacationCompetitive payComprehensive training program". We split into benefits and pay. We kept "Competitive pay" in Pay section. Good. We also have the line "PDQ (PDQ) is a well established, fast casual restaurant concept that has growth opportunities for team members in a casual dining restaurnat company. At People Dedicated to Quality you can grow your career with us. In this RM role, you will manage restaurant front of house / service teams along with assistant manager roles and duties working as a member of the restaurant management (AM) team." This is substantive; we haven't included it. Should we include it somewhere? It's about the role/growth opportunities. Could be part of About the role or maybe a separate section like "About the role" already covers mission but not this. We could add a paragraph after the initial About the role paragraph that includes this info. Let's incorporate. We need to preserve ALL substantive information. So we must include that paragraph. Thus About the role section could have two paragraphs: first the mission description, second the growth opportunities and role description. Let's craft:

  About the role

  PDQ = People Dedicated to Quality. Our restaurants offer food made from scratch that our guests feel good about eating and our Team Members are proud to serve. We keep things simple and do them the right way, because that’s the only way we know how. Servin' up chicken with no added steroids, no added hormones, and no nonsense. Because we are People Dedicated to Quality, our hospitality and food are Just Made, Better. We promise this to our Guests, our Team Members and the Communities we are part of.

  PDQ is a well established, fast casual restaurant concept that has growth opportunities for team members in a casual dining restaurant company. At People Dedicated to Quality you can grow your career with us. In this RM role, you will manage restaurant front of house / service teams along with assistant manager roles and duties working as a member of the restaurant management (AM) team.

  Note: fix typo "restaurnat" to "restaurant". We should preserve original text? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Changing a typo might be considered altering detail. However it's a clear typo; but we might keep as is? The original: "casual dining restaurnat company". That's a misspelling. Should we keep it? Probably we should keep the exact text to preserve information. Changing it could be considered altering. Safer to