Support

We need to produce HTML fragment with sections: About the role? Actually we have "Who We Are" description, then "Overview" etc. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. Let's map. We have "Who We Are" description: could be About the role? Actually it's company description. Could be "About the role" maybe not. But we can put "About the role" heading with that description? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings. It doesn't forbid using About the role for company overview. Probably okay. We have Overview: "At Level99, a Support team member is dedicated to providing outstanding hospitality..." That's basically role overview. Could be part of About the role. We have Responsibilities list: many bullet points. We have Must-have Skills list. We have Other Desirable (but Not Necessary) Skills & Experience. We have "YOU MIGHT BE A FIT ON THE LEVEL99 TEAM IF YOU…" list. We have Pay: "This role will pay an hourly rate plus tips." That's specific enough for Pay section. We have Schedule? Not explicitly given besides flexible schedule based on business needs which will include days, nights, weekends and holidays; able to work eight hour-plus shifts, etc. That's schedule info. So we can include Schedule section. Benefits? Not mentioned besides full-service bar and award-winning restaurant? That's not employee benefits. No explicit benefits like health insurance, etc. So we should not create Benefits section. Qualifications? Not separate; maybe combine with Skills. Could have Requirements section? Could put Must-have Skills as Requirements. Other desirable as Qualifications? But we need to follow headings: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: company description + overview. - Responsibilities: list of duties. - Requirements: Must-have Skills (maybe treat as requirements). - Qualifications: Other Desirable (but Not Necessary) Skills & Experience. - Skills: maybe combine? But we already used Must-have as Requirements; we could put Skills as the "YOU MIGHT BE A FIT..." list? Or we could put Skills as the Must-have Skills and Requirements as something else? Let's think: The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if we have content. We need to decide which content fits each. We have: - About the role: company description and overview of role. - Responsibilities: the bullet list under "Key responsibilities involve..." and the list after. - Requirements: maybe the "Must-have Skills" list (these are required). - Qualifications: the "Other Desirable (but Not Necessary) Skills & Experience" list. - Skills: maybe the "YOU MIGHT BE A FIT..." list (these are more about personal traits). Could be considered Skills. - Pay: hourly rate plus tips. - Schedule: flexible schedule, days/nights/weekends/holidays, eight hour-plus shifts, etc. We should not create Benefits. Now we need to output HTML fragment with

for each section heading, then content:

for prose,

• for lists. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from the text. Let's extract content. Company description (Who We Are): "Level99 is a sprawling playground designed for adults with over 50 life-sized mini-games where Players dodge axes, crack puzzles, and outsmart real-world challenges. Each game lasts about 1-4 minutes and is built for 2-6 people to play together. One ticket to Level99 unlocks access to all of our games including Challenge Rooms, Player-vs-Player duels, and an art scavenger hunt. We save your progress each time you play so you can earn rewards and climb our coveted leaderboard. Alongside the games, Level99 offers a full-service bar and award-winning restaurant - featuring scratch-cooking, local craft beers, handmade cocktails, and a variety of event spaces. Level99 has locations in Natick, MA, Providence, RI, Tysons, VA, Disney Springs, FL, and is opening in West Hartford, CT, Paramus, NJ, King of Prussia, PA, and Raleigh, NC. Level99 is backed by Act III Holdings, led by Panera founder Ron Shaich, and we have a talented team that has worked on successful entertainment projects ranging from 5 Wits to Walt Disney Imagineering. Visit www.level99.com for more details. Level99 Corbin's Corner in West Hartford, CT - Coming Late Fall!" Overview: "At Level99, a Support team member is dedicated to providing outstanding hospitality to all restaurant guests and entertainment players. This includes expediting and delivering food orders to dining room guests, as well as assisting guests picking up orders at the counter window." We can combine these into About the role section prose. Responsibilities list: The bullet points after "Key responsibilities involve monitoring food quality, managing ticket times, and ensuring work areas are well-stocked with supplies." Then list: - Review and understand all guest orders, including in-restaurant dining, takeout and delivery - Distinguish between guest facing counter pickup window and main dining room orders, expediting accordingly - Interacting with guests at the pickup counter to ensure all needs and expectations are met - Run food to guest tables, identifying items as delivering, clearing dishes as needed, and ensuring all guest needs are met - Replenish sauces, ramekins, and specific containers designated to specific service areas - Communicate effectively to both front of house and back of house teams - Receive, check and pack all guest takeout orders - Keep all materials for takeout/delivery and dining organized, including plates, bags, boxes & labels - Keep a close eye on quality, consistency, and ticket times - Build a knowledge of all food menus and established standards, striving for consistency in both flavor and presentation We need to preserve each as
• . Must-have Skills list: - Organized, thorough, and precise - Analytical and systematic thinking - Understanding of ticket times and kitchen metrics - Knowledge of health and sanitation code and policies - High integrity and professionalism - A positive, joyful, upbeat and energetic attitude - leading by example - Passion for hospitality - Ability to work a flexible schedule based on business needs which will include days, nights, weekends and holidays - Able to work eight hour-plus shifts, plus ability to stand, sit, squat or walk for extended periods of time, walk up and down stairs - Able to grasp, reach overhead, push, lift and carry up to 50 pounds - Ability to work well under pressure in a fast paced, ever changing work environment Other Desirable (but Not Necessary) Skills & Experience Include: - Multilingual - Previous BOH or FOH experience YOU MIGHT BE A FIT ON THE LEVEL99 TEAM IF YOU… list: - Like to laugh, would be described as a "low maintenance, low drama" person, have a tendency to have a bit of fun while you work - Have a high tolerance for ambiguity, like to go fast, and are excited to learn on the job - Are just a little bit obsessive about getting the details right the first time - Have a high energy personality, the kind of person who is typically smiling, and likes to "get it done now" Pay: "This role will pay an hourly rate plus tips." Schedule: The flexible schedule info is already in Must-have Skills (Ability to work a flexible schedule based on business needs which will include days, nights, weekends and holidays; Able to work eight hour-plus shifts, plus ability to stand, sit, squat or walk for extended periods of time, walk up and down stairs). But we also have schedule info elsewhere? Not really. We could still make a Schedule section with that info, but we would be duplicating. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put schedule info only in Must-have Skills, we still preserve it. But we also need a Schedule section if we have specific content. The schedule info is present in Must-have Skills; we could move it to Schedule section to avoid duplication? But we must not lose info. We could keep it in Must-have Skills and also have Schedule section referencing same? That would duplicate. Better to move schedule-specific bullets to Schedule section and keep Must-have Skills without those. However the Must-have Skills list includes other items like organized, etc. We could split: Keep Must-have Skills as the other items (organized, analytical, etc.) and put schedule-related items in Schedule section. That would preserve all info without duplication. Let's extract schedule-related bullets: - Ability to work a flexible schedule based on business needs which will include days, nights, weekends and holidays - Able to work eight hour-plus shifts, plus ability to stand, sit, squat or walk for extended periods of time, walk up and down stairs Also maybe "Able to grasp, reach overhead, push, lift and carry up to 50 pounds" is physical requirement, not schedule. Keep in Must-have Skills. Thus Must-have Skills list becomes: - Organized, thorough, and precise - Analytical and systematic thinking - Understanding of ticket times and kitchen metrics - Knowledge of health and sanitation code and policies - High integrity and professionalism - A positive, joyful, upbeat and energetic attitude - leading by example - Passion for hospitality - Ability to work well under pressure in a fast paced, ever changing work environment - Able to grasp, reach overhead, push, lift and carry up to 50 pounds Schedule section: - Ability to work a flexible schedule based on business needs which will include days, nights, weekends and holidays - Able to work eight hour-plus shifts, plus ability to stand, sit, squat or walk for extended periods of time, walk up and down stairs Now we need to ensure we didn't lose any other schedule info like "Ability to work a flexible schedule based on business needs which will include days, nights, weekends and holidays" already captured. Now we need to output HTML. Structure:

  About the role

  ... combined company description and overview ...

  Responsibilities

  • ... each responsibility ...

  Requirements

  • ... Must-have Skills (excluding schedule) ...

  Qualifications

  • ... Other Desirable ...

  Skills

  • ... YOU MIGHT BE A FIT ...

  Pay

  This role will pay an hourly rate plus tips.

  Schedule

  • ... schedule bullets ...
  We must not include Benefits section. Check that we haven't missed any substantive info: The "Overview" sentence about expediting and delivering food orders etc is included in About the role prose. Also the "Who We Are" paragraph includes location list, etc. All included. Check for any other details: "Level99 Corbin's Corner in West Hartford, CT - Coming Late Fall!" included in company description. Now ensure we don't include any boilerplate like "Level99 is an E-Verify employer." That's a minor metadata; we can fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short p after About the role maybe? But we already have About the