Autonomous Vehicle Fleet Supervisor

We need to output only HTML fragment, no html/body tags. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. Let's parse posting. Content: - Intro: "Cognizant is a Large IT Consulting Firm..." includes description, location: On Site, must reside in US, legally authorized. Also mentions "Autonomous Vehicle Fleet Supervisor" role. - Role Responsibilities: list bullet points. - Desired Skills & Experience: list bullet points. - Salary And Other Compensation: includes application deadline, hourly rate $26-28, discretionary annual incentive program. - Benefits: list bullet points. - Disclaimer: about hourly rate etc. - The Cognizant Community: description. - About Us: description. We need to decide sections: About the role (maybe intro description), Responsibilities, Requirements (maybe desired skills & experience), Qualifications (maybe education/experience?), Skills (maybe desired skills?), Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes "Applications will be accepted until October 9th, 2026." That's application instruction? It's a deadline; maybe we keep as part of Pay section? It's not exactly application instructions like "apply via". It's a deadline; we can keep as part of Pay or maybe a separate note. The instruction says remove application instructions. The deadline might be considered application instruction; but it's also substantive info about timing. However they said remove application instructions. Safer to remove that line? But they said preserve ALL substantive information; do NOT invent or summarize away detail. The deadline is substantive. However it's an application instruction (when to apply). The rule says remove application instructions. I'd remove the deadline line to comply. But then we lose info. However maybe they consider that as part of "Pay" section? Not sure. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the line about applications accepted until date. So we will omit that. Now we need to decide sections. We have: - About the role: description of role, location, authorization, etc. Could be a paragraph. - Responsibilities: list of duties. - Requirements: maybe education/experience? The posting has "Desired Skills & Experience" includes high school diploma or GED, Bachelor's preferred, 3+ years supervisory experience, etc. That could be Requirements or Qualifications. We'll map: Requirements: education and experience. Qualifications: maybe skills? But we have Skills section separate. Let's think: typical sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to avoid thin sections. We have content for About the role, Responsibilities, Requirements (education/experience), Skills (customer service, communication, shift availability, etc.), Benefits, Pay. Schedule: maybe mention availability to work in different shifts (24 hours). That's schedule info. So we can have Schedule section. Qualifications: maybe we can combine with Requirements? But we need to avoid filler. Could put Qualifications as "Bachelor's Degree preferred" etc. But we already have education/experience in Requirements. Could treat Requirements as "High school diploma or GED, Bachelor's Degree preferred, 3+ Years of supervisory experience." Qualifications could be "Excellent customer service skills, Ability to work independently and in a team-oriented environment, Strong communication and conflict resolution skills." Skills could be "Availability to work in different shifts (24 hours)"? Actually shift availability is schedule. Hmm. Better: Use Requirements for education/experience, Qualifications for core competencies (customer service, communication, conflict resolution), Skills for specific abilities (maybe none left). But we need to avoid duplication. Let's extract bullet points: From "Desired Skills & Experience": - High school diploma or GED, Bachelor's Degree preferred - 3+ Years of supervisory experience. - Excellent customer service skills. - Availability to work in different shifts (24 hours). - Able to work independently and in a team-oriented environment. - Strong communication and conflict resolution skills. We can categorize: Requirements (education/experience): - High school diploma or GED; Bachelor's Degree preferred. - 3+ Years of supervisory experience. Qualifications (core competencies): - Excellent customer service skills. - Able to work independently and in a team-oriented environment. - Strong communication and conflict resolution skills. Skills (maybe shift availability? but that's schedule). Could treat shift availability as Schedule. Thus Schedule: Availability to work in different shifts (24 hours). Now Responsibilities: list from "Role Responsibilities". We'll keep each as

. Benefits: list from Benefits section. Pay: hourly rate $26-28 per hour, discretionary annual incentive program. We also have mention "This position is also eligible for Cognizant’s discretionary annual incentive program, based on performance and subject to the terms of Cognizant’s applicable plans." That's part of Pay. Now About the role: we need to capture description: "Cognizant is a Large IT Consulting Firm that leverages modern technologies to improve a variety of business operations. As our team continues to grow, we are currently looking to hire additional Teams Leads. This role is On Site, and all candidates must reside in the United States. Cognizant will only consider applicants for this position who are legally authorized to work in the United States without requiring company sponsorship now or at any time in the future. The Autonomous Vehicle Fleet Supervisor plays a crucial role it coordinates all day-to-day field operations, ensuring the highest levels of customer service, efficiency, and safety. This position involves providing guidance to staff, handles driver check-in processes, assigning work, and coordinates schedule rotations. Develops a safe team-oriented environment, maintains adherence to established protocols, and handles various tasks to ensure smooth operations." We need to preserve all substantive info. We'll put that in a

maybe multiple paragraphs. Now we must not repeat job title as heading. The job title is "Autonomous Vehicle Fleet Supervisor". We'll not use as heading. Now we need to output only HTML fragment, no /. Use

for headings. We'll produce sections in order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we may omit Skills if we don't have distinct content; but we have shift availability as schedule. Could we omit Skills? The instruction: Prefer a few substantive sections over many thin ones. If we have no specific skills beyond those already captured, we could omit Skills. But we have shift availability which is schedule. So we can omit Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check if we have content for each: - About the role: yes. - Responsibilities: yes. - Requirements: education/experience. - Qualifications: customer service, teamwork, communication. - Benefits: list. - Pay: hourly rate + incentive. - Schedule: availability to work in different shifts (24 hours). Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now we need to format lists:

• for any list of duties/requirements/benefits. For About the role we can use

  paragraphs. For Responsibilities:

  • each duty. For Requirements:
    • each. For Qualifications:
      • each. For Benefits:
        • each. For Pay: maybe

          with details. For Schedule:

          or

          • ? It's a single item; we can use

            . Now we need to remove duplicated lines. Check for duplicates: none. Now we need to ensure we don't include any boilerplate like "Disclaimer: The hourly rate, other compensation, and benefits information is accurate as of the date of this posting." That's a disclaimer; maybe we should keep? It's not cookie/navigation/legal/EEO etc. It's a disclaimer about compensation accuracy. Might be considered legal boilerplate? It's a disclaimer. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about compensation. Might be considered legal boilerplate; safer to remove. However it's substantive about accuracy. But it's a disclaimer; I'd remove to follow instruction. Also "The Cognizant Community" and "About Us" sections are boilerplate marketing; we should remove as they are not specific to the role. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't explicitly say to remove marketing fluff, but we should preserve ALL substantive information. The "The Cognizant Community" and "About Us" are generic company description, not specific to role. Might be considered boilerplate. However they are not explicitly listed to remove. But they are not substantive to the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we remove them, we are removing detail that is present in posting. Are they substantive? They are generic fluff but still part of posting. The instruction didn't say to remove marketing fluff. However earlier they said "Prefer a few substantive sections over many thin ones." So we could include them as part of About the role? But they are not about the role. Might be better to include them as part of About the role? But they'd be thin. Given the instruction to prefer few substantive sections, we could omit those generic sections as they are not specific to the role. However we risk violating "preserve ALL substantive information". But maybe they consider that not substantive to the job. I'd keep them as part of About the role? Actually About the role already includes description of role and location etc. Adding generic company fluff would dilute. I think we should keep only role-specific info. The generic sections are not essential to understanding the role. I'll omit them. Now we need to ensure we don't include any mention of "Applications will be accepted until October 9th, 2026." Remove. Now produce HTML. Let's craft:

            About the role

            Cognizant is a large IT consulting firm that leverages modern technologies to improve business operations. The team is growing and seeking additional Team Leads. This position is on‑site and requires candidates to reside in the United States and be legally authorized to work in the U.S. without sponsorship. The Autonomous Vehicle Fleet Supervisor coordinates day‑to‑day field operations, ensuring high levels of customer service, efficiency, and safety. Responsibilities include providing guidance to staff, managing driver check‑in processes, assigning work, coordinating schedule rotations, fostering a safe team‑oriented environment, maintaining protocol adherence, and handling various tasks to keep operations running smoothly.

            Responsibilities

            • Direct and guide field staff to maintain outstanding customer service and operational efficiency in a safe manner.
            • Manage driver check‑in processes, including readiness for the schedule, daily checklists, and assignment of day‑to‑day tasks.
            • Supervise operational targets and adjust schedules for operational efficiencies.
            • Ensure drivers comply and adhere to procedural guidelines.
            • Observe safety practices and take corrective action when required.
            • Monitor and handle break times for drivers to ensure compliance with regulations.
            • Assist dispatch supervisors, including coordinating wheelchair assistance calls.
            • Assist Operations/Depot Manager during training sessions and one‑on‑one meetings.
            • Interact with officials on routine matters during shifts.