Overnight Valet Attendant - Sarasota Modern

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

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About Towne Towne is an exceptional arrival through departure experience company... (company description). Could be "About the role"? Actually it's about the company. Could be "About the role"? The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have sections: - Compensation: "Towne Park is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location. The hourly base pay range for this position is $18 per hour plus tips." - Work Schedule: "The work schedule for this position is Fri-Sun 10:30p-7a." - 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." - Essential Functions: includes Reasonable accommodations may be made... then Descriptive Statement(s) - % of Time bullet list with percentages. - Qualifications: Education: High school diploma or GED Required 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... etc. - Scope Authority To Act etc. - Budget Responsibility - Benefits: "Employees are eligible to enroll in accident insurance, critical illness insurance, hospital indemnity insurance, and telemedicine benefits. Employees are also able to enroll in the company’s 401k retirement savings plan. Eligibility requirements depend on your job classification, length of employment and number of hours worked. Benefits are subject to change and may be subject to a specific plan or program terms. Seasonal and temporary roles are not eligible for benefits outlined above." - WORKING CONDITIONS & PHYSICAL DEMANDS: includes Physical Requirements, Lifting Requirements, Working Environment, Travel. We need to output sections only when there is real specific content. We should avoid filler like "commensurate with experience" but we have actual pay range $18 per hour plus tips, schedule Fri-Sun 10:30p-7a. So we can include Pay and Schedule sections. We also have Benefits section with specific benefits listed. We have Qualifications (education, licensure, work experience). We have Skills (list of abilities). We have Responsibilities (Essential Functions with descriptive statements). We have About the role? Could use "About the role" for summary? Or "About Towne"? The instruction says we can use About the role heading. The summary is about the role. So we can put Summary under About the role? Or we could have a section "About the role" containing the summary paragraph. Or we could have a separate "Responsibilities" section for essential functions. The instruction says prefer a few substantive sections over many thin ones. So we could combine some. We need to use

  for section headings. Use

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

    for prose. We need to preserve all substantive information. Not invent or summarize away detail. So we need to keep the percentages and bullet points. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit duplicated lines besides maybe "Reasonable accommodations may be made to enable individuals with disabilities to perform all functions." appears twice (in Essential Functions and Working Conditions). We should keep only one? The instruction says remove duplicated lines. So we should keep only one occurrence. Probably keep the first occurrence in Essential Functions and drop the second in Working Conditions. Also "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." appears in Working Conditions. We'll drop that duplicate. Also "Click here for important notices that may be applicable to you." and "For more information about our privacy policy, please click here." are boilerplate/legal; remove. Also "For more information, visit www.towne.com and follow us on LinkedIn." maybe keep as part of About Towne? It's company info; could be considered substantive? It's not essential to job but maybe we keep as part of About the role? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That line is substantive about company. Might keep. But we need to avoid duplication. We'll keep the About Towne paragraph as is. Now structure: We could have sections: - About the role (maybe includes Summary and About Towne? Actually About the role should be about the role, not company. But we could have "About Towne" as a separate section? Not in allowed headings list but we could still use

    for any heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. We could still use other headings but better to stick to those. So we can use "About the role" for the summary of the role. The company description could be placed in a

    before sections? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. It doesn't forbid other headings, but we should prefer the given ones. However we could include a brief intro paragraph before sections. Simplify: We'll output:

    About the role

    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 maybe a

    Responsibilities

    with the essential functions descriptive statements as a list. But we need to preserve percentages. The descriptive statements are bullet points with percentages. We'll make each bullet as
  • containing the statement and percentage. We need to keep the statement: "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. We'll create
    • for each. Then

      Qualifications

      with education, licensure, work experience as list? Could be
      • 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
      Then

      Knowledge

      maybe? But we have Knowledge section: "Knowledge of principles and processes for providing customer and personal services." That's a single line. Could be included under Qualifications or Skills? But we have Skills section with many abilities. We could combine Knowledge and Skills under Skills? But instruction says prefer a few substantive sections over many thin ones. So we could merge Knowledge into Skills or Qualifications. However we have a distinct "Knowledge" line; we could put it under Skills as a bullet. Better: Have

      Skills

      with a list that includes the knowledge statement and all ability statements. But we also have "Scope Authority To Act", "Budget Responsibility", "Working Conditions & Physical Demands". Those are also substantive. Could be separate sections: maybe "Working Conditions". But we have many sections; we need to prefer few substantive sections. Could combine Scope Authority, Budget Responsibility, Working Conditions into a section "Additional Details". But not in allowed headings. However we could still use

      for any heading; the examples are not exclusive. But to be safe, we could create sections for those as they are substantive. But we need to avoid filler. They have content. Let's decide to include sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule, Working Conditions. That's 8 sections, maybe okay. But we need to avoid thin sections: each has substantive content. Now we need to remove duplicated lines: "Reasonable accommodations may be made to enable individuals with disabilities to perform all functions." appears in Essential Functions and Working Conditions. We'll keep only one, maybe in Essential Functions (Responsibilities) and drop from Working Conditions. Also "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions." appears in Working Conditions; we'll drop that. Now we need to preserve all other details. Let's extract each piece. About Towne paragraph: "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. For more information, visit www.towne.com and follow us on LinkedIn." We might keep this as a preamble before sections, maybe as a

      without heading. The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. This is not job title; it's company description. Could be placed as a

      before any heading. Now Summary: Already used in About the role? Actually we used summary as About the role. But we also have the About Towne paragraph separate. So we need to decide: maybe we keep About Towne as a

      intro, then About the role heading with