Restaurant Server Part 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. Key info: - Additional Information: Weekend Availability Preferred, Job Number 26114808, Job Category Food and Beverage & Culinary, Location 3700 Wailea Alanui Dr, Wailea, Hawaii, United States, 96753, Schedule Full Time, Located Remotely? N, Position Type Non-Management, Pay Range: $16.00-$16.00 per hour, Tip Eligible: Y. - POSITION SUMMARY: Serve food courses and alcoholic beverages to guests. Set tables according to type of event and service standards. Answer questions on menu selections. Communicate with the kitchen regarding menu questions, the length of wait, re-cook orders, and product availability. Communicate additional meal requirements, allergies, dietary needs, and special requests to the kitchen. Record transaction in MICROS system at time of order. Check in with guests to ensure satisfaction with each food course and/or beverages. Maintain cleanliness of work areas, china, glass, etc., throughout the day. Complete closing duties, including restocking items, turning off lights, etc. Present physical and accurate check to guest and process payment. Follow all company and safety and security policies and procedures; report accidents, injuries, and unsafe work conditions to manager; and complete safety training and certifications. Ensure uniform and personal appearance are clean and professional, maintain confidentiality of proprietary information, and protect company assets. Welcome and acknowledge all guests according to company standards, anticipate and address guests’ service needs, assist individuals with disabilities, and thank guests with genuine appreciation. Speak with others using clear and professional language. Develop and maintain positive working relationships with others, support team to reach common goals, and listen and respond appropriately to the concerns of other employees. Ensure adherence to quality expectations and standards. Read and visually verify information in a variety of formats (e.g., small print). Stand, sit, or walk for an extended period of time or for an entire work shift. Move, lift, carry, push, pull, and place objects weighing less than or equal to 25 pounds without assistance and objects weighing in excess of 50 pounds with assistance. Grasp, turn, and manipulate objects of varying size and weight, requiring fine motor skills and hand-eye coordination. Move over sloping, uneven, or slippery surfaces as well as up and down stairs and/or service ramps. Reach overhead and below the knees, including bending, twisting, pulling, and stooping. Perform other reasonable job duties as requested by Supervisors. - PREFERRED QUALIFICATIONS: Education: High school diploma or G.E.D. equivalent. Related Work Experience: At least 1 year of related work experience. Supervisory Experience: No supervisory experience. License or Certification: None. - Then there is a lot of boilerplate about equal opportunity etc. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to produce sections: maybe About the role (position summary), Responsibilities (list of duties), Requirements (maybe preferred qualifications?), Qualifications (maybe education/experience?), Skills (maybe not explicit), Benefits (none explicit), Pay (we have pay range), Schedule (full time). Also maybe location? Not required heading. We must not repeat job title as heading. We must not put Job ID as heading. We need to decide which sections to include based on content. We have: - About the role: could be the position summary paragraph. - Responsibilities: list of duties (the bullet-like sentences). Could be turned into

• . - Requirements: maybe the preferred qualifications (education, experience, supervisory, license). Could be under Requirements or Qualifications. The spec says we can use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to use. We have both "Preferred Qualifications" and maybe "Requirements"? The posting doesn't have explicit "Requirements" but we can treat the preferred qualifications as Requirements or Qualifications. Since we have both headings available, we could put education/experience under Qualifications, and maybe skills under Skills? But we don't have explicit skills list; we could infer from responsibilities but better not to invent. So maybe we only include sections where we have concrete content: About the role (position summary), Responsibilities (list of duties), Qualifications (education/experience/license), Pay (pay range), Schedule (full time). Benefits: none explicit (tip eligible Y maybe considered benefit? Tip eligible is not a benefit but could be considered part of compensation. However spec says only create Benefits section if posting actually states them. It does mention tip eligible Y, which is a benefit? Might be considered a benefit. But it's not a typical benefit like health insurance. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state tip eligible Y, which is a benefit? Could be considered a benefit. But we already have Pay section for pay range. Tip eligibility could be included in Pay or maybe Benefits. Safer to include Benefits section with "Tip eligible". However the spec says "Prefer a few substantive sections over many thin ones." So maybe we combine tip eligibility into Pay section? But Pay section is for pay range; we could add note about tip eligibility within Pay section as a paragraph. That's okay. Thus sections: - About the role: position summary paragraph. - Responsibilities: list of duties (the many sentences). Could be bullet list. - Qualifications: education, experience, supervisory, license. - Pay: pay range and tip eligibility. - Schedule: full time. We should not include Skills if no explicit. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep all details from position summary, responsibilities, qualifications, pay, schedule. We need to format as HTML fragment: use

  for headings,

  • for any list of duties/requirements/benefits, and

    for prose. Thus:

    About the role

    Serve food courses and alcoholic beverages to guests. Set tables according to type of event and service standards. Answer questions on menu selections. Communicate with the kitchen regarding menu questions, the length of wait, re-cook orders, and product availability. Communicate additional meal requirements, allergies, dietary needs, and special requests to the kitchen. Record transaction in MICROS system at time of order. Check in with guests to ensure satisfaction with each food course and/or beverages. Maintain cleanliness of work areas, china, glass, etc., throughout the day. Complete closing duties, including restocking items, turning off lights, etc. Present physical and accurate check to guest and process payment. Follow all company and safety and security policies and procedures; report accidents, injuries, and unsafe work conditions to manager; and complete safety training and certifications. Ensure uniform and personal appearance are clean and professional, maintain confidentiality of proprietary information, and protect company assets. Welcome and acknowledge all guests according to company standards, anticipate and address guests’ service needs, assist individuals with disabilities, and thank guests with genuine appreciation. Speak with others using clear and professional language. Develop and maintain positive working relationships with others, support team to reach common goals, and listen and respond appropriately to the concerns of other employees. Ensure adherence to quality expectations and standards. Read and visually verify information in a variety of formats (e.g., small print). Stand, sit, or walk for an extended period of time or for an entire work shift. Move, lift, carry, push, pull, and place objects weighing less than or equal to 25 pounds without assistance and objects weighing in excess of 50 pounds with assistance. Grasp, turn, and manipulate objects of varying size and weight, requiring fine motor skills and hand-eye coordination. Move over sloping, uneven, or slippery surfaces as well as up and down stairs and/or service ramps. Reach overhead and below the knees, including bending, twisting, pulling, and stooping. Perform other reasonable job duties as requested by Supervisors.

    That is the position summary; but many of those sentences are actually responsibilities. However the spec says we should not repeat content. We could split: About the role could be a brief summary (first few sentences) and Responsibilities list the rest. But we need to preserve all substantive information; we can duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid duplication. However we need to follow the heading usage: About the role likely a short paragraph; Responsibilities a list. We could put the position summary as About the role (maybe first two sentences) and then list the rest as responsibilities. But that would be summarizing away detail (omitting some). Better to keep all detail under Responsibilities as a list, and About the role could be a brief generic statement like "Serve food and beverages, set tables, communicate with kitchen, handle payments, maintain cleanliness, ensure guest satisfaction, follow safety policies, etc." But that would be summarizing. The spec says do NOT summarize away detail. So we must not lose any detail. So we need to include all detail somewhere. If we put all detail under Responsibilities as a list, we can still have About the role maybe just a short intro that doesn't omit detail? But any intro would be extra, not removing detail. It's okay to have extra text as long as we don't lose detail. The spec says "do NOT invent or summarize away detail." Adding extra text is not summarizing away detail; it's adding. But we should avoid inventing. So we can add a brief generic statement that is not invented? It would be invented if not in posting. Better to avoid adding anything not in posting. So maybe we omit About the role section entirely if we cannot find a concise summary that is directly from posting without inventing. However the spec says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include About the role only if we have specific content for it. The posting has a "POSITION SUMMARY" which is specific content for About the role. So we can use that as About the role. Then Responsibilities could be other specific content like duties? But the POSITION SUMMARY already includes many duties. However we could treat the POSITION SUMMARY as About the role, and then we could still have Responsibilities as a list of duties extracted from the same text? That would be duplication. But duplication is not prohibited; it's just repeating detail. The spec didn't forbid duplication, only said preserve all substantive information; do not invent or summarize away detail. Duplication preserves detail (doesn't lose). It's okay but maybe not ideal. However we could avoid duplication by splitting the POSITION SUMMARY into two parts: first sentence(s) as About the role, and the rest as Responsibilities list. But that would be summarizing away detail? Not if we keep all detail; we just split. That's fine. Let's extract first sentence: "Serve food courses and alcoholic beverages to guests." That could be About the role. Then the rest as responsibilities. But the spec says "Prefer a few substantive sections over many thin ones." Having many sections may be okay. We'll have About the role (short), Responsibilities (list), Qualifications, Pay, Schedule. We need to ensure we don't lose any detail. If we take only first sentence for About the role, we lose the rest of the detail unless we put them in Responsibilities. So we need to move all other sentences to Responsibilities list. That preserves all detail. Thus: About the role:

    Serve food courses and alcoholic beverages to guests.

    Responsibilities:
    • Set tables according to type of event and service standards.
    • Answer questions on menu selections.
    ... etc. We need to include all remaining sentences from the POSITION SUMMARY after the first sentence. Let's list them