Overnight Valet Attendant - AC Portsmouth

We need to output HTML fragment with sections: About the role? The posting includes "About Towne Towne is an exceptional arrival..." That's company description. Could be "About the role"? Actually "About Towne" is company overview. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings if they exist. The posting includes: Job Details (Two available openings for OVERNIGHT shifts $20/hr + tips). Then Compensation, Work Schedule, Benefits. Then Summary (role description). Then Essential Functions (list of duties). Then Qualifications (Education, Licensure, Work Experience, Knowledge, Skills). Then SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel. We need to include sections only when posting has real specific content. Avoid filler like "commensurate with experience". The Compensation section: they say "The hourly base pay range for this position is $20 per hour plus tips." That's specific. So we can include Pay section with that. Work Schedule: "The work schedule for this position is overnight shifts." That's specific. Benefits: they list specific benefits. So include Benefits. About the role: we have Summary describing responsibilities. Could be "About the role" or "Responsibilities". The Summary is about Guest Service Associate responsibilities. Could map to "About the role". Also we have Essential Functions with detailed duties (list). That could be "Responsibilities". We'll need to decide. We must not repeat job title as heading. No Job ID. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes "Click here for important notices..." and privacy policy links. Those are boilerplate; remove them. Also "For more information, visit www.towne.com and follow us on LinkedIn." That's maybe okay but could be considered boilerplate? It's company info; maybe keep as part of About the company? But instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The LinkedIn link is not necessarily boilerplate but could be considered navigation? Might be okay to keep as part of About the company? However they said "About Towne Towne is an exceptional arrival..." That's company overview. Could be placed under a heading like "About the company"? Not in allowed headings list. But we could put it under "About the role"? Might be odd. Perhaps we can omit company overview as it's not directly about the role? But they said preserve ALL substantive information. The company overview is substantive. But we don't have a heading for it; we could include it as a

  before first heading? The instruction: Output ONLY the HTML fragment — no /. It didn't say we must start with a heading. So we can have a

  with company overview, then headings. We must not include duplicated lines. Ensure we don't repeat. Now structure:

  About Towne Towne is an exceptional arrival through departure experience company....

  Then maybe

  About the role

  with

  Summary...

  Then

  Responsibilities

  with
  • ... from Essential Functions (list each bullet). Need to preserve percentages? The bullet includes % of Time. Should we keep that? It's substantive. We'll include as part of each
  • . Eg:
  • Maintains pleasant, friendly and professional demeanor with all guests, co-workers, and clients. Acknowledges and greets guests within five feet with a professional and friendly demeanor. Uses guest last names during interactions. - 25%
  etc. Then

  Qualifications

  with
  • Education: High school diploma or general education degree (GED)
  etc. Also Licensure, Work Experience, Knowledge, Skills. Could separate into subheadings? Not allowed; only those headings. Could combine all qualifications into one list. But we need to preserve details. Could do separate

  for Knowledge and Skills? Not in allowed list but they gave examples: Skills is allowed. Knowledge not listed but could be considered part of Qualifications. We'll keep under Qualifications. We need to include Pay:

  Pay

  with

  The hourly base pay range for this position is $20 per hour plus tips.

  Schedule:

  Schedule

  with

  The work schedule for this position is overnight shifts.

  Benefits:

  Benefits

  with
  • accident insurance
  etc. Also 401k retirement savings plan. Also note eligibility etc. We'll include eligibility details as part of
  • maybe. We also have SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel. These are not in allowed headings but could be considered part of Qualifications or Responsibilities? Might be better to include as separate sections? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could add other headings if needed, but they said prefer a few substantive sections over many thin ones. However we need to preserve all substantive information. Could we fold those into Qualifications or Responsibilities? For example, WORKING CONDITIONS & PHYSICAL DEMANDS could be part of Qualifications? Not really. Could be its own heading like "Working Conditions". But not in examples; but we could still use

    for it. The instruction didn't forbid other headings, just gave examples. However they said "Prefer a few substantive sections over many thin ones." So maybe we should combine them into existing sections where possible. For instance, we could add a

    Working Conditions

    but that adds another section. Might be okay if it's substantive. But we need to decide. Let's see content: SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel. These are substantive. Could we put them under a heading like "Job Details"? Not in list. Could we put under "Requirements"? Not exactly. Perhaps we can create a heading "Additional Details". But they didn't forbid. However they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are typical but not exclusive. I'd include them as separate headings to preserve info. But to follow "prefer a few substantive sections over many thin ones", maybe we can combine SCOPE Authority To Act and Budget Responsibility into a

    Job Scope

    . And WORKING CONDITIONS & PHYSICAL DEMANDS and Travel into a

    Working Conditions

    . That would be two sections. Let's do:

    Job Scope

    with

    Authority To Act: Job is fairly routine... Budget Responsibility: The employee has control over resources available only.

    Working Conditions

    with
    • Physical Requirements: ...
    • Lifting Requirements: ...
    • Working Environment: ...
    • Travel: Travel of up to 5% may be required.
    We need to preserve all details. Now check for any duplicated lines: The posting includes "Reasonable accommodations may be made to enable individuals with disabilities to perform all functions." appears twice (in Essential Functions header and WORKING CONDITIONS). We should include only once? The instruction: remove duplicated lines. So we should include it only once. Where? Probably under Working Conditions as it's about accommodations. We'll include it there once. Also "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." appears in Essential Functions header and again in WORKING CONDITIONS. We'll keep one. Now ensure we don't include boilerplate: "Click here for important notices that may be applicable to you." and privacy policy link. Remove. Also "For more information, visit www.towne.com and follow us on LinkedIn." Might be considered company info; we could keep as part of About Towne paragraph? It's navigation/link. Might be considered boilerplate. Safer to remove. Now craft HTML. We'll start with

    About Towne Towne is an exceptional arrival through departure experience company. With its best-in-class parking and hospitality solutions and its fully integrated technology platform, we deliver seamless parking and mobility experiences in the places where people live, learn, work, play, rejuvenate, and recover. Towne’s 14,000 team members create smiles by delivering exceptional experiences for the millions of people we proudly serve each year. For nearly 40 years, Towne has been committed to providing the best experience, delivered by the best team, powered by innovative technology, enhancing lives and communities.

    Then

    About the role

    with

    Summary The Guest Service Associate is responsible for providing exceptional hospitality services to guests in an attentive, friendly and efficient manner. The Guest Service Associate is responsible for parking and retrieving guest vehicles in a prompt yet safe manner and assisting guests with luggage, including delivery and pick up of guest luggage (where applicable) during arrival and departure.

    Then

    Responsibilities

    with
    list each bullet. Let's extract bullets: - Maintains pleasant, friendly and professional demeanor with all guests, co-workers, and clients. Acknowledges and greets guests within five feet with a professional and friendly demeanor. Uses guest last names during interactions. - 25% - Uses salutation of the day and welcomes guests to the location. Practices proper Towne Park phone etiquette. Posts up in designated areas when not completing tasks. - 10% - Parks and retrieves vehicles while driving slowly and cautiously. Assists guests with bell services and luggage storage as needed. Opens all vehicle and hotel doors for guests. - 20% - Assists guests with directions, taxis, reservations and other inquiries. Provides guests with information about outlets, meeting rooms and/or amenities of the facility as well as main attractions in the area. Delivers messages, items and/or guest amenities as requested. Shuttles guests to appropriate places that are approved by the location. - 10% - Explains parking rates and retrieval procedures to guests upon arrival. Issues claim checks only after receiving vehicle keys and collects claim checks from all guests prior to issuing keys. Consistently completes and maintains all ticket information including key tag, guest folio, location of vehicle, damage survey and claim check receipt from all vehicles taken into the valet system. Consistently completes location on all key tags after parking vehicle. Calculates and collects revenue for vehicles when needed. - 35% We'll keep percentages. Then

    Qualifications

    with
    list: - Education: High school diploma or general education degree (GED) - Licensure, Certification, Etc.: Must hold a valid driver’s license for the state you are applying to work, or within a commutable distance from the state you are applying to work (as applicable) - Work Experience: One (1) month related experience and/or training; OR equivalent combination of education and experience - Knowledge: Knowledge of principles and processes for providing customer and personal services. - Skills: Ability to read and write standard English language; Ability to read and comprehend simple instructions, short correspondence and memos; Ability to write simple