Security Officer - Full Time Front Desk Access Services
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (page already shows it)
- 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
2. **Analyze the Input Text:**
Let me parse the job posting content:
- Company: Allied Universal®, North America’s leading security and facility services company
- Overview/culture text
- Job Title/Role: Security Officer Full Time Front Desk Access Services in Leesburg, VA (but I shouldn't repeat the job title as a heading)
- Job Description: Front Desk Security Professional in healthcare location, welcome patients/visitors/staff, maintain professional environment, support access control, badge procedures, respond to questions, communicate security info
- Position Type: Full Time
- Pay Rate: $21.00 / Hour
- Job Schedule: DayTime, Mon-Fri 02:00 PM - 10:00 PM (specific days listed)
- What You'll Do: list of duties (bullet points)
- Minimum Requirements: list of requirements (bullet points)
- Why Join Us: list of benefits/career growth etc. (bullet points)
- Closing: EEO statement, application info, etc. - user said to remove EEO/equal-opportunity boilerplate, legal, scam-warning, application instructions
- Requisition ID: 2026-1678466 - should be folded into a short `
` or dropped per rules
Let me identify sections and content:
**About the role/culture**: The first paragraph about Allied Universal, purpose, dynamic workplace, etc. This is prose. I'll put it under an appropriate heading or as intro prose. The rules say use `
` for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to map the content to these headings, but only include sections with real specific content. I shouldn't create headings if there's no content.
Let's map:
- "About the role" / overview: The first paragraph about Allied Universal, purpose, etc. Has content.
- Responsibilities: "What You'll Do" section. Has specific bullet points.
- Requirements/Qualifications: "Minimum Requirements" section. Has specific list.
- Skills: Not explicitly separate, but maybe part of requirements. The rules mention "Skills" as a possible heading. I'll check if there's distinct skills content. The requirements list includes preferences, but I can maybe fold into Requirements or Qualifications. I'll see.
- Benefits: "Why Join Us" section has specific benefits: retirement savings plan, medical, dental, vision, basic life and AD&D, disability insurance, discounts on top brands and services. Has content.
- Pay: "$21.00 / Hour" stated. Has content.
- Schedule: "Job Schedule DayTime Mon02:00 PM - 10:00 PM..." etc. Has specific schedule.
Rules:
- "never create Pay/Schedule/Benefits sections unless the posting actually states them" -> They are stated, so I can include them.
- "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" -> OK.
- "Do NOT repeat the job title as a heading (the page already shows it)" -> I won't add a heading for the job title.
- "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it" -> I'll fold requisition ID into a short `
` or drop it. I'll probably put it in a small footer paragraph.
- "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions" -> I need to remove the EEO closing, application instructions, etc. The last part about Equal Opportunity Employer, contact info, requisition ID, etc. should be removed or folded minimally.
Let me re-read the rules carefully: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the EEO statement at the end, the "For more information:" lines, the "If you have difficulty..." etc. The requisition ID should be folded into a short `
` or dropped. I'll probably put it in a tiny paragraph at the bottom, but since it's minor metadata, I could fold it into a `
` at the end without a heading.
Now, structure mapping:
Possible headings used:
- `
About the role
` - the opening prose about Allied Universal and purpose
- `Responsibilities
` - "What You'll Do" bullet points
- `Requirements
` - "Minimum Requirements" bullet points (or I could split into Qualifications/Requirements, but rules say use those headings if content exists. I'll use `Requirements
` or maybe `Qualifications
`. The posting says "Minimum Requirements", so I'll use `Requirements
`)
- `Skills
` - not explicitly separate, but the requirements list includes preferred skills/certifications. I could either fold into Requirements or create a Skills section if there's distinct content. Looking at the posting, "Comfortable using a computer or tablet is preferred.", "Customer service experience is preferred.", "CPR and First Aid certification is preferred.", "Access control and badge experience is preferred." These are under Minimum Requirements. I think I'll just include them under Requirements, or maybe create a Skills section if I want to separate, but rules prefer few substantive sections over many thin ones. I'll probably just have Requirements cover it, or maybe add a Skills heading if I can extract distinct skill mentions. But to be safe and follow "prefer a few substantive sections over many thin ones", I'll keep it to: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Skills can be part of Requirements.
Let's check the exact headings examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". They listed both "Requirements" and "Qualifications" as separate examples. I need to decide. The posting has "Minimum Requirements". I could use `Requirements
` and maybe `Qualifications
` if there's distinct qualifications content, but it's all under Minimum Requirements. I'll use `Requirements
` and combine qualifications there. Or I could use `Qualifications
` since the section is called "Minimum Requirements". Actually, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists both Requirements and Qualifications as possible. I'll pick one. Since the posting says "Minimum Requirements", I'll use `Requirements
`. I won't create a separate Qualifications section if there's no distinct content beyond requirements.
- `Benefits
` - "Why Join Us" specific benefits: retirement savings plan, medical, dental, vision, basic life and AD&D, disability insurance, discounts on top brands and services. Has content.
- `Pay
` - "$21.00 / Hour". Has content.
- `Schedule
` - specific schedule Mon-Fri 02:00 PM - 10:00 PM. Has content.
Now, I need to make sure I don't create a section if there's no content. All six have content.
Let's parse each section's content precisely:
**About the role** (or opening):
"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."
I'll wrap in `
`.
**Responsibilities** ("What You'll Do"):
- Provide customer service to patients, visitors, staff, and vendors by carrying out site-specific procedures and security-related policies at a healthcare location.
- Staff the front desk, greet and direct visitors, manage visitor access procedures, and maintain a professional, welcoming presence.
- Monitor access points and report unusual activity, unauthorized entry attempts, and policy concerns to appropriate site contacts and/or Allied Universal leadership.
- Respond to incidents, alarms, and critical situations in a calm, problem-solving manner, following emergency response procedures and contacting appropriate personnel.
- Maintain accurate visitor logs, incident documentation, and required administrative records while handling information with discretion.
I'll use `
- ` for each.
**Requirements** ("Minimum Requirements"):
- Comfortable using a computer or tablet is preferred.
- Customer service experience is preferred.
- CPR and First Aid certification is preferred.
- Access control and badge experience is preferred.
- 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.
- Allied Universal will consider qualified applications with criminal histories in a manner consistent with applicable 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.
- A valid driver’s license will be required for driving positions only.
I'll list the clear requirements. Some are conditional/preferred. I'll include all substantive ones. I'll use `
- `.
**Benefits** ("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.
I'll use `
- `.
**Pay** ("Pay Rate: $21.00 / Hour"):
- I'll put "$21.00 / Hour" as text under the Pay
` for prose - Do NOT repeat the job title as a heading (page already shows it) - 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 2. **Analyze the Input Text:** Let me parse the job posting content: - Company: Allied Universal®, North America’s leading security and facility services company - Overview/culture text - Job Title/Role: Security Officer Full Time Front Desk Access Services in Leesburg, VA (but I shouldn't repeat the job title as a heading) - Job Description: Front Desk Security Professional in healthcare location, welcome patients/visitors/staff, maintain professional environment, support access control, badge procedures, respond to questions, communicate security info - Position Type: Full Time - Pay Rate: $21.00 / Hour - Job Schedule: DayTime, Mon-Fri 02:00 PM - 10:00 PM (specific days listed) - What You'll Do: list of duties (bullet points) - Minimum Requirements: list of requirements (bullet points) - Why Join Us: list of benefits/career growth etc. (bullet points) - Closing: EEO statement, application info, etc. - user said to remove EEO/equal-opportunity boilerplate, legal, scam-warning, application instructions - Requisition ID: 2026-1678466 - should be folded into a short `
` or dropped per rules Let me identify sections and content: **About the role/culture**: The first paragraph about Allied Universal, purpose, dynamic workplace, etc. This is prose. I'll put it under an appropriate heading or as intro prose. The rules say use `
` for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I need to map the content to these headings, but only include sections with real specific content. I shouldn't create headings if there's no content. Let's map: - "About the role" / overview: The first paragraph about Allied Universal, purpose, etc. Has content. - Responsibilities: "What You'll Do" section. Has specific bullet points. - Requirements/Qualifications: "Minimum Requirements" section. Has specific list. - Skills: Not explicitly separate, but maybe part of requirements. The rules mention "Skills" as a possible heading. I'll check if there's distinct skills content. The requirements list includes preferences, but I can maybe fold into Requirements or Qualifications. I'll see. - Benefits: "Why Join Us" section has specific benefits: retirement savings plan, medical, dental, vision, basic life and AD&D, disability insurance, discounts on top brands and services. Has content. - Pay: "$21.00 / Hour" stated. Has content. - Schedule: "Job Schedule DayTime Mon02:00 PM - 10:00 PM..." etc. Has specific schedule. Rules: - "never create Pay/Schedule/Benefits sections unless the posting actually states them" -> They are stated, so I can include them. - "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" -> OK. - "Do NOT repeat the job title as a heading (the page already shows it)" -> I won't add a heading for the job title. - "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it" -> I'll fold requisition ID into a short `
` or drop it. I'll probably put it in a small footer paragraph. - "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions" -> I need to remove the EEO closing, application instructions, etc. The last part about Equal Opportunity Employer, contact info, requisition ID, etc. should be removed or folded minimally. Let me re-read the rules carefully: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the EEO statement at the end, the "For more information:" lines, the "If you have difficulty..." etc. The requisition ID should be folded into a short `
` or dropped. I'll probably put it in a tiny paragraph at the bottom, but since it's minor metadata, I could fold it into a `
` at the end without a heading. Now, structure mapping: Possible headings used: - `
About the role
` - the opening prose about Allied Universal and purpose - `Responsibilities
` - "What You'll Do" bullet points - `Requirements
` - "Minimum Requirements" bullet points (or I could split into Qualifications/Requirements, but rules say use those headings if content exists. I'll use `Requirements
` or maybe `Qualifications
`. The posting says "Minimum Requirements", so I'll use `Requirements
`) - `Skills
` - not explicitly separate, but the requirements list includes preferred skills/certifications. I could either fold into Requirements or create a Skills section if there's distinct content. Looking at the posting, "Comfortable using a computer or tablet is preferred.", "Customer service experience is preferred.", "CPR and First Aid certification is preferred.", "Access control and badge experience is preferred." These are under Minimum Requirements. I think I'll just include them under Requirements, or maybe create a Skills section if I want to separate, but rules prefer few substantive sections over many thin ones. I'll probably just have Requirements cover it, or maybe add a Skills heading if I can extract distinct skill mentions. But to be safe and follow "prefer a few substantive sections over many thin ones", I'll keep it to: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Skills can be part of Requirements. Let's check the exact headings examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". They listed both "Requirements" and "Qualifications" as separate examples. I need to decide. The posting has "Minimum Requirements". I could use `Requirements
` and maybe `Qualifications
` if there's distinct qualifications content, but it's all under Minimum Requirements. I'll use `Requirements
` and combine qualifications there. Or I could use `Qualifications
` since the section is called "Minimum Requirements". Actually, the rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists both Requirements and Qualifications as possible. I'll pick one. Since the posting says "Minimum Requirements", I'll use `Requirements
`. I won't create a separate Qualifications section if there's no distinct content beyond requirements.
- `Benefits
` - "Why Join Us" specific benefits: retirement savings plan, medical, dental, vision, basic life and AD&D, disability insurance, discounts on top brands and services. Has content.
- `Pay
` - "$21.00 / Hour". Has content.
- `Schedule
` - specific schedule Mon-Fri 02:00 PM - 10:00 PM. Has content.
Now, I need to make sure I don't create a section if there's no content. All six have content.
Let's parse each section's content precisely:
**About the role** (or opening):
"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."
I'll wrap in `
`. **Responsibilities** ("What You'll Do"): - Provide customer service to patients, visitors, staff, and vendors by carrying out site-specific procedures and security-related policies at a healthcare location. - Staff the front desk, greet and direct visitors, manage visitor access procedures, and maintain a professional, welcoming presence. - Monitor access points and report unusual activity, unauthorized entry attempts, and policy concerns to appropriate site contacts and/or Allied Universal leadership. - Respond to incidents, alarms, and critical situations in a calm, problem-solving manner, following emergency response procedures and contacting appropriate personnel. - Maintain accurate visitor logs, incident documentation, and required administrative records while handling information with discretion. I'll use `
- ` for each.
**Requirements** ("Minimum Requirements"):
- Comfortable using a computer or tablet is preferred.
- Customer service experience is preferred.
- CPR and First Aid certification is preferred.
- Access control and badge experience is preferred.
- 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.
- Allied Universal will consider qualified applications with criminal histories in a manner consistent with applicable 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.
- A valid driver’s license will be required for driving positions only.
I'll list the clear requirements. Some are conditional/preferred. I'll include all substantive ones. I'll use `
- `.
**Benefits** ("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.
I'll use `
- `. **Pay** ("Pay Rate: $21.00 / Hour"): - I'll put "$21.00 / Hour" as text under the Pay
- `.
**Benefits** ("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.
I'll use `