Security Officer Unarmed Vehicle Patrol Driver

We need to output HTML fragment with sections: About the role? The posting includes Overview (company description) maybe as About the role? Actually Overview is about company. Could be "About the role" or "About Allied Universal". 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. 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. We need to include sections only if there is real content. We have: - Overview: description of company and role: could be "About the role" or "About Allied Universal". Probably "About the role" fits. - Job Description: details of duties: we can put under "Responsibilities". It includes bullet-like sentences: Provide customer service..., Conduct regular..., Monitor access..., Respond to incidents..., Document patrols... So we can list as

  • each. - Minimum Requirements: list of requirements: At least one year..., valid driver's license..., comfort using computer..., handcuffs..., pepper spray certification..., age..., high school diploma..., background investigation..., drug screen..., licensing requirements... So we can put under "Requirements" or "Qualifications". The instructions list both Requirements and Qualifications as possible headings. We need to decide which to use. Since we have both experience and qualifications, maybe "Requirements" for mandatory items, "Qualifications" for preferred? But we can combine. However we should avoid thin sections. Perhaps we can have one "Requirements" section covering all mandatory and preferred items. Or we could split: Requirements (mandatory) and Qualifications (preferred). Let's see content: Minimum Requirements section includes both mandatory and preferred items. It says "At least one year of security-related experience is required." (mandatory). "A valid driver’s license is required..." (mandatory). "Comfort using a computer or tablet is preferred." (preferred). "Handcuffs, pepper spray, and baton experience is preferred." (preferred). "Pepper spray certification is preferred." (preferred). "Be at least 18 years of age for unarmed roles; 21+ years of age for armed roles." (mandatory? likely requirement). "Possess a high school diploma or equivalent." (mandatory). Then background investigation, drug screen, licensing requirements (mandatory). So we could separate: Requirements (mandatory) and Qualifications (preferred). That would be two sections, each with substantive content. That seems okay. - Why Join Us: includes Smart Tools, Career Growth, Financial and Health Benefits, Exclusive Perks. That's benefits. So we can have a "Benefits" section with list items. - Pay Rate: $17.00 / Hour. That's pay. So we need a Pay section with that info. - Job Schedule: DayTime Wed 06:00 AM - 06:00 PM etc. Actually schedule: "DayTimeWed06:00 AM - 06:00 PMThur06:00 AM - 06:00 PMFri06:00 AM - 06:00 PM". It seems schedule for Wed, Thu, Fri 6am-6pm. So we have schedule info. So we need a Schedule section. - Position Type: Full Time. Could be part of Schedule or maybe a separate section? Not listed in headings but we could include under Schedule or maybe as a short p. The instructions: we can fold minor metadata into a short

    or drop it. Position type is maybe minor metadata; we could include in a short p under Overview or separate. But we should not create a heading for it unless we have a heading like "Position Type". Not in the list. So we can include it in a paragraph. - Requisition ID: drop. - Closing EEO boilerplate: remove. Thus sections: About the role (or Overview), Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't create sections with filler. All have content. Now format: Use

    for each heading. Then content: For prose use

    . For lists use

    • . We need to preserve all substantive information. Let's extract exact sentences. Overview: "Allied Universal®, North America’s leading security and facility services company, offers rewarding careers that provide you a sense of purpose. While working in a dynamic, welcoming, and collaborative workplace, you will be part of a team that contributes to a culture that positively impacts the communities and customers we serve." That's two sentences. Could be one paragraph. Job Description: "As a Security Officer Unarmed Vehicle Patrol Driver in Marston, MO, you will serve and safeguard clients in a range of industries such as Tech/Media/Telecom, and more. As a Driving Unarmed Patrol Officer at a dynamic technology, media, and telecommunications location, you will conduct routine vehicle and foot patrols, maintain a visible presence to help deter incidents, and respond to security-related concerns. You will provide outstanding customer service, communicate professionally, and support a welcoming environment. Join Allied Universal, where agility, reliability, innovation, teamwork, caring, and integrity guide every shift." But we might combine with Overview? Actually Overview already includes company description. The Job Description includes role specifics. We could put all under "About the role" or "Responsibilities". However the instructions: Use

      for section headings (e.g. About the role, Responsibilities...). So we need to decide where to put the descriptive overview vs duties. Probably "About the role" for overview (company + role summary). Then "Responsibilities" for duties list. Thus About the role paragraph: combine the overview sentences and maybe the first two sentences of Job Description? But we must not duplicate. Let's think: Overview already describes company and role purpose. Job Description includes more specifics about the role: serving clients, patrols, etc. Those are duties. So we can keep Overview as About the role (company + purpose). Then Responsibilities list the duties. Thus About the role: "Allied Universal®, North America’s leading security and facility services company, offers rewarding careers that provide you a sense of purpose. While working in a dynamic, welcoming, and collaborative workplace, you will be part of a team that contributes to a culture that positively impacts the communities and customers we serve." Now Responsibilities: list each duty: - Provide customer service to employees, visitors, contractors, and vendors at a technology, media, and telecommunications location by carrying out security-related procedures, site-specific policies, and when appropriate, emergency response activities. - Conduct regular and random unarmed patrols of interior areas, exterior grounds, parking areas, access points, and the business perimeter, reporting unusual conditions and maintenance concerns. - Monitor access to the location, verify credentials as directed by site procedures, and assist with visitor and contractor sign-in processes. - Respond to incidents, alarms, and critical situations in a calm, problem-solving manner, following established escalation and notification procedures. - Document patrols, incidents, observations, and daily activities accurately in required reports and logs. Now Requirements (mandatory): list: - At least one year of security-related experience is required. - A valid driver’s license is required in accordance with Allied Universal driver policy requirements. - Be at least 18 years of age for unarmed roles; 21+ years of age for armed roles. - Possess a high school diploma or equivalent. - As a condition of employment, applicants will be subject to a background investigation in accordance with all federal, state, and local laws. - As a condition of employment, applicants will be subject to a drug screen to the extent permitted by law. - Licensing requirements are subject to state and/or local laws and regulations and may be required prior to employment. Note: The statement about Allied Universal considering qualified applications with criminal histories is also a requirement? It's more of a policy. Could be included but it's not a requirement for applicant; it's a statement. Might be considered minor metadata; we could include in a p under Requirements or separate. But we can include as a bullet maybe under Requirements? It's not a requirement for applicant; it's a company policy. Might be okay to include but it's not a requirement. The instruction: preserve ALL substantive information. So we should include it. Could be a separate bullet under Requirements or maybe under Qualifications? It's not a qualification. I'd include it as a bullet under Requirements (though it's not a requirement for applicant). Or we could put it in a short p after Requirements. But to keep sections thin, maybe we add it as a bullet under Requirements. Thus Requirements bullets: - At least one year of security-related experience is required. - A valid driver’s license is required in accordance with Allied Universal driver policy requirements. - Be at least 18 years of age for unarmed roles; 21+ years of age for armed roles. - Possess a high school diploma or equivalent. - As a condition of employment, applicants will be subject to a background investigation in accordance with all federal, state, and local laws. - As a condition of employment, applicants will be subject to a drug screen to the extent permitted by law. - Licensing requirements are subject to state and/or local laws and regulations and may be required prior to employment. - Allied Universal will consider qualified applications with criminal histories in a manner consistent with applicable laws. Now Qualifications (preferred): list: - Comfort using a computer or tablet is preferred. - Handcuffs, pepper spray, and baton experience is preferred. - Pepper spray certification is preferred. Now Benefits: from Why Join Us: - Smart Tools: Access to our exclusive technology to view and claim additional shifts to earn more. - Career Growth: Get paid training and access to career growth opportunities. - Financial and Health Benefits: Enjoy access to a retirement savings plan, plus medical, dental, vision, basic life and AD&D, and disability insurance. - Exclusive Perks: Enjoy discounts on top brands and services through our Perks Program. We could format as list items each with bold label? But we just need to preserve info. Could do

      Smart Tools: Access to our exclusive technology to view and claim additional shifts to earn more.

      etc. That preserves. Now Pay: "$17.00 / Hour". Could be a paragraph. Schedule: The schedule text: "Position Type: Full Time Pay Rate: $17.00 / Hour Job Schedule DayTimeWed06:00 AM - 06:00 PMThur06:00 AM - 06:00 PMFri06:00 AM - 06:00 PM". Actually the schedule includes Position Type and Pay Rate already. But we already have Pay separate. Position Type: Full Time could be included in Schedule section or a short p. Since we have Schedule heading, we can include Position Type and schedule details. Thus Schedule section: include Position Type: Full Time and the schedule for Wed, Thu, Fri 6am-6pm. We need to parse the schedule: "DayTimeWed06:00 AM - 06:00 PMThur06:00 AM - 06:00 PMFri06:00 AM - 06:00 PM". Likely means Wednesday, Thursday, Friday 6:00 AM - 6:00 PM. So we can state: "Full Time