Jobs · Management · Massachusetts

Security Professional Pharmaceutical Site

Allied Universal · Cambridge, MA · Yesterday
On-siteManagement$24/hrPart-time
The user wants me to convert this job posting into clean semantic HTML following specific rules. Let me analyze the content and structure it appropriately. First, I need to identify the sections: - Company Overview (but this is more of an intro) - Job Description (overview of the role) - Starting Pay (explicitly stated) - Responsibilities (list provided) - Qualifications (must have) - detailed list - Preferred Qualifications (nice to have) - short list - Benefits - detailed list - Closing (EEO statement, contact info, requisition ID - should be removed per rules) Rules to follow: - Use

for section headings (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 into short

    or drop - Preserve ALL substantive information - Remove boilerplate (EEO, scam warnings, application instructions, contact info) - Include section ONLY when real specific content exists - Never emit heading with filler/placeholder text - Never create Pay/Schedule/Benefits unless actually stated - Output ONLY HTML fragment, no html/body, no markdown fences Now, let's map the content: 1. "Overview Company Overview" - this is prose about the company. Could be "About the role" or "About the company". Since it's about the company, maybe "About the company" but the rule says headings like "About the role". I'll use "About the role" for the job description paragraph. 2. "Job Description" paragraph - describes the flex officer role. This is "About the role". 3. "Starting Pay $24 / hour" - this is Pay section. 4. "Must have at least 1 year of security experience" - this is a requirement, but also appears in qualifications. Actually, the qualifications section says "No prior experience required" but the job description says "Must have at least 1 year of security experience". There's a contradiction. I'll include both as stated. 5. "Part time flexible weekdays and weekends with all shifts available" - this is Schedule. 6. "Paid orientation and Paid training" - could be Benefits or part of Pay. 7. Responsibilities - list provided. 8. Qualifications (must Have) - long list. 9. Preferred Qualifications (nice To Have) - short list. 10. Benefits - list provided. 11. Closing - EEO, contact, requisition ID - remove. Now, I need to decide on section headings. The rules suggest: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I'll create: - About the role (combining company overview and job description) - Pay (starting pay) - Schedule (part time flexible weekdays and weekends) - Responsibilities - Qualifications (must have) - but the rule says "Requirements" or "Qualifications". I'll use "Qualifications" for must-have, and maybe "Preferred qualifications" for nice-to-have. - Benefits Note: The qualifications list includes both requirements and skills. The rule says "Requirements" and "Qualifications" and "Skills". But the posting has "Qualifications (must Have)" and "Preferred Qualifications". I'll use "Qualifications" for must-have, and "Preferred qualifications" for nice-to-have. Also, "Skills" might be separate, but the qualifications list includes skills like communication, etc. I'll keep them under Qualifications. Now, the "Must have at least 1 year of security experience" appears in the job description but the qualifications say "No prior experience required". I'll include both as separate bullet points? Actually, the job description says "Must have at least 1 year of security experience" right after Starting Pay. Then in Qualifications it says "No prior experience required". This is contradictory. I'll include both as they appear: maybe under Requirements or Qualifications. I'll put the "Must have at least 1 year of security experience" under a "Requirements" section? But the rule says use "Requirements" as a heading. However, the posting doesn't have a separate "Requirements" heading; it's in the job description. I'll create a "Requirements" section for that line and the "Part time flexible..." maybe? But "Part time flexible..." is schedule. Better to follow the posting's structure: The posting has "Starting Pay", "Must have at least 1 year...", "Part time flexible...", "Paid orientation...", then "Responsibilities", "Qualifications (must Have)", "Preferred Qualifications", "Benefits". I'll create sections: - About the role (company overview + job description paragraph) - Pay (starting pay) - Schedule (part time flexible weekdays and weekends with all shifts available) - Benefits (paid orientation and paid training could go here, but also the benefits list later. I'll combine: include paid orientation/training in Benefits section along with the listed benefits) - Responsibilities - Qualifications (must have) - Preferred qualifications But the rule says "Benefits" section only if posting actually states them. It does. Also, "Paid orientation and Paid training" is mentioned before responsibilities. I'll include that in Benefits. Now, the "Must have at least 1 year of security experience" - I'll put that under a "Requirements" heading? The rule says use "Requirements" as a heading. But the posting doesn't have a "Requirements" heading; it's a bullet in the job description. However, the rule says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I can use "Requirements" for that line. But it's just one line. I could include it in Qualifications? But Qualifications says "No prior experience required". That's contradictory. I'll include both under "Qualifications" as separate bullets? Actually, the "Must have at least 1 year of security experience" is in the job description before responsibilities. It might be a requirement. I'll create a "Requirements" section with that one bullet, and then "Qualifications" for the must-have list. But that seems thin. The rule says "Prefer a few substantive sections over many thin ones." So maybe combine: include that line in the Qualifications section as a bullet. But the Qualifications section already has a list. I'll add it as the first bullet in Qualifications? However, the Qualifications section says "No prior experience required". That's directly contradictory. I'll preserve both as they appear in the posting: the job description says "Must have at least 1 year of security experience", and the Qualifications section says "No prior experience required". I'll include both in the Qualifications section, maybe with a note? But the rule says preserve ALL substantive information; do NOT invent or summarize away detail. So I must include both. I'll put the "Must have at least 1 year of security experience" as a bullet in a "Requirements" section, and the Qualifications list under "Qualifications". But the rule says never create a section unless real specific content. A single bullet might be thin. However, the posting explicitly states it as a requirement. I'll include it in the "Qualifications" section as a bullet, but then there's a contradiction. I think the best is to have a "Requirements" section with that one bullet, and then "Qualifications" for the must-have list. But the rule says "Requirements" is an example heading. I'll do that. Alternatively, I could put the "Must have at least 1 year of security experience" in the "About the role" paragraph? But it's a distinct requirement. Let me structure:

    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.

    Allied Universal® is hiring a Security Professional Flex Officer. The Security Professional Flex Officer will serve and safeguard clients in a range of industries such as Healthcare, Education, Finance and more. Join a leading team where flexibility meets opportunity. As a Security Professional Flex Officer, you’ll use our exclusive shift-pickup platform to view and claim open shifts based on your availability - giving you the freedom to build a schedule that works for you, while gaining valuable site experience across various industries. Whether you're looking to supplement your income or take the first step toward a phenomenal career, this position offers unmatched access to hands-on experience and growth opportunities. The Security Professional Flex Officer may be called upon to work irregular shifts at times with little to no advance notice.

    Pay

    Starting pay: $24 per hour.

    Schedule

    Part-time, flexible weekdays and weekends with all shifts available.

    Requirements

    • Must have at least 1 year of security experience.

    Responsibilities

    • Perform security patrols of designated areas on foot or in vehicle
    • Watch for irregular or unusual conditions that may create security concerns or safety hazards
    • Sound alarms or calls police or fire department in case of fire or presence of unauthorized persons
    • Warn violators of rule infractions, such as loitering, smoking, or carrying forbidden articles
    • Permit authorized persons to enter property and monitors entrances and exits
    • Observe departing personnel to protect against theft of company property and ensures that authorized removal of property is conducted within appropriate client requirements
    • Investigate and prepare reports on accidents, incidents, and suspicious activities; maintain written logs as required by the post
    • Aid customers, employees, and visitors in a courteous and professional manner
    • Make emergency notifications as necessary pursuant to site Post Orders

    Qualifications

    • Must possess a high school diploma or equivalent or 5 years of verifiable experience
    • Licensing requirements are subject to state and/or local laws and regulations and may be required prior to employment
    • Valid driver’s license if driving a company or customer-owned vehicle
    • 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
    • No prior experience required
    • Be at least 18 years of age, or higher if required by the state (21 years, if armed)
    • Reliability and ability to adapt to different post assignments
    • Be able to operate radio or telephone equipment and/or console monitors
    • Demonstrated ability to interact cordially and communicate with the public
    • Effective oral and written communication skills; able to write informatively, clearly, and accurately
    • Active listening and problem-solving skills
    • Assess and evaluate situations effectively; identify critical issues quickly and accurately
    • Mediate conflict with tact, diplomacy
    • Teamwork
    • Attention to detail

    Preferred qualifications

    • Ability to speak, read, and write in multiple languages (e.g., Spanish, Portuguese, French, Arabic)
    • Prior security, military, or law enforcement experience

    Benefits

    • Paid orientation and paid training

Similar jobs