Host/Hostess/Server Assistant

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: description about role (maybe About the role). It includes "Pay Rate Range: $15/hr Based on Experience." So Pay section. Benefits: "Medical benefits 401(k) plan with matching Scratch kitchen & no microwaves - be proud of where you work and the food you serve! Career advancement opportunities - half of our managers started as Team Members To help promote family and quality of life for our teams, Ted's Montana Grill closes our restaurants on Thanksgiving and Christmas Day." Also "Flexible schedules". So Benefits and maybe Schedule? Flexible schedules is schedule info. So we can have Schedule section: "Flexible schedules". Also maybe "Pay" section. Requirements: "Full-service restaurant experience preferred Strong communication skills Gets along great with people!" That's requirements. Also maybe Qualifications? Not separate. Skills: maybe "Strong communication skills". But we can combine. We need to avoid duplication. Let's parse content: - About the role: description of role: "SERVER ASSISTANTS (HOSTS) ... While we’re Premium, Polished and Professional, we’re also Cool (known as 3 PC). We live by “The Big Sky Spirit” ... You will help create an atmosphere of genuine hospitality, ensuring a remarkable only-at-Ted’s experience for our Guests." Also "GENUINE HOSPITALITY IS IN OUR DNA: ... deliver the “Big Sky Moments” to ensure a great Guest experience each and every time." Also sections about HOSPITALITY, The Experience, SUSTAINABILITY. Those could be part of About the role or separate sections? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Likely we have About the role (description), Responsibilities (maybe not explicit), Requirements, Benefits, Pay, Schedule. There's no explicit Responsibilities list, but we could infer duties: "help create an atmosphere of genuine hospitality, ensuring a remarkable only-at-Ted’s experience for our Guests." That's more about role. Could treat as Responsibilities. But we should not invent. If no explicit responsibilities, maybe omit Responsibilities section. However we have "You will help create an atmosphere..." that is a duty. Could be considered Responsibilities. The instruction: only include section when posting has real, specific content for it. So we can include Responsibilities with that sentence. Requirements: "Full-service restaurant experience preferred Strong communication skills Gets along great with people!" That's specific. Qualifications: maybe not separate; could be same as Requirements. But we could omit Qualifications if not distinct. Skills: maybe "Strong communication skills" but already in Requirements. Could omit Skills. Benefits: list: "Medical benefits", "401(k) plan with matching", "Scratch kitchen & no microwaves", "Career advancement opportunities - half of our managers started as Team Members", "To help promote family and quality of life for our teams, Ted's Montana Grill closes our restaurants on Thanksgiving and Christmas Day.", also "Flexible schedules" maybe schedule. Pay: "$15/hr Based on Experience." Schedule: "Flexible schedules". Also maybe mention closing on Thanksgiving and Christmas Day (that's a benefit but also schedule). Could include in Benefits. We need to output HTML fragment with

headings and

• for lists,

  for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep exact phrases. Let's extract exact sentences: From posting: "SERVER ASSISTANTS (HOSTS) Ted's Montana Grill isn't your ordinary restaurant, so we aren't looking for ordinary people. While we’re Premium, Polished and Professional, we’re also Cool (known as 3 PC). We live by “The Big Sky Spirit” which is our cultural compass and is evident in everything that we do." "Pay Rate Range: $15/hr Based on Experience." "GENUINE HOSPITALITY IS IN OUR DNA: At Ted’s Montana Grill, the Server Assistants are vital and valued members of our team and deliver the “Big Sky Moments” to ensure a great Guest experience each and every time. You will help create an atmosphere of genuine hospitality, ensuring a remarkable only-at-Ted’s experience for our Guests." "WHY WORK FOR TED'S? A strong PPA that generates GREAT tips! Flexible schedules Medical benefits 401(k) plan with matching Scratch kitchen & no microwaves - be proud of where you work and the food you serve! Career advancement opportunities - half of our managers started as Team Members To help promote family and quality of life for our teams, Ted's Montana Grill closes our restaurants on Thanksgiving and Christmas Day." "Requirements Full-service restaurant experience preferred Strong communication skills Gets along great with people! We invite you to become part of the team by applying today!" "Ted’s Montana Grill is proud to be an Equal Opportunity and e-Verify employer." (boilerplate to remove) "HOSPITALITY We take great pride in ensuring all guests receive a warm and memorable experience leaving them feeling better than when they came in. From a bowl of half sours to our two-dollar bills, we empower each team member to deliver Big Sky Moments in ways that are natural and effortless to Ted’s and our guests." "The Experience Our restaurants represent classic saloons of the 19th century where cattlemen and land barons found a little relaxation after a hard day’s work." "SUSTAINABILITY We believe in leaving a better world for future generations. You’ll see this in our commitment to local growers, the paper straws, the Boraxo soap in our restrooms and sustainable choices in our kitchen operations. We are steadfast in our commitment to people, product and prosperity. Ted’s Montana Grill develops and encourages people to become leaders and engage the hearts and minds of our teams." We need to remove boilerplate: EEO, e-Verify, application instructions, duplicated lines. We need to keep substantive info: all the above except boilerplate. We need to structure into sections. Let's decide sections: - About the role: could include the introductory description about Ted's Montana Grill, the Big Sky Spirit, genuine hospitality, etc. Also maybe the HOSPITALITY, The Experience, SUSTAINABILITY paragraphs as they describe culture. Could be part of About the role. - Responsibilities: "You will help create an atmosphere of genuine hospitality, ensuring a remarkable only-at-Ted’s experience for our Guests." Also maybe "deliver the “Big Sky Moments” to ensure a great Guest experience each and every time." That's more about role but could be responsibilities. - Requirements: list: Full-service restaurant experience preferred; Strong communication skills; Gets along great with people! - Benefits: list: Medical benefits; 401(k) plan with matching; Scratch kitchen & no microwaves - be proud of where you work and the food you serve!; Career advancement opportunities - half of our managers started as Team Members; To help promote family and quality of life for our teams, Ted's Montana Grill closes our restaurants on Thanksgiving and Christmas Day.; Flexible schedules (maybe schedule). Also "A strong PPA that generates GREAT tips!" that's a benefit (tips). Should include. - Pay: "$15/hr Based on Experience." - Schedule: "Flexible schedules." Also maybe mention closing on Thanksgiving and Christmas Day (but that's a benefit). Could keep schedule separate. We must not create sections with filler like "not specified". We have content for each. Now produce HTML. We need to use

  for each section heading. Use

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

    for prose. Thus:

    About the role

    ... prose ...

    If we have multiple paragraphs, we can wrap each in

    . For Responsibilities: maybe a

    • list. For Requirements:
      • . For Benefits:
        • . For Pay: maybe

          (since single line). For Schedule:

          or

          • if list. Let's extract exact prose for About the role: combine sentences: "Ted's Montana Grill isn't your ordinary restaurant, so we aren't looking for ordinary people. While we’re Premium, Polished and Professional, we’re also Cool (known as 3 PC). We live by “The Big Sky Spirit” which is our cultural compass and is evident in everything that we do." "GENUINE HOSPITALITY IS IN OUR DNA: At Ted’s Montana Grill, the Server Assistants are vital and valued members of our team and deliver the “Big Sky Moments” to ensure a great Guest experience each and every time." "HOSPITALITY We take great pride in ensuring all guests receive a warm and memorable experience leaving them feeling better than when they came in. From a bowl of half sours to our two-dollar bills, we empower each team member to deliver Big Sky Moments in ways that are natural and effortless to Ted’s and our guests." "The Experience Our restaurants represent classic saloons of the 19th century where cattlemen and land barons found a little relaxation after a hard day’s work." "SUSTAINABILITY We believe in leaving a better world for future generations. You’ll see this in our commitment to local growers, the paper straws, the Boraxo soap in our restrooms and sustainable choices in our kitchen operations. We are steadfast in our commitment to people, product and prosperity. Ted’s Montana Grill develops and encourages people to become leaders and engage the hearts and minds of our teams." We need to keep exactly as given, but we can separate into paragraphs. Now Responsibilities: maybe combine two sentences: "You will help create an atmosphere of genuine hospitality, ensuring a remarkable only-at-Ted’s experience for our Guests." and "deliver the “Big Sky Moments” to ensure a great Guest experience each and every time." Actually the latter is from earlier. We'll include both as list items. Requirements list: "Full-service restaurant experience preferred", "Strong communication skills", "Gets along great with people!" Benefits list: "A strong PPA that generates GREAT tips!", "Flexible schedules", "Medical benefits", "401(k) plan with matching", "Scratch kitchen & no microwaves - be proud of where you work and the food you serve!", "Career advancement opportunities - half of our managers started as Team Members", "To help promote family and quality of life for our teams, Ted's Montana Grill closes our restaurants on Thanksgiving and Christmas Day." Pay: "$15/hr Based on Experience." Schedule: maybe "Flexible schedules" already in benefits; but we could still have Schedule section with that. However to avoid duplication, maybe we keep Flexible schedules under Benefits and not Schedule. But instruction: include section only when posting has real specific content for it. If we put Flexible schedules under Benefits, we still have Schedule section maybe empty. Better to not create Schedule section if we already used that info elsewhere. However we could still have Schedule section with "Flexible schedules" and not duplicate in Benefits. But then we would lose that info from Benefits if we remove. We could keep Flexible schedules in Benefits and also have Schedule section referencing same? That would duplicate. Better to keep Flexible schedules under Benefits and omit Schedule section. But we need to see if posting explicitly mentions schedule besides flexible schedules. It does: "Flexible schedules" under WHY WORK FOR TED'S? Also mentions closing on Thanksgiving and Christmas Day (which is a schedule benefit). So we could have Schedule section with "Flexible schedules" and "Closed on Thanksgiving and Christmas Day". But the latter is also a benefit. Could be placed under Benefits as well. To avoid duplication