Teammate, Las Vegas | Luke's Lobster

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each section heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Title: Luke’s Lobster is a Maine-inspired, fast-casual lobster shack known for its award-winning seafood rolls. Our seafood is traceable to its source, sustainably caught and processed by our own team to our own high standards. Role - Teammate - Las Vegas, NV - Compensation & Benefits: Starting Wage: $13/hr + TIPS**On average, Luke’s Teammates earn an additional $11/hr when you factor in tips!**Option to join company-sponsored 401k plan after a 1-year waiting periodPre-Tax Commuter Benefits (based on location)Health Insurance Program, including Medical, Dental and Vision (if eligible)Opportunities for advancement in a growing companyEmployee Discounts50% off in shack (excludes alcohol) & 25% off Luke’s Online MarketCasual Work Environment, Flexible Scheduling, & Great Work/Life Balance - Then a paragraph about caring about ethical, environmentally-focused company, supportive environment, etc. - Duties & Responsibilities: bullet list (actually dash lines) of duties: Preparing and serving a simple, seafood-centric menu (there’s no cooking but some minor food prep); Engaging in friendly guest interaction; Taking orders and recommending products at the register; Performing opening and closing duties, including cleaning and setting up for shifts; Utilizing your exceptional attention to detail, safety, cleanliness and organization; Communicating Luke's mission of serving sustainable, traceable seafood (We’re a certified B-Corp!); What does that mean? Check it out here: https://www.bcorporation.net/community/lukes-lobster - Qualifications: Minimum one year restaurant, customer service or retail experience; Understanding of food safety standards, DOH regulations; Ability to handle shellfish / tolerate exposure to shellfish allergen - The Luke's Lobster Story: paragraph about history. - Equal Opportunity Statement: boilerplate to remove. - Essential job functions: list of physical requirements: standing for sustained periods, lifting objects, ascending/descending stairs, bending, crouching, reaching. - Luke's Lobster is a participant of E-Verify. We need to decide which sections to include. We have: - About the role: Could be the introductory paragraph describing the company and role. That is substantive. - Responsibilities: Duties & Responsibilities list. - Requirements/Qualifications: Qualifications list. - Skills: Not explicitly listed; maybe we could infer from duties but better not to create unless explicit. So we may omit Skills. - Benefits: The compensation & benefits paragraph includes many benefits: starting wage, tips, 401k, commuter benefits, health insurance, advancement opportunities, employee discounts, casual work environment, flexible scheduling, work/life balance. This is substantive. So we can have Benefits section. - Pay: Could be separate from Benefits? The posting includes Starting Wage: $13/hr + TIPS and note about average tips $11/hr. That's pay info. Could be separate Pay section. But we could combine Pay and Benefits into one Benefits section? The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into a single Benefits section (or maybe separate Pay and Benefits if both have content). Since we have both pay and benefits details, we could have a Pay section (starting wage, tips) and a Benefits section (401k, commuter, health insurance, discounts, etc). But that might be thin? However each has multiple items. Could be okay. - Schedule: The posting mentions Flexible Scheduling as part of benefits. Could be a Schedule section. But we could incorporate that into Benefits. Since we want few sections, maybe combine Schedule into Benefits. Thus we could have sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits (including pay, benefits, schedule). That's four sections. We need to use headings: About the role, Responsibilities, Requirements, Benefits. Use

  . We must not repeat job title as heading. The role is Teammate - Las Vegas, NV but we won't use that as heading. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate. We need to format lists with

  • . For prose, use

    . We need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. We need to include the link to B Corp. We need to include the story paragraph? It's substantive but maybe could be part of About the role? The About the role section could include company description and role. The story is more background; could be included in About the role as additional prose. We'll include it. We need to include essential job functions (physical requirements). That could be part of Requirements or maybe a separate section? Could be part of Requirements (physical demands). We'll include under Requirements as a list. We need to include Equal Opportunity Statement? That's boilerplate to remove. We need to include E-Verify participant? That's maybe minor metadata; could be folded into a short

    or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. So E-Verify could be a short

    maybe under About the role or at end. But we might drop it as minor metadata? It's not job ID but still minor. Safer to include as a short

    somewhere, maybe after Requirements. But we need to preserve ALL substantive information; E-Verify is not substantive? It's a compliance detail. Might be considered minor metadata. The instruction says fold minor metadata into a short

    or drop it. So we can include a short

    about E-Verify. Now let's draft. Section About the role:

    About the role

    then

    containing: Luke’s Lobster is a Maine-inspired, fast-casual lobster shack known for its award-winning seafood rolls. Our seafood is traceable to its source, sustainably caught and processed by our own team to our own high standards. Role - Teammate - Las Vegas, NV (maybe we keep location). Then also the paragraph about caring about ethical, environmentally-focused company, supportive environment, etc. Then the Luke's Lobster Story paragraph. Could be multiple

    elements. We need to avoid repeating job title as heading; we can still mention role in prose. Section Responsibilities:

    Responsibilities

    then
    • each duty. List duties: - Preparing and serving a simple, seafood-centric menu (there’s no cooking but some minor food prep) - Engaging in friendly guest interaction - Taking orders and recommending products at the register - Performing opening and closing duties, including cleaning and setting up for shifts - Utilizing your exceptional attention to detail, safety, cleanliness and organization - Communicating Luke's mission of serving sustainable, traceable seafood (We’re a certified B-Corp!) - What does that mean? Check it out here: https://www.bcorporation.net/community/lukes-lobster Note: The last item includes a link; we can keep as
    • with anchor. Section Requirements:

      Requirements

      then
      • each qualification and also essential job functions. Qualifications: - Minimum one year restaurant, customer service or retail experience - Understanding of food safety standards, DOH regulations - Ability to handle shellfish / tolerate exposure to shellfish allergen Essential job functions (physical demands): - Standing for sustained periods of time - Lifting objects from lower to higher positions - Ascending or descending stairs - Bending, crouching, and reaching to low and high places We could combine them in one list or separate? Probably one list is fine. Section Benefits:

        Benefits

        then
        • each benefit. Benefits list: - Starting Wage: $13/hr + TIPS (On average, Luke’s Teammates earn an additional $11/hr when you factor in tips!) - Option to join company-sponsored 401k plan after a 1-year waiting period - Pre-Tax Commuter Benefits (based on location) - Health Insurance Program, including Medical, Dental and Vision (if eligible) - Opportunities for advancement in a growing company - Employee Discounts: 50% off in shack (excludes alcohol) & 25% off Luke’s Online Market - Casual Work Environment - Flexible Scheduling - Great Work/Life Balance We could also include the note about "Casual Work Environment, Flexible Scheduling, & Great Work/Life Balance" as separate items. We might also include the statement about caring about ethical, environmentally-focused company? That's more about culture; maybe we already included in About the role. Now we need to ensure we don't include any filler like "commensurate with experience", "not specified", etc. We don't have those. We need to output only HTML fragment, no /, no markdown fences. Let's craft. We need to be careful to escape any HTML special characters? The text includes apostrophes, ampersands, etc. We can keep as is; they are safe inside text nodes. However we have an ampersand in "TIPS**"? Actually there is "**" markdown for bold; we need to remove markdown formatting. The posting includes "**On average, Luke’s Teammates earn an additional $11/hr when you factor in tips!**" with double asterisks indicating bold. We need to output plain text without markdown. So we should remove the asterisks and just keep the sentence. Similarly there may be other markdown like "**". We'll strip them. Also there is "Pre-Tax Commuter Benefits (based on location)" fine. We need to ensure we don't include any stray asterisks. Now produce final HTML. Let's write:

          About the role

          Luke’s Lobster is a Maine-inspired, fast-casual lobster shack known for its award-winning seafood rolls. Our seafood is traceable to its source, sustainably caught and processed by our own team to our own high standards. Role: Teammate – Las Vegas, NV.

          Do you care about working for an ethical, environmentally-focused company? Do you thrive working in a supportive and collaborative environment that values and solicits open and honest communication? Then you will love working at Luke’s Lobster! We believe all boats rise when you put people, community, and the environment at the heart of all decision‑making.

          Luke’s Lobster was born out of the dream of Maine native and third‑generation lobsterman, Luke Holden, to bring the quality lobster rolls of his youth to the big city. He and business partner, Ben Conniff, opened their first lobster shack in NYC’s East Village in October 2009. Now, 15 years later, Luke’s Lobster brings traceable, sustainable seafood to guests across the globe. We work directly with fishermen to hand pick the best seafood, bring it straight to our own seafood company in S