Senior Service & Sales Representative (SRQ) - Full-Time

We need to output HTML fragment with sections as per rules. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate: EEO, equal opportunity, scam warning, navigation, legal, cookie, etc. Also remove "See more of our amazing benefits... HERE!" maybe keep benefits content but not the link? The instruction: remove duplicated lines, application instructions. The "See more of our amazing benefits, including any eligibility or specific location offerings, HERE!" is likely a link to benefits page; we can keep benefits content but maybe drop that sentence as it's just a reference. Also "Not available in Puerto Rico" is a note about benefits? Could be considered part of benefits but it's a limitation; we can keep as part of benefits paragraph. We need to preserve all substantive information. Let's parse the posting. First paragraph: "The CLEAR Senior Service and Sales Representative (Senior Ambassador) makes magic happen every day by creating frictionless experiences for our members." That's about the role. Could be part of About the role. Then "What You'll Do" bullet list (actually sentences). We'll treat as Responsibilities. List items: - Drive membership enrollments by engaging travelers and educating them about the benefits of CLEAR, as well as supporting other team members in reaching their enrollment goals - Balance high volume with high-quality customer and member experiences - Resolve traveler and/or member concerns or inquiries in an appropriate and timely manner, escalating needs as required/needed. - Consistently adhere to security procedures by validating airline documents, verifying CLEAR member traveler identification and following all security and safety protocols at all times - Support Managers and leadership in the training & development of new and existing team members, serving as a subject matter expert to guide on the job training. - Troubleshoot technical issues with hardware and software within the operating environment, ensuring front line triage occurs prior to elevating to corporate support team. Then "What You're Great At" list: abilities. Could be Skills or Qualifications? Probably Skills. List: - Ability to function autonomously and with integrity keeping the CLEAR’s customers and business partners best interests in mind. - Strong communication skills and the ability to engage with customers, members, and teammates alike. - Ability to follow detailed instructions and execute them with 100% accuracy, in a fast-paced and constantly changing environment. - Demonstrated leadership skills: Role model, exemplary team member who consistently goes above and beyond for other employees and customers. - Self-motivated achiever interested in taking on additional roles and responsibilities, and selling CLEAR! - Ability to comply with all security and safety guidelines, policies and procedures, and follow protocol thoroughly and consistently. Then "Role Requirements": list: - You must be 18 years of age or older - High school diploma or GED equivalent required - Open availability and flexibility is a must – ability to work a variety of shifts - Ability to stand for up to 8 hours per day - Desire to grow into a management and/or leadership position - Successful completion of CLEAR, airport, and government screening as applicable, and CLEAR background checks, including but not limited to a drug test. This may also include federal Personnel Security (PerSec) SF-85 screening, depending on your work assignment Then "How You'll Be Rewarded": list benefits: - Free CLEAR membership for you + family/friends discounts - 401(k) Retirement Plan, including a company match* - 10 company-paid holidays (paid 1.5x if worked) - Full-time team members also receive: - Comprehensive Medical, Dental, and Vision Insurance - Paid Time Off - See more of our amazing benefits, including any eligibility or specific location offerings, HERE! (we may drop) - Not available in Puerto Rico Then "About CLEAR": description paragraph. Then note about SF-85 background check adjudicated by DHS etc. That's more detail about requirements maybe but could be part of Requirements. Then EEO statement etc. Remove. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (first paragraph maybe plus About CLEAR? Actually About CLEAR is company description; could be About the role? Usually About the role is role description; About CLEAR is company overview. Could be placed under About the role or maybe we could create a separate section? Not in list. We could put About CLEAR under About the role as additional context. Or we could treat About CLEAR as part of About the role. We'll include About the role heading and include both the initial role description and the About CLEAR paragraph. Responsibilities: the "What You'll Do" list. Requirements: maybe the "Role Requirements" list (age, education, availability, physical, desire to grow, screenings). Also the SF-85 note could be included under Requirements. Qualifications: maybe we don't have separate qualifications beyond requirements; but we could treat "Role Requirements" as Qualifications. However we need both Requirements and Qualifications sections if we have distinct content. The posting has "Role Requirements" and "What You're Great At" (skills). So we can map: - Requirements: the bullet list under Role Requirements. - Qualifications: maybe we could treat "What You're Great At" as Skills, not Qualifications. But we need to decide. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to decide which sections to include based on content. We have: - About the role: we have role description and About CLEAR. - Responsibilities: What You'll Do. - Requirements: Role Requirements. - Skills: What You're Great At. - Benefits: How You'll Be Rewarded. - Pay: Not explicitly stated; there is no pay info. So we should NOT include Pay section. - Schedule: Not explicitly stated; there is mention of open availability, variety of shifts, but not a specific schedule. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have. Schedule we have only "Open availability and flexibility is a must – ability to work a variety of shifts". That's about schedule but not explicit schedule details. Might be considered schedule info? It's about availability. Could be considered schedule. However the instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state open availability and flexibility, ability to work a variety of shifts. That is schedule-related. So we could include a Schedule section with that content. But we need to avoid filler like "varies". This is specific: ability to work a variety of shifts. So we can include Schedule. Pay: no mention of salary, hourly rate, etc. So we omit Pay. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. We might also include Qualifications if we have distinct content; but we already have Requirements. Could we treat Requirements as Qualifications? But we have both Requirements and Skills; Qualifications may be redundant. Safer to include Requirements and Skills, omit Qualifications. Now we need to format lists with

• . For prose, use

  . We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO statement, equal opportunity, scam warning, navigation, legal, cookie. Also remove "Note: The SF-85 background check is adjudicated by the Department of Homeland Security..."? That's not boilerplate; it's substantive about screening. Keep it maybe under Requirements. Also remove "CLEAR is an equal opportunity employer..." etc. Also remove "If you need assistance or an accommodation due to a disability, you may contact us at fieldrecruiting@clearme.com." That's accommodation info; could be considered part of Requirements? It's about accommodations; but it's EEO-related. Might be considered boilerplate? It's a statement about accommodations; could be kept but it's more about process. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is EEO/accommodation statement, so remove. Also remove "CLEAR will consider for employment qualified applicants with criminal histories..." etc. That's EEO-related; remove. Now compile content. About the role: combine initial sentence and About CLEAR paragraph. Initial: "The CLEAR Senior Service and Sales Representative (Senior Ambassador) makes magic happen every day by creating frictionless experiences for our members." About CLEAR paragraph: "Have you ever had that green-light feeling? That feeling when you hit every green light and the day just feels like magic? CLEAR’s mission is to create frictionless experiences where every day has that feeling. With more than 30+ million passionate members and hundreds of partners around the world, CLEAR’s identity platform is transforming the way people live, work, and travel. Whether it’s at the airport, stadium, or right on your phone, CLEAR connects you to the things that make you, you - unlocking easier, more secure, and more seamless experiences - making them all feel like magic." We could combine into one

  or two

  . Use

  for prose. Responsibilities:

  • each bullet. Requirements: list items. We need to include the SF-85 note maybe as part of Requirements. Requirements list: - You must be 18 years of age or older - High school diploma or GED equivalent required - Open availability and flexibility is a must – ability to work a variety of shifts - Ability to stand for up to 8 hours per day - Desire to grow into a management and/or leadership position - Successful completion of CLEAR, airport, and government screening as applicable, and CLEAR background checks, including but not limited to a drug test. This may also include federal Personnel Security (PerSec) SF-85 screening, depending on your work assignment - Note: The SF-85 background check is adjudicated by the Department of Homeland Security. This screening may include, but is not limited to, additional criminal screening, credit checks, and verification of identity and citizenship or immigration status, as required by federal security screening standards. We could keep the note as a separate

    under Requirements or as part of the list item. Probably as a separate paragraph. Skills: list items from "What You're Great At". Benefits: list items from "How You'll Be Rewarded". Also include note "Not available in Puerto Rico". Could be a

    after list. Schedule: we have "Open availability and flexibility is a must – ability to work a variety of shifts". That's already in Requirements; but we might move it to Schedule to avoid duplication. However we need to preserve all substantive information; we can keep it in Requirements and also have Schedule? That would duplicate. Better to move schedule-specific content to Schedule section and remove from Requirements. But the requirement about open availability is also a requirement. Could be both. But we should avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication but better to avoid. We could keep it in Requirements and also have Schedule with same content? That would be duplication. Let's think: The posting mentions open availability under Role Requirements. So it's a requirement. So we keep it under Requirements. For Schedule section, we could note that the role requires flexible scheduling, variety of shifts. But that's same info. Might be considered duplication but still preserving info. However we might decide not to create Schedule section because the info is already captured under Requirements. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule info (open availability, variety of shifts). So we could create Schedule section with that info. But we would then have that info also under Requirements (as a requirement). That's okay; it's not invented, it's just present in two places. Might be acceptable. However we might prefer to avoid redundancy