Manager, Regional Security

We need to output HTML fragment with sections: Overview (maybe as

Overview?), Responsibilities, Qualifications, Benefits, Pay, maybe About AIT Worldwide? The instructions: use

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

• for any list of duties/requirements/benefits, and

  for prose. 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. 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. We need to decide which sections to include based on content. The posting includes: - Introduction (some fluff). Could be considered "Overview"? Actually there is an "Overview" heading later: "Overview The Manager, Regional Security is responsible for overseeing and managing security operations..." So we can have Overview section. - Responsibilities: a long list of duties. - Qualifications: includes Education, Experience, Knowledge, Skills, And Abilities. - Benefits: "What AIT Can Offer You" includes bonus eligibility, benefits list, vacation etc. - Pay: "The wage range for this position is $66,250.00-$99,370.00 and may vary based on geography as well as relative knowledge, skills, abilities, and experience." - About AIT Worldwide: description of company. - Possibly "Skills" could be part of Qualifications. We need to avoid duplicate lines. Also remove boilerplate like EEO statement, contact info for disability, etc. We need to preserve all substantive info. We need to use

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. We need to use

    for prose. We need to not repeat job title as heading. We need to not include Job ID etc. We need to output only HTML fragment. Let's extract content. Introduction paragraph: "Join us at AIT, where we believe every day presents an opportunity to make a global impact! We’re problem solvers, driven by our curiosity and creativity, in endless pursuit of solutions for our customers. Together, we champion the strength of our global teams. And, as trusted advisors, we go above and beyond, working together in a supportive and collaborative environment to ensure customer satisfaction. Through the company's continued growth, we challenge ourselves to be better, continuously learning and growing in our dynamic environment. Helping others is at the core of our culture, join us in finding fulfillment by giving back to our local communities as the united team that is AIT. Find out what our people deliver.® means when you come move the world with us! Hear directly from our teammates at AIT Worldwide Logistics and make us the next stop on your career journey." That's fluff but substantive? It's basically company culture intro. Could be part of Overview or maybe we can include as a short paragraph under Overview? The Overview heading later gives specific role description. The introduction could be considered part of "About AIT" but there is also a separate "About AIT Worldwide" later. The introduction is more generic. Might be considered boilerplate? It's not EEO but it's marketing fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This intro is not exactly boilerplate but could be considered fluff. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. The intro is substantive? It's describing company culture; maybe we keep it as part of Overview or a separate "About AIT" section? There's already an "About AIT Worldwide" later with more detail. The intro is somewhat redundant with that later section. Might be considered duplicated lines? Not exactly duplicate but similar. Safer to keep the later "About AIT Worldwide" and drop the intro? But we must preserve ALL substantive information; if we drop the intro, we lose some info about culture, problem solvers, etc. However the later About AIT Worldwide includes details about being a global freight forwarder, history, etc. The intro includes culture statements not covered later. So we should keep it. Perhaps we can include it as a short paragraph under Overview or as a separate "About AIT" section? The instructions list possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the company" but we can still use a heading like "About AIT Worldwide" as

    About AIT Worldwide

    if we want. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It's not exclusive; we can use other headings as needed, but they gave examples. Probably okay to use About AIT Worldwide. We need to avoid creating sections with filler text. So each section must have real specific content. Let's outline: - Overview: description of role from "Overview The Manager, Regional Security is responsible for overseeing and managing security operations, programs, and contractor compliance team within a specific geographic area, or region for a company or organization. This role will work ensure the safety and security of employees, facilities, vendors, agents, carriers and assets. Providing continuous support to AIT locations, field management domestically – internationally, stake holders and effectively implementing contracting/compliance/security programs and training." We can put that as

    . - Responsibilities: list of duties. We'll extract each bullet-like sentence. The responsibilities paragraph is a long run-on with many duties separated by periods. We need to split into list items. Let's parse: "Manage/lead the Contractor Compliance Team, to ensure proper security policies and procedures related to Contracting AIT Worldwide Service Providers are followed and executed. Maintain strong communications with internal and external customers related to ongoing efficiencies, updates, and changes within the security supply chain logistics. Manage, develop, and coordinate continued security assessments and documents updates Manage, maintain and develop continued efficiencies, oversee daily security operations, manage security teams, and coordinate incident response Manage and respond in a timely manner to security compliance and procedural questions from internal and external customers. Develop crisis management plans, respond to security incidents, and ensure compliance with regulations Oversee continued audit process of security service contracting and security compliance service providers. Managing physical security measures and conducting security audits. Create, draft, update, and implement Contracting & Compliance standard operating procedures based upon the needs of the organization and businesstraining employees on security matters, collaborating with other departments, and building relationships with external partners Manage/Maintain System Issues related to contracting, compliance, and settlements Effectively complete special projects as dictated by business needs Performs other duties as assigned Complies with all policies and standards" We need to clean up typos: "businesstraining" should be "business training". We'll keep as is but maybe fix minor? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Fixing a typo could be considered altering? Probably okay to keep as is; but we could keep the original text. However the original has no space: "businesstraining". We'll keep it exactly. We'll make each as

    . - Qualifications: includes Education, Experience, Knowledge, Skills, And Abilities. We can structure as maybe a

    with sub-items? But we can just list each qualification as
    • . However we need to preserve the structure: Education Bachelor's Degree in business or computer science required. Experience 5+ years relevant work experience in security. 7+ years global security preferred. Knowledge, Skills, And Abilities: list of abilities each with proficiency level (High, Medium). We'll keep them as list items. We could also have a

      Qualifications

      and then
      • Education...
      etc. - Benefits: "What AIT Can Offer You In addition to your base compensation, you may be eligible for a bonus based on achievement of business and/or individual performance metrics (dependent on position). Benefits offered include Medical, Prescription, Health Savings Account, Flexible Spending Accounts, Dental, Vision, Life, AD&D, Disability, Supplemental Health, Employee Support, Paid Parental Leave, Pet Insurance, 401(k) and Tuition Reimbursement. In addition, teammates may be eligible for up to 10 to 20 days of vacation (depending on tenure), 2 personal days, 1 floating holiday, 5 sick days, 5 volunteer hours, and 6 company holidays (plus Veterans Day for Veterans) annually." We'll make a

      Benefits

      and then a

      for the prose, maybe also a

      for the list of benefits? The instruction: Use
      • for any list of duties/requirements/benefits. So we should list benefits as
        • . However the benefits list is long; we can split into items. We also have bonus eligibility statement; that's not a list but prose. Could be a

          before the list. - Pay: wage range. We'll make

          Pay

          and

          The wage range for this position is $66,250.00-$99,370.00 and may vary based on geography as well as relative knowledge, skills, abilities, and experience.

          - About AIT Worldwide: description. We'll make

          About AIT Worldwide

          and

          ...

          We should also include the Introduction? Could be part of Overview or separate "About the role"? Actually "About the role" is not present; we have Overview. The introduction is more about company culture; maybe we can include it as a short paragraph under Overview before the role description? But the Overview heading already has role description. We could combine: Overview section includes both intro and role description. However the instruction: Prefer a few substantive sections over many thin ones. So we could have Overview containing the intro paragraph plus the role overview. That would be substantive. But we also have a separate "About AIT Worldwide" later; that is about company. So we could keep Overview as role overview only, and put the intro as part of "About AIT Worldwide"? But the intro is about culture, not just company description. However the About AIT Worldwide later includes description of what they do, history, etc. The intro includes culture statements not in that later section. Could we merge them? Possibly we could have About AIT Worldwide section include both the intro and the later description. That would be substantive. Thus we could have sections: Overview (role overview), Responsibilities, Qualifications, Benefits, Pay, About AIT Worldwide. We need to ensure we don't create sections with filler text. All have content. Now we need to output HTML fragment only. Let's craft. We'll start with

          Overview

          then

          ...

          Overview paragraph: combine introduction and role overview? Let's decide. Option: Overview includes the role overview only (the paragraph after "Overview"). The introduction could be placed before Overview as a

          without heading? But we need to use headings for sections; we could just have a leading

          for the intro, then

          Overview

          . That's okay; the instruction didn't forbid stray