Assistant Manager 39175

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: Who We Are: description of Ayvaz Pizza (Franchisee of Pizza Hut) hiring Restaurant Assistant Manager who will be responsible for assisting with daily operations... etc. This is about the role? Could be "About the role" or "Who We Are". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map sections accordingly. We have: - Who We Are: description of company and role. Could be "About the role" or maybe "Who We Are". But they gave examples; we can use "About the role" as heading for that content. - Who You Are: Personable, Results-oriented self-starter... This could be "Qualifications" or "Skills"? Actually "Who You Are" describes desired traits. Could be "Qualifications" or "Skills". We'll decide. - Here-s What You Will Be Doing As an integral member of the Operations Team, this position is responsible for: (list). Then "And along the way, we will provide to you the training and development needed to achieve your management goals! Internal promotions are based on personal performance and business need, not hire date!" That's maybe part of responsibilities or benefits? It's about training and development. Could be part of "Responsibilities"? Actually it's about what you will be doing and training. Might be part of responsibilities. - Qualifications (includes, But Not Limited To) list: Minimum 1 year Assistant Manager experience..., Flexibility to work..., Valid Driver-s License..., High School diploma..., Demonstrated ability..., Excellent problem solving... - Responsibilities: Under the direction of the General Manager, the Assistant Manager is responsible to support the General Manager in managing the restaurant-s daily operations, including, but not limited to: list of duties. - SOME Perks - Benefits (Based on eligibility requirements:) list: discount program, provider finder/cost estimation tool, wellness program, pregnancy planning tool, Receive your GED credentials at no cost, Tuition Assistance, Receive Daily Pay - On-demand pay..., The Company reserves the right to conduct a background check..., We are an equal opportunity employer. Location: 6704 Montana, El Paso, Texas 79925 We need to remove boilerplate: equal opportunity employer, background check maybe keep? It's not boilerplate? It's a statement but could be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove "We are an equal opportunity employer." and maybe background check statement? It's not exactly EEO but could be considered legal. Safer to remove it. Also location maybe keep as metadata? They said fold minor metadata into a short

or drop it. Location is minor metadata; we can include in a short

maybe under a heading? But they said do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location in a

maybe after a heading? But we need headings only for sections with substantive content. Could have a

for location after some heading? But they said output ONLY the HTML fragment. We can include a

for location without a heading? Probably okay. But better to fold into a short

under maybe "About the role" or at end. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Benefits are stated (list). Pay: they mention "Receive Daily Pay - On-demand pay". That's about pay schedule? It's about pay frequency. Could be considered Pay section. Schedule: they mention flexibility to work rotating shifts, including weekends and holidays (Closed on Thanksgiving and Christmas). That's schedule info. So we can have Benefits, Pay, Schedule sections. But we need to avoid filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. Let's extract sections: About the role (or Who We Are): description of company and role: "Ayvaz Pizza (Franchisee of Pizza Hut) is hiring Restaurant Assistant Manager who will be responsible for assisting with the daily operations of the restaurant. The Restaurant Assistant Manager assists with ensuring that each visit by a customer result in a friendly and personalized service with great food that is promptly delivered in a clean and inviting environment. We are looking for a self-motivated, dynamic team player to join our team! The Restaurant Assistant Manager position is responsible for providing exceptional guest service and support, while working closely with the District Manager and other team members to maintain operational standards and procedures." We could also include "Who You Are" as part of Qualifications/Skills. But we have separate Qualifications list. The "Who You Are" traits: Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting. That's more like Skills or Qualifications. We'll incorporate into Skills section maybe. Responsibilities: list from "Under the direction of the General Manager..." bullet list. Qualifications: list from "Qualifications (includes, But Not Limited To)" bullet list. Skills: maybe from "Who You Are" and also some from Qualifications? But we already have Qualifications. Could treat Skills as separate: Personable, Results-oriented self-starter, go-getter, Team contributor and leader who thrives in a fast-paced setting. Also maybe "Excellent problem solving and decision-making skills" already in Qualifications. Might be redundant. Better to combine Qualifications and Skills? But instruction says prefer a few substantive sections over many thin ones. Could merge Qualifications and Skills into one "Qualifications" section that includes both experience requirements and personal traits. That would be okay. But they gave examples of headings: Qualifications, Skills separate. However we can decide to only include Qualifications if it covers both. But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we can combine. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't create empty sections. Now extract content for each. About the role: as above. Responsibilities: list items: - Overseeing restaurant-s daily operations - Maintain day-to-day financial controls - Create and manage staff schedules - Interview, hire, train and orientate team - Oversee coaching, counseling, and developing staff and managing team relations. - Exercise proper food handling, equipment maintenance and facility management - Ensure health and safety inspections and standards are met - Set the tone for the fun, family environment in the restaurant Note: some have hyphens like restaurant-s; we keep as is. Qualifications: list: - Minimum 1 year Assistant Manager experience (high volume food service concepts preferred) - Flexibility to work, rotating shifts, including weekends and holidays (Closed on Thanksgiving and Christmas) - Valid Driver-s License in good standing - access to private transportation - High School diploma or equivalent - possess all documents required by state and federal law - Demonstrated ability to effectively lead and manage your own team in a fast-paced, dynamic environment. - Excellent problem solving and decision-making skills, results oriented and customer service focused Also include "Who You Are" traits: Personable, Results-oriented self-starter, a go-getter. Team contributor and leader who thrives in a fast-paced setting. Could add as bullet points under Qualifications. Benefits: list: - A discount program that has discounts on things like glasses, hearing aids, weight loss programs, step tracking devices, shoes, etc. - A provider finder/cost estimation tool, allowing members to find in-network providers and get a cost estimation before the visit - A wellness program, where earning points for things like achieve step goals, can be redeemed to purchase wellness related items - A pregnancy planning tool, that helps track fertility, baby growth, milestones, etc. - Receive your GED credentials at no cost to you. - Tuition Assistance. We invest in YOU by Empowerment and Building Confidence for your future. - Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule. They can track every shift worked and every penny earned, and they can cash out to use that pay whenever they want. Pay: The Daily Pay description is also a benefit but could be Pay section. However we already have Daily Pay under Benefits. Might be better to separate Pay: "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule. They can track every shift worked and every penny earned, and they can cash out to use that pay whenever they want." That's about pay frequency. So we can have Pay section with that description. Schedule: from Qualifications: "Flexibility to work, rotating shifts, including weekends and holidays (Closed on Thanksgiving and Christmas)". That's schedule info. So Schedule section can contain that sentence. We need to avoid duplication: The flexibility sentence appears in Qualifications list; we might move it to Schedule and remove from Qualifications to avoid duplication. But we must preserve all substantive information; we can keep it in both places? Better to avoid duplication but still preserve info. We could keep it in Schedule and remove from Qualifications list, but then we lose it from Qualifications. However we could keep it in Qualifications as part of list but also have Schedule section referencing it; duplication is okay? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but could be considered redundant. It's okay to keep in both places? Might be okay but better to avoid duplication. Let's keep it in Schedule and remove from Qualifications list. Then Qualifications loses that point; but we still have the info in Schedule. That's fine. Now Benefits list includes Daily Pay; but we moved Daily Pay to Pay section. So we should remove Daily Pay from Benefits to avoid duplication. However the Benefits list includes that as a perk; we could keep it there and also have Pay section; duplication again. Better to keep Daily Pay under Pay and remove from Benefits. But the Benefits list originally includes it; we need to preserve all substantive information; we can keep it in Pay and also mention it's a benefit? Might be okay to keep only in Pay and note that it's a benefit. But to be safe, we could keep it in Benefits and also have Pay section referencing same info (duplicate). The instruction didn't forbid duplication. I'd prefer to keep it in Benefits and also have Pay section? That seems redundant. Let's think: The Benefits section is for perks; Pay is separate. The Daily Pay is a pay-related benefit; could be placed under Pay. I'll move it to Pay and remove from Benefits. Thus Benefits list will be: - discount program... - provider finder/cost estimation tool... - wellness program... - pregnancy planning tool... - Receive your GED credentials at no cost to you. - Tuition Assistance. We invest in YOU by Empowerment and Building Confidence for your future. Pay section: "Receive Daily Pay - On-demand pay allows employees to access their pay on their schedule. They can track every shift worked and every penny earned, and they can cash out to use that pay whenever they want." Schedule section: "Flexibility to work, rotating shifts, including weekends and holidays (Closed on Thanksgiving and Christmas)." Now About the role: we might also include the location as a short

  after About the role or at end. We'll add a

  for location: "Location: 6704 Montana, El Paso, Texas 79925". Could be placed after About the role. Now we need to output HTML fragment with

  headings and

  • for lists,

    for prose. We must not include <