Security Guard - Part Time Patrol Documentation
` 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
- Job Title: Security Officer – Part Time Enhanced (implied, but I shouldn't repeat it as a heading)
- Location: Ashburn, VA (implied from "Security Guard Enhanced Part Time Patrol Documentation in Ashburn, VA")
- Pay Rate: $23.36 / Hour
- Job Schedule: DayTimeSat11:00 PM - 07:00 AM (looks like a typo/messy format: "DayTimeSat11:00 PM - 07:00 AM" - probably means evening/night shift, maybe "Saturday" or just a shift description. I'll handle it carefully.)
- How This Role Works: Fixed-Shift Commitment ("Anchor Shifts"), 6 month commitment. Earn More, Claim-A-Shift Program.
- Responsibilities: list of duties
- Minimum Requirements: list of requirements
- Why Join Us: benefits/culture points
- Closing: EEO statement, application info, etc. -> I need to REMOVE EEO/equal-opportunity/scam-warning boilerplate per rules.
- Requisition ID: 2026-1678730 -> fold into short
or drop, but not as heading.
Let me extract substantive content section by section, following the rules.
**Headings allowed per rules:** About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
But: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text"
Also: "never create Pay/Schedule/Benefits sections unless the posting actually states them"
Let's check what's actually in the posting:
- Pay: "$23.36 / Hour" -> real content, should have a Pay section.
- Schedule: "DayTimeSat11:00 PM - 07:00 AM" and description of fixed-shift, anchor shifts, Claim-A-Shift program. There's schedule info, but it's mixed with role description. I'll create a Schedule section if there's specific schedule info, but careful not to include placeholder text.
- Benefits: "Smart Tools: Access to our exclusive technology...", "Career Growth: Get paid training and access to career growth opportunities.", "Financial Benefits: Participate in our retirement savings plan...", "Exclusive Perks: Enjoy discounts on top brands and services through our Perks Program." -> These are real benefits, but the heading "Benefits" should only appear if there's real content. I'll structure them properly.
- Qualifications/Requirements: The posting has "Minimum Requirements" section. Rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to decide how to map "Minimum Requirements" -> probably "Requirements" or "Qualifications". The rules list both "Requirements" and "Qualifications". I'll likely use one, or combine if needed, but must preserve all substantive info. I'll check if there's a distinction. The posting has "Minimum Requirements" followed by bullet points. I'll use `Requirements
` or `Qualifications
`. Rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll pick one that fits best. Probably "Requirements" since the section says "Minimum Requirements". But to be safe, I'll look at the content: it lists preferences and requirements. I'll use `Requirements
`.
- Skills: Not explicitly separate, but some are mentioned (CPR certification, access control, customer service). I'll maybe fold into Requirements or Qualifications, or create a Skills section if there's distinct content. The rules say include section ONLY when there's real specific content. I'll see.
- About the role: There's job description, "How This Role Works", etc. I'll use `About the role
` or maybe just fold into an intro paragraph. The rules say use for section headings (e.g. About the role, ...). I'll include it if there's substantive content.
- Responsibilities: clearly listed. `Responsibilities
`
- Requirements/Qualifications: `Requirements
`
- Pay: `$23.36 / Hour` -> `Pay
`
- Schedule: shift details, anchor shifts, etc. -> `Schedule
` but careful: the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them". It does state pay and schedule-related content. I'll create them.
- Benefits: the "Why Join Us" section has benefits. I'll create `Benefits
` but must ensure no placeholder text. The content is real: smart tools, career growth, financial benefits, exclusive perks.
Now, what to REMOVE per rules:
- Cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- The closing EEO statement: "Allied Universal® is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race/ethnicity, age, color, religion, sex, sexual orientation, gender identity, national origin, genetic information, disability, protected veteran status or relationship/association with a protected veteran, or any other basis or characteristic protected by law." -> REMOVE.
- "For more information: www.aus.com." -> REMOVE or maybe fold into
but rules say remove application instructions. I'll drop.
- "If you have difficulty using the online system and require an alternate method to apply or require an accommodation, please contact our local Human Resources department." -> REMOVE.
- "To find an office near you, please visit: www.aus.com/offices." -> REMOVE.
- "Requisition ID 2026-1678730" -> fold into short
or drop. I'll fold into a short
at the end or beginning, but not as heading.
- Job title: "do NOT repeat the job title as a heading (the page already shows it)" -> I won't add a heading for it. I might mention it in prose or drop it. The rules say "Do NOT repeat the job title as a heading". I'll just not include it as a heading. I could include it in a
but maybe better to just omit or mention briefly without heading. I'll see. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)" -> I'll just not output a heading for it. I might still include it in text if needed, but probably best to drop or put in a
without heading. I'll keep it minimal.
Let's re-read carefully: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put Requisition ID in a
, but not as heading. I'll fold it into a
at the bottom or somewhere.
Now, let's map the sections that have real content:
1. **About the role / Job Description**: The posting starts with "Life doesn’t always follow a fixed schedule. That’s why we created the Security Officer – Part Time Enhanced position..." and "Job Description" section. I'll use `
About the role
` or maybe just `Job Description
`. The rules list "About the role" as an example heading. I'll use `About the role
` and put the description there.
Wait, the rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So these are the allowed headings. I should use them only if there's real content.
Let's list the content I'll include:
- **About the role**: The introductory paragraph about Allied Universal, the position, flexibility, etc. I'll combine the first part.
- **Responsibilities**: bullet list of duties.
- **Requirements**: bullet list of minimum requirements.
- **Pay**: "$23.36 / Hour"
- **Schedule**: shift description, anchor shifts, 6-month commitment, Claim-A-Shift program. I'll structure Schedule section with the specific schedule info.
- **Benefits**: Smart Tools, Career Growth, Financial Benefits, Exclusive Perks. I'll put these as a list under Benefits, but careful: the rules say "never emit a heading followed by filler/placeholder text". The benefits content is real, so `Benefits
` is fine. But I need to format the benefits as prose or list. The rules say "Use - for any list of duties/requirements/benefits, and
for prose." So benefits that are list-like can be
- , but the "Why Join Us" section has bullet-point-like sentences. I'll use
- for those, or
if they are prose. I'll decide case by case.
Let's parse the "Why Join Us" section:
"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 Benefits: Participate in our retirement savings plan to invest in your future.
Exclusive Perks: Enjoy discounts on top brands and services through our Perks Program."
These are four points. I'll put them as `
- ` items under a `
Benefits
` heading, or maybe keep as with inline. Rules prefer
- for lists of benefits. I'll use `
- `.
Responsibilities bullet points:
"Provide customer service to tenants, visitors, contractors, and/or employees at a commercial real estate location by following site-specific procedures and security-related policies.
Conduct regular and random unarmed patrols of building interiors, exterior grounds, parking areas, access points
` 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 - Job Title: Security Officer – Part Time Enhanced (implied, but I shouldn't repeat it as a heading) - Location: Ashburn, VA (implied from "Security Guard Enhanced Part Time Patrol Documentation in Ashburn, VA") - Pay Rate: $23.36 / Hour - Job Schedule: DayTimeSat11:00 PM - 07:00 AM (looks like a typo/messy format: "DayTimeSat11:00 PM - 07:00 AM" - probably means evening/night shift, maybe "Saturday" or just a shift description. I'll handle it carefully.) - How This Role Works: Fixed-Shift Commitment ("Anchor Shifts"), 6 month commitment. Earn More, Claim-A-Shift Program. - Responsibilities: list of duties - Minimum Requirements: list of requirements - Why Join Us: benefits/culture points - Closing: EEO statement, application info, etc. -> I need to REMOVE EEO/equal-opportunity/scam-warning boilerplate per rules. - Requisition ID: 2026-1678730 -> fold into short
or drop, but not as heading. Let me extract substantive content section by section, following the rules. **Headings allowed per rules:** About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule But: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text" Also: "never create Pay/Schedule/Benefits sections unless the posting actually states them" Let's check what's actually in the posting: - Pay: "$23.36 / Hour" -> real content, should have a Pay section. - Schedule: "DayTimeSat11:00 PM - 07:00 AM" and description of fixed-shift, anchor shifts, Claim-A-Shift program. There's schedule info, but it's mixed with role description. I'll create a Schedule section if there's specific schedule info, but careful not to include placeholder text. - Benefits: "Smart Tools: Access to our exclusive technology...", "Career Growth: Get paid training and access to career growth opportunities.", "Financial Benefits: Participate in our retirement savings plan...", "Exclusive Perks: Enjoy discounts on top brands and services through our Perks Program." -> These are real benefits, but the heading "Benefits" should only appear if there's real content. I'll structure them properly. - Qualifications/Requirements: The posting has "Minimum Requirements" section. Rules say use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I need to decide how to map "Minimum Requirements" -> probably "Requirements" or "Qualifications". The rules list both "Requirements" and "Qualifications". I'll likely use one, or combine if needed, but must preserve all substantive info. I'll check if there's a distinction. The posting has "Minimum Requirements" followed by bullet points. I'll use `Requirements
` or `Qualifications
`. Rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll pick one that fits best. Probably "Requirements" since the section says "Minimum Requirements". But to be safe, I'll look at the content: it lists preferences and requirements. I'll use `Requirements
`.
- Skills: Not explicitly separate, but some are mentioned (CPR certification, access control, customer service). I'll maybe fold into Requirements or Qualifications, or create a Skills section if there's distinct content. The rules say include section ONLY when there's real specific content. I'll see.
- About the role: There's job description, "How This Role Works", etc. I'll use `About the role
` or maybe just fold into an intro paragraph. The rules say use for section headings (e.g. About the role, ...). I'll include it if there's substantive content.
- Responsibilities: clearly listed. `Responsibilities
`
- Requirements/Qualifications: `Requirements
`
- Pay: `$23.36 / Hour` -> `Pay
`
- Schedule: shift details, anchor shifts, etc. -> `Schedule
` but careful: the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them". It does state pay and schedule-related content. I'll create them.
- Benefits: the "Why Join Us" section has benefits. I'll create `Benefits
` but must ensure no placeholder text. The content is real: smart tools, career growth, financial benefits, exclusive perks.
Now, what to REMOVE per rules:
- Cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
- The closing EEO statement: "Allied Universal® is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race/ethnicity, age, color, religion, sex, sexual orientation, gender identity, national origin, genetic information, disability, protected veteran status or relationship/association with a protected veteran, or any other basis or characteristic protected by law." -> REMOVE.
- "For more information: www.aus.com." -> REMOVE or maybe fold into
Responsibilities
` - Requirements/Qualifications: `Requirements
` - Pay: `$23.36 / Hour` -> `Pay
` - Schedule: shift details, anchor shifts, etc. -> `Schedule
` but careful: the rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them". It does state pay and schedule-related content. I'll create them. - Benefits: the "Why Join Us" section has benefits. I'll create `Benefits
` but must ensure no placeholder text. The content is real: smart tools, career growth, financial benefits, exclusive perks. Now, what to REMOVE per rules: - Cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - The closing EEO statement: "Allied Universal® is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race/ethnicity, age, color, religion, sex, sexual orientation, gender identity, national origin, genetic information, disability, protected veteran status or relationship/association with a protected veteran, or any other basis or characteristic protected by law." -> REMOVE. - "For more information: www.aus.com." -> REMOVE or maybe fold intobut rules say remove application instructions. I'll drop. - "If you have difficulty using the online system and require an alternate method to apply or require an accommodation, please contact our local Human Resources department." -> REMOVE. - "To find an office near you, please visit: www.aus.com/offices." -> REMOVE. - "Requisition ID 2026-1678730" -> fold into short
or drop. I'll fold into a short
at the end or beginning, but not as heading. - Job title: "do NOT repeat the job title as a heading (the page already shows it)" -> I won't add a heading for it. I might mention it in prose or drop it. The rules say "Do NOT repeat the job title as a heading". I'll just not include it as a heading. I could include it in a
but maybe better to just omit or mention briefly without heading. I'll see. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)" -> I'll just not output a heading for it. I might still include it in text if needed, but probably best to drop or put in a
without heading. I'll keep it minimal. Let's re-read carefully: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can put Requisition ID in a
, but not as heading. I'll fold it into a
at the bottom or somewhere. Now, let's map the sections that have real content: 1. **About the role / Job Description**: The posting starts with "Life doesn’t always follow a fixed schedule. That’s why we created the Security Officer – Part Time Enhanced position..." and "Job Description" section. I'll use `
About the role
` or maybe just `Job Description
`. The rules list "About the role" as an example heading. I'll use `About the role
` and put the description there. Wait, the rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So these are the allowed headings. I should use them only if there's real content.
Let's list the content I'll include:
- **About the role**: The introductory paragraph about Allied Universal, the position, flexibility, etc. I'll combine the first part.
- **Responsibilities**: bullet list of duties.
- **Requirements**: bullet list of minimum requirements.
- **Pay**: "$23.36 / Hour"
- **Schedule**: shift description, anchor shifts, 6-month commitment, Claim-A-Shift program. I'll structure Schedule section with the specific schedule info.
- **Benefits**: Smart Tools, Career Growth, Financial Benefits, Exclusive Perks. I'll put these as a list under Benefits, but careful: the rules say "never emit a heading followed by filler/placeholder text". The benefits content is real, so `Benefits
` is fine. But I need to format the benefits as prose or list. The rules say "Use - for any list of duties/requirements/benefits, and
for prose." So benefits that are list-like can be
- , but the "Why Join Us" section has bullet-point-like sentences. I'll use
- for those, or
if they are prose. I'll decide case by case.
Let's parse the "Why Join Us" section:
"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 Benefits: Participate in our retirement savings plan to invest in your future.
Exclusive Perks: Enjoy discounts on top brands and services through our Perks Program."
These are four points. I'll put them as `
- ` items under a `
Benefits
` heading, or maybe keep as with inline. Rules prefer
- for lists of benefits. I'll use `
- `.
Responsibilities bullet points:
"Provide customer service to tenants, visitors, contractors, and/or employees at a commercial real estate location by following site-specific procedures and security-related policies.
Conduct regular and random unarmed patrols of building interiors, exterior grounds, parking areas, access points
for prose." So benefits that are list-like can be
- , but the "Why Join Us" section has bullet-point-like sentences. I'll use
- for those, or
if they are prose. I'll decide case by case. Let's parse the "Why Join Us" section: "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 Benefits: Participate in our retirement savings plan to invest in your future. Exclusive Perks: Enjoy discounts on top brands and services through our Perks Program." These are four points. I'll put them as `
- ` items under a `
Benefits
` heading, or maybe keep aswith inline. Rules prefer
- for lists of benefits. I'll use `
- `. Responsibilities bullet points: "Provide customer service to tenants, visitors, contractors, and/or employees at a commercial real estate location by following site-specific procedures and security-related policies. Conduct regular and random unarmed patrols of building interiors, exterior grounds, parking areas, access points
- for lists of benefits. I'll use `
- ` items under a `
- for those, or