Security Operations Agent

The user wants me to convert this 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: - About the role (Summary) - Responsibilities (Essential Duties & Responsibilities) - Requirements (Knowledge Of, Skill In, Ability To) - Qualifications (Minimum Qualifications, Preferred Qualifications) - Working Conditions (Working Conditions And Physical Demands) - General Information (General Information) - Conditions of Employment (CONDITIONS OF EMPLOYMENT) - Benefits (Benefits) - Pay (Salary mentioned: $25.00 - $27.57 Commensurate with Experience, plus shift differential) - Schedule (shift information mentioned) I need to use

for section headings,

• for lists,

  for prose. Don't repeat job title. Don't include Job ID. Remove boilerplate like EEO, application instructions, etc. Let me structure: 1. About the role - from Summary 2. Responsibilities - from Essential Duties & Responsibilities 3. Requirements - combine Knowledge Of, Skill In, Ability To (these are requirements) 4. Qualifications - Minimum and Preferred 5. Working Conditions - Working Conditions And Physical Demands 6. General Information - General Information 7. Conditions of Employment - CONDITIONS OF EMPLOYMENT 8. Benefits - Benefits (but note it says "Click here to learn more" - but there is some info: comprehensive benefits package, drug and alcohol-free workplace) 9. Pay - Salary range and shift differential 10. Schedule - shift info But the rules say: include a section ONLY when the posting has real, specific content for it. Never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary range and shift differential, so Pay section is appropriate. Schedule info is in General Information and Summary. Benefits section has some content. Also, remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove "How To Apply" section, EEO statement, etc. Now, I need to output ONLY the HTML fragment, no /, no markdown code fences. Let me write the HTML. I'll start with

  About the role

  then

  for the summary. Then

  Responsibilities

  with
  • for each duty. Then

    Requirements

    with subsections? But the rules say use

    for section headings. Could use

    for Requirements and then maybe

    ? But the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So I should use

    for each major section. For sub-sections like Knowledge, Skills, Abilities, I could either make them separate

    sections or combine under Requirements. The example includes "Skills" as a possible heading. But the posting has "Knowledge Of", "Skill In", "Ability To". I think I'll make them separate

    sections: Knowledge, Skills, Abilities. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe combine into one Requirements section with lists. Let me see: The posting has three distinct lists: Knowledge Of, Skill In, Ability To. They are all requirements. I'll create a Requirements section with three sub-lists, but using

    for each? The instruction says use

    for section headings. It doesn't forbid multiple

    s. But "Prefer a few substantive sections over many thin ones." So maybe one Requirements section with three

    lists, each preceded by a or

    ? But the instruction says use

    for section headings. It doesn't mention

    . I think I should use

    for each major section. The example includes "Skills" as a possible heading. So I could have Knowledge, Skills, Abilities as separate

    sections. But they are thin? Each has several items. Might be okay. Alternatively, I could have a single Requirements section with three subsections using

    but the instruction doesn't mention

    . It says "use

    for section headings". It doesn't say you can't use other headings, but to be safe, I'll use

    for each major section. I'll create: - About the role - Responsibilities - Knowledge - Skills - Abilities - Qualifications - Working Conditions - General Information - Conditions of Employment - Pay - Schedule - Benefits But that's many sections. Some are thin. Let's evaluate. Knowledge: list of 3 items (knowledge of 49 CFR, aviation radio, Microsoft apps). Skills: 2 items (verbal communication, written communication, organize data, interpersonal skills). Actually "Skill In" lists: communicate verbally, communicate in writing, organize data, interpersonal skills. That's 4. Abilities: many items (15+). So Abilities is substantial. Knowledge and Skills are smaller. Could combine Knowledge and Skills into one section? But they are distinct. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine Knowledge, Skills, Abilities into one "Requirements" section with three lists. But then how to label each list? Could use headings inside the section. That's allowed because we can use

    for prose and

    • for lists. We can have a

      Knowledge

      then
      . That's fine. Similarly, Qualifications has Minimum and Preferred. Could be one Qualifications section with two lists. Working Conditions and Physical Demands is one section. General Information is another. Conditions of Employment is another. Pay: salary range and shift differential. Schedule: shift info (assigned shifts, holidays, overtime, bid process, etc.) Benefits: comprehensive benefits package, drug-free workplace. Now, I need to remove boilerplate: "Welcome to the City of Charlotte..." mission statement, guiding principles? That's part of the summary? The summary includes "The work of a Security Operations Agent involves..." The preceding paragraphs are about the city. Should I include that? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The city description is substantive? It's about the employer. Could be part of About the role. But the page already shows the job title, and the department is Aviation Department. The city description is generic. I'll include a brief paragraph about the city in About the role. Also, "Department: Aviation Department Salary: $25.00 - $27.57 Commensurate with Experience" - that's metadata. I'll put salary in Pay section, department maybe in About the role. Now, let's write the HTML. I'll start with

      About the role

      Department: Aviation Department. The City of Charlotte is America’s Queen City, opening her arms to a diverse and inclusive community of residents, businesses and visitors alike. Here you will find a safe, family-oriented city where people work together to help everyone thrive. The mission of the City of Charlotte is to deliver quality public services and promote the safety, health, and quality of life for all residents.

      The work of a Security Operations Agent involves monitoring security access points (vehicle gates, doors, etc.), conducting inspections, and controlling vehicular and pedestrian access at Charlotte Douglas International Airport. Provide direction and information to the public in a tactful and courteous manner aligned with the airport’s Customer Service Philosophy. Act without direct supervision using independent judgment and discretion in accordance with departmental, local, state and federal rules, regulations, laws, ordinances and standard operating procedures. This is an unarmed uniformed position. This position requires availability to work any assigned shift. If assigned to a 2nd or 3rd shift, a 2.5% shift differential will be added to the base hourly rate.

      Then

      Responsibilities

      • Interpret and adhere to Federal regulations, procedures, and instructions to ensure the safety of persons and security of airport property.
      • Staff security access points (doors, vehicle gates, etc.), monitor activity, and conduct inspections of persons, property, and vehicles ensuring that the entry of vehicles, drivers and passengers meet airport security clearance requirements.
      • Maintain situational awareness and notify applicable resources to potential hazards.
      • Assess situations quickly, objectively, determine the proper course of action, and act decisively using independent judgment within established rules, regulations, and procedures.
      • Communicate effectively; operate a variety of communications equipment; transmit and receive emergency and non-emergency information; maintain logs and records.
      • Respond to airport emergencies and incidents in accordance with the National Incident Management System (NIMS), Airport Emergency Plan, Airport Security Plan, and other plans, policies, procedures, and regulations governing emergency response.
      • Provide security services during special details and events.
      • Prepare and maintain logs, records, and reports.
      • Aid the airlines, tenants, traveling public and other employees as needed.
      • Provide escorts to authorized visitors and contractors as necessary.
      Then

      Requirements

      Knowledge

      • Thorough knowledge of 49 CFR Part 1542, Airport Security Program, CLT Security Standards, Security Operations Standard Operating Procedures, TSA issued security directives, national amendments, and information circulars related to airport security, or the ability to obtain such knowledge within 30 days of hire.
      • Knowledge of aviation radio procedures/phraseology and ability to navigate on airport non-movement areas and movement areas or can obtain such knowledge within 30 days of hire.
      • Knowledge of Microsoft applications (Word, Outlook, Excel, PowerPoint, Teams, SharePoint, One Drive, etc.), WorkDay, E-Builder, and other computer-based applications or the ability to obtain such knowledge within 30 days.

      Skills

      • Communicate clearly and effectively verbally in person, over telephone and two-way radio.
      • Communicate clearly and effectively in writing.
      • Effectively organize data and prioritize resources during routine and special operations.
      • Strong interpersonal skills and the ability to foster effective working relationships with numerous internal and external airport stakeholders.

      Abilities

      • Work in an airport environment which includes the non-movement of the airfield.
      • Demonstrate strong situational awareness and be able to work in a fast-paced airport operating environment.
      • Recognize potential threats and respond quickly and calmly under emergency situations.
      • Act without direct supervision using independent judgment and discretion in emergency situations in accordance with departmental policies, procedures, rules, regulations, laws, and ordinances.
      • Deal courteously and firmly with the traveling public, airport employees/workers, airport stakeholders and those seeking access to restricted areas.
      • Work independently or as part of a team.
      • Represent the airport in a professional, positive manner and provide exceptional customer service to the traveling public, tenants, co-workers, and others.
      • Establish and maintain effective working relationships with co-workers, other agencies, tenants, employees and the public, representing CLT in a professional, positive manner.
      • Communicate clearly and effectively with diverse populations.
      • Effectively communicate in writing, complete paperwork, and generate reports.
      • Be clearly understood over radio and phone communications.
      • Respond calmly and effectively in emergency and stressful situations.