Roving Security Officer

We need to produce HTML fragment with sections: About the role? The posting includes description: "Ready to suit up as a Special Response Security Guard..." etc. We'll need to parse. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. Let's extract content: - About the role: The introductory paragraph(s) describing role: "Ready to suit up as a Special Response Security Guard... As a casual Security Officer – Response, your role will vary depending on the day and special event. Whether it’s customer service, patrols, or surveillance, we need you to adapt with agility and precision." Also maybe "Tell us about how you embrace change and thrive in the heart of the action." That's about role. - Responsibilities: List of duties: Monitor premises, Conduct patrols, Control access points, Respond quickly, Provide excellent customer service, Write detailed reports, Collaborate with authorities, Ensure safety. - Qualifications: List: Authorized to work in US, Provide documentation of HS diploma or GED, Pass extensive screening, Ability to think quickly, Responsive and strong problem solving skills, Security/Military/Law Enforcement experience a plus, Must have Florida Class D security license, Must be 21+ with valid driver's license and clean driving record (Driving post). Also maybe "Be able to ace (and pass) an extensive screening process". That's qualifications. - Skills: Could be derived from qualifications: ability to think quickly, problem solving, adaptability, etc. But we may not need separate Skills if content overlaps. The instruction: prefer few substantive sections over many thin ones. We could combine Qualifications and Skills? But we have headings list; we can include Qualifications and maybe Skills if there is distinct content. The posting mentions "Ability to think quickly and adapt to changing situations", "Responsive and strong problem solving skills". Those could be skills. Also "If you have Security, Military, Law Enforcement experience – even better!" That's experience. Could be qualifications. We could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Benefits: "A comprehensive benefits package including medical, dental, and vision insurance plans, a 401(k) retirement savings plan with employer matching contributions, paid time off (PTO) policy, paid holidays, disability coverage, and life insurance options", "Career growth opportunities at GardaWorld", "Uniform provided at no cost". Also "DailyPay is available for GardaWorld employees!" That's a benefit. Pay: "$18.00 / Hour Competitive hourly wage of $18.00 / Hour (DailyPay is available for GardaWorld employees!)" Actually DailyPay mentioned also in benefits but we can keep in Pay. Schedule: "Site Location: Tampa, FL Schedule: Special Response / Rover: MUST have OPEN AVAILABILITY 1st (Mornings) & 3rd (Overnight) shifts ( Available any day / on short notice)". So schedule info. We need to avoid repeating job title. Also we should not include boilerplate like EEO, legal, etc. Remove those paragraphs at end. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details: location Tampa, FL; schedule specifics; pay $18/hour; DailyPay; benefits list; uniform; career growth; responsibilities list; qualifications list; etc. We must not include headings with filler like "not specified". So only include sections with content. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Ready to suit up as a Special Response Security Guard... As a casual Security Officer – Response, your role will vary depending on the day and special event. Whether it’s customer service, patrols, or surveillance, we need you to adapt with agility and precision. Tell us about how you embrace change and thrive in the heart of the action.

Responsibilities

• Monitor the premises to ensure security
• Conduct patrols to spot any suspicious activity
• Control access points and verify identities
• Respond quickly to incidents or potential threats
• Provide excellent customer service while maintaining security
• Write detailed reports on events and incidents
• Collaborate with authorities during serious situations
• Ensure the safety and protection of individuals and property

Qualifications

• Authorized to work in the U.S.
• Ability to provide documentation of High School Diploma or GED
• Ability to ace and pass an extensive screening process
• Ability to think quickly and adapt to changing situations
• Responsive and strong problem‑solving skills
• Security, Military, or Law Enforcement experience is a plus
• Must possess a Florida Class D security license
• Must be 21 years of age or older with a valid driver’s license and a clean driving record (this is a driving post)

Benefits

• Comprehensive benefits package: medical, dental, and vision insurance
• 401(k) retirement savings plan with employer matching contributions
• Paid time off (PTO) policy
• Paid holidays
• Disability coverage
• Life insurance options
• Career growth opportunities at GardaWorld
• Uniform provided at no cost
• DailyPay available for GardaWorld employees

Pay

Competitive hourly wage of $18.00 per hour.

Schedule

Site location: Tampa, FL. Schedule: Special Response / Rover – must have open availability for 1st (mornings) and 3rd (overnight) shifts; available any day on short notice.

We need to ensure we didn't repeat job title. Also we need to ensure we didn't include any boilerplate like EEO etc. We removed those. Check for any duplicated lines: we have "DailyPay is available for GardaWorld employees!" appears both in Pay and Benefits; we kept in Benefits and Pay. Might be duplication but it's okay as it's substantive. Could we avoid duplication? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the DailyPay mention somewhere. It's okay to appear in both sections if it's mentioned in both places originally? Actually original text: "$18.00 / Hour Competitive hourly wage of $18.00 / Hour (DailyPay is available for GardaWorld employees!)" and later "A comprehensive benefits package...". DailyPay appears only in the pay line. So we should keep it only in Pay section, not duplicate in Benefits. However we added DailyPay to Benefits as a bullet; that would be adding info not originally in benefits section (though it's a benefit). But it's still substantive info; but we might be adding a bullet that wasn't explicitly under benefits. However the instruction says preserve ALL substantive information; does not forbid placing it elsewhere as long as we don't lose it. Adding it to Benefits is not losing it, but we are adding a bullet that wasn't originally under Benefits but it's still true. However we might be considered adding detail not originally present? It's still true but not explicitly listed under benefits. Safer to keep DailyPay only under Pay section, and not duplicate. Thus adjust Benefits bullet list to exclude DailyPay. Now check if any other info missed: "Career growth opportunities at GardaWorld" we included. "Uniform provided at no cost" included. "Site Location: Tampa, FL" included in schedule. Also "Special Response / Rover: MUST have OPEN AVAILABILITY 1st (Mornings) & 3rd (Overnight) shifts ( Available any day / on short notice)" included. Also we might need to include "As a casual Security Officer – Response" maybe in About the role. Check for any other substantive info: "In the United States, GardaWorld Security remains the only guarding security company to be Certified by Great Place to Work." That's a substantive statement about company; could be included in About the role or maybe a separate section? But we have no heading for company info; we could add to About the role as a sentence. It's not boilerplate; it's a fact about employer. Should we include? The instruction: preserve ALL substantive information. So we should include that statement somewhere. Where fits? Could be in About the role after description. Let's add a sentence: "In the United States, GardaWorld Security remains the only guarding security company to be Certified by Great Place to Work." Also "26% of our corporate employees started as frontline workers. If you’re ambitious with an entrepreneurial spirit – someone who wants to be a GardaWorld Ambassador – a promising career awaits you!" That's also substantive about career growth; we already have career growth opportunities bullet; we could incorporate that statement there. But we already have "Career growth opportunities at GardaWorld". Could add more detail: "26% of corporate employees started as frontline workers; ambitious entrepreneurial spirits can become GardaWorld Ambassadors." That's substantive; we should preserve. So we can add to Benefits bullet list or About the role. Since it's about career growth, we can add to Benefits bullet list as a point: "26% of corporate employees started as frontline workers; ambitious entrepreneurial spirits can become GardaWorld Ambassadors." Also "GardaWorld Security is a global champion in sophisticated and tailored security solutions, employing and training highly skilled and dedicated professionals across the globe." That's also substantive about company; we can add to About the role. Also "Not the job for you? Make sure to check out all our jobs! We also have tactical, surveillance, and concierge roles available." That's basically navigation / boilerplate? It's a suggestion to check other jobs; could be considered boilerplate? It's not EEO/legal but it's a generic call to action; maybe considered navigation? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is like navigation to other jobs; could be considered navigation. Safer to remove. Also "Employment is contingent on the successful completion of a background check and drug screening to be conducted after an offer of employment is extended." That's substantive? It's a condition of employment; could be considered part of qualifications or requirements. It's not boilerplate; it's a condition. Should we preserve? It's substantive info about hiring process. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include that. Where? Could be under Qualifications or a separate section like Requirements. We have Qualifications; we can add a bullet: "Employment contingent upon successful background check and drug screening after offer." Also "It is the policy of GardaWorld Security Services to provide equal employment opportunities..." That's EEO boilerplate; remove. Also "STATE LICENSE B1200012" maybe metadata; could be dropped. Thus we need to incorporate these. Let's restructure sections: About the role: include description, company certifications, global champion statement. Responsibilities: list. Qualifications: list including auth to work, HS diploma, screening, quick thinking, problem solving, security experience a plus, Florida Class D license, 21+ with valid driver's license clean record, employment contingent on background check and drug screening. Benefits: list including medical/dental/vision, 401k match, PTO, paid holidays, disability, life insurance, career growth opportunities, uniform provided, DailyPay? Actually DailyPay is pay not benefit; but