Jobs · Information Technology · California

Security Officers Distribution Screener

Allied Universal · Bloomington, CA · 5 days ago
On-siteInformation Technology$18.5/hrFull-time
The user wants me to reformat a job posting into clean semantic HTML. Let me analyze the content and structure it according to the rules. First, I need to identify the sections: - Company Overview (but the rule says don't repeat job title as heading, and the page already shows it. The posting starts with "Overview Company Overview:" but that's likely a heading. However, the rule says use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Company Overview" could be "About the role" or similar. But the posting has "Job Description" then pay info, then requirements, then another role description for "Security Professional Flex Officer". Actually, the posting seems to have two parts: one for FedEx Security Warehouse positions, and another for Security Professional Flex Officer. But they are in the same posting. Let's read carefully. The text: "Overview Company Overview: Allied Universal®, North America’s leading security and facility services company... Job Description $18.50 Per Hour This is for our FedEx Security Warehouse positions in Bloomington and Ontario Payrate and Schedules Vary by site Requirements Must have an ACTIVE guard card... Please see link to schedule your interview... Allied Universal® is hiring a Security Professional Flex Officer. The Security Professional Flex Officer will serve and safeguard clients... Responsibilities... Qualifications (must Have)... Preferred Qualifications (nice To Have)... Benefits... Closing... Requisition ID..." So there are two distinct job descriptions? Actually, it might be a single posting that includes two roles: FedEx Security Warehouse and Security Professional Flex Officer. But the user wants to reformat the entire posting. I need to include all substantive information. I should structure sections based on content. The rules: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for lists,

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it. Preserve ALL substantive information. Remove boilerplate (EEO, scam warnings, application instructions). Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Never create Pay/Schedule/Benefits sections unless the posting actually states them. Now, the posting has: - Company Overview (prose) - Job Description for FedEx Security Warehouse: includes pay rate ($18.50/hr), locations (Bloomington and Ontario), note that payrate and schedules vary by site. - Requirements for FedEx position (list) - Interview scheduling link (should be removed as application instruction) - Then a separate role: Security Professional Flex Officer with description, responsibilities, qualifications, preferred qualifications, benefits. - Closing with EEO statement (boilerplate, remove) - Requisition ID (metadata, fold into a short

    or drop) I need to decide how to structure. Since there are two roles, maybe separate sections for each? But the rule says "Prefer a few substantive sections over many thin ones." Could combine into one posting with subsections? However, the headings are limited to

    for section headings. I could have sections like "About the Company", "FedEx Security Warehouse Position", "Security Professional Flex Officer Position", each with sub-sections? But the rule says use

    for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid multiple

    for different roles. But the page already shows the job title (maybe the title is "Security Professional Flex Officer"? The user didn't provide the page title. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So I should not include the job title as a heading. The posting mentions two titles: "FedEx Security Warehouse positions" and "Security Professional Flex Officer". Which one is the main? The posting seems to be for both? Actually, the first part says "This is for our FedEx Security Warehouse positions in Bloomington and Ontario". Then later "Allied Universal® is hiring a Security Professional Flex Officer." Might be two separate jobs in one posting. I'll treat them as two distinct roles within the same posting. I'll create sections: - Company Overview (as

    About the Company

    or "Company Overview") - FedEx Security Warehouse Position (maybe

    FedEx Security Warehouse Position

    ) but that's a job title? The rule says do NOT repeat the job title as a heading. But the page already shows it? Not sure. The user says "the page already shows it". Since we don't have the page, we assume the job title is displayed elsewhere. So we should not repeat the job title as a heading. However, we need to differentiate the two roles. Could use "Position Details" or "Role Overview". But the rule says use

    for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So maybe we can have "About the Role" for each? But there are two roles. Might be better to have separate sections for each role with their own responsibilities, requirements, etc. Let's think: The posting is likely a single job posting for "Security Professional Flex Officer" but also mentions FedEx Security Warehouse positions? Actually, reading again: "Job Description $18.50 Per Hour This is for our FedEx Security Warehouse positions in Bloomington and Ontario Payrate and Schedules Vary by site Requirements ... Please see link to schedule your interview ... Allied Universal® is hiring a Security Professional Flex Officer. The Security Professional Flex Officer will serve and safeguard clients..." It seems like the posting includes two separate job advertisements. Possibly the user pasted two job postings together. But we must reformat the given text as is. I'll structure as follows: 1. Company Overview (prose) 2. FedEx Security Warehouse Position - Pay and Schedule (since it mentions pay rate and schedules vary) - Requirements (list) 3. Security Professional Flex Officer Position - About the Role (description) - Responsibilities (list) - Qualifications (list) - Preferred Qualifications (list) - Benefits (list) 4. Additional Information (requisition ID, maybe) But the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The FedEx part states pay rate and schedules vary. The Flex Officer part doesn't mention pay or schedule specifically, but benefits are listed. So we can create Pay/Schedule for FedEx, Benefits for Flex Officer. Also, the interview link is application instruction, remove. EEO statement is boilerplate, remove. Requisition ID: fold into a short

    at the end. Now, let's write HTML. I'll start with

    Company Overview

    then

    for the prose. Then

    FedEx Security Warehouse Position

    but that's a job title? Might be considered repeating job title. The rule: "Do NOT repeat the job title as a heading (the page already shows it)". Since we don't know the page title, but the posting includes two titles. Perhaps the page title is "Security Professional Flex Officer" or "FedEx Security Warehouse". To be safe, I'll avoid using the exact job title as heading. Instead, use "Position Overview" or "Role Details". But the rule says use

    for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So I can use "About the Role" for each role? But there are two roles. Could have "About the FedEx Security Warehouse Role" and "About the Security Professional Flex Officer Role". That might be okay. Alternatively, since the posting is a single document, maybe the main role is Security Professional Flex Officer, and the FedEx part is a specific assignment? The text: "This is for our FedEx Security Warehouse positions in Bloomington and Ontario" then later "Allied Universal® is hiring a Security Professional Flex Officer." Could be that the Flex Officer role includes FedEx assignments. But the requirements differ (guard card vs not). Actually, the FedEx requirements include "Must have an ACTIVE guard card" while Flex Officer qualifications don't mention guard card. They are separate. I'll treat them as two separate positions within the same company. I'll create two main sections with headings "FedEx Security Warehouse Position" and "Security Professional Flex Officer Position". But to avoid repeating job title, maybe "Position: FedEx Security Warehouse" and "Position: Security Professional Flex Officer". However, the rule says "Do NOT repeat the job title as a heading". If the page already shows the job title, we shouldn't repeat it. Since we don't have the page, we assume the page shows one title. The user gave us the entire text. I think it's safer to not use the exact job title as heading. Instead, use generic headings like "Position Details" for each? But that would be ambiguous. Let's read the rule again: "Do NOT repeat the job title as a heading (the page already shows it)". This implies that the HTML fragment will be inserted into a page that already has the job title displayed. So we should not include an

    with the job title. But we can have other headings like "About the Role", "Responsibilities", etc. So for each role, we can have "About the Role" but there are two roles. That would be confusing. Maybe the posting is actually for the Security Professional Flex Officer, and the FedEx part is a specific location? The text: "Job Description $18.50 Per Hour This is for our FedEx Security Warehouse positions in Bloomington and Ontario Payrate and Schedules Vary by site Requirements ... Please see link to schedule your interview ... Allied Universal® is hiring a Security Professional Flex Officer." It seems like two separate job ads concatenated. The user wants us to reformat the entire posting. I think we should include both, but structure them clearly. I'll use

    for each major section: "Company Overview", "FedEx Security Warehouse Position", "Security Professional Flex Officer Position". But the first is not a job title, it's company overview. The second and third are job titles. However, the rule says not to repeat the job title as a heading. If the page already shows the job title, then we shouldn't include it. But we have two job titles. Which one is the page title? Unknown. Perhaps the page title is "Security Professional Flex Officer" because that's the last one mentioned? Or maybe the posting is for "Security Professional Flex Officer" and the FedEx part is a specific assignment description. The Flex Officer description says "The Security Professional Flex Officer will serve and safeguard clients in a range of industries such as Healthcare, Education, Finance and more." Not specifically FedEx. So they are separate. Given the ambiguity, I'll follow the rule: do not repeat the job title as a heading. So I will not create an

    with "FedEx Security Warehouse Position" or "Security Professional Flex Officer". Instead, I'll create sections like "Position Overview" for each? But that would be duplicate headings. Better to combine into one "Positions" section? But the rule says prefer a few substantive sections over many thin ones. Maybe the best is to treat the whole posting as one job posting for "Security Professional Flex Officer" and the FedEx part is a specific location detail? But the requirements differ. The FedEx part requires guard card, weekends, etc. The Flex Officer part has different qualifications. They are distinct. I think the user expects us to reformat the given text as is, preserving all substantive information. The rule about not repeating job title is to avoid duplication with the page title. Since we don't have the page title, we can assume the page title is not included in

Similar jobs

Security Officer Screener

Allied UniversalWichita, KS· 4 mo ago
Information Technology$19.17/hrapply on securitycareers-aus.icims.com

Security Officer Screener

Allied UniversalEvangeline Parish County, LA· 3 mo ago
Information Technology$15.24/hrapply on securitycareers-aus.icims.com

Security Officer Screener

Allied UniversalMiami, FL· 4 mo ago
Information Technology$15.24/hrapply on securitycareers-aus.icims.com