Retail Shortage Control - Part 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: - About the role (introductory paragraph) - Responsibilities (broken into Command Presence, Knowledge and Communication, Support and Guidance) - Requirements/Qualifications (Experience and Responsibilities section) - Benefits (mentioned in the text) - Pay (explicitly stated) - Schedule (mentioned flexible schedule) The job title is "Shortage Control Associate" but I should not repeat it as a heading per instructions. I need to use

for section headings,

• for lists,

  for prose. I must remove boilerplate like EEO statement, application instructions, etc. The posting includes "Burlington Stores, Inc. is an equal opportunity employer committed to workplace diversity." That's boilerplate, remove. Also remove Job ID/Posting Number/Address/Zip Code/Position Type/Career Site Category/Position Category - these are metadata, fold into a short

  or drop. The instructions say "fold minor metadata into a short

  or drop it." I'll include location maybe in a short p. The pay is explicitly stated: "Base Pay: $14.75 per hour - $14.75 per hour" and later "Base Pay $14.75 - $14.75 per hour". So include Pay section. Schedule: "Candidates must be able to work a flexible schedule; including nights, weekends, and holidays as required." So include Schedule section. Benefits: "You will enjoy a competitive wage, flexible hours, and an associate discount. Part-time associates, based on hours worked, may be eligible for Burlington's benefits package which includes medical coverage and a 401(k) plan. Part-time associates may also be eligible for up to 4 hours of paid time off annually after one year of service, up to 8 paid holidays, and paid sick time in accordance with applicable law." That's substantive, include Benefits section. Now structure: 1. About the role: The first paragraph(s) describing the role. I'll put as

  under

  About the role

  . 2. Responsibilities: The three subsections: Command Presence, Knowledge and Communication, Support and Guidance. Each could be a sub-list under Responsibilities. Since the rule says use

  for section headings like Responsibilities, Requirements, etc. I'll make Responsibilities an

  and then maybe subheadings? But the rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't mention subheadings. I could make each of those three as separate

  ? But they are subsections of Responsibilities. The example list includes "Responsibilities" as a heading. I think I should have one

  Responsibilities

  and then use
  • for each duty, but the duties are grouped. Could do nested lists or separate lists with bold labels. However, the instruction: "Use
    • for any list of duties/requirements/benefits". So I can create a list for each group. Maybe use

      for each group? But the example headings are top-level sections. The posting has "Command Presence:", "Knowledge and Communication:", "Support and Guidance:" as subheadings. I could treat them as

      as well? The rule says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with three sub-lists, each introduced by a or something. But semantic HTML: could use

      but not allowed? The rule only mentions

      for section headings. It doesn't say we cannot use

      . But to be safe, I'll keep only

      for main sections. I'll make Responsibilities an

      and then use

      with
      • that include the category as bold text. Alternatively, I could make each category a separate

        but that might be too many thin sections. The posting has three categories with multiple bullet points each. That's substantive. I'll make them separate

        headings: Command Presence, Knowledge and Communication, Support and Guidance. But the example list includes "Responsibilities" as a heading, not subheadings. However, the rule says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's an example list, not exhaustive. I think it's okay to have subheadings as

        if they are major sections. But the posting's structure: "Command Presence:", "Knowledge and Communication:", "Support and Guidance:" are under "Experience and Responsibilities:"? Actually the text: "Command Presence: ... Knowledge and Communication: ... Support and Guidance: ... Experience and Responsibilities: ..." So "Experience and Responsibilities" seems to be the requirements/qualifications section. The three before are responsibilities. So I'll have: - About the role - Responsibilities (with three subsections as lists) - Requirements (or Qualifications) for the Experience and Responsibilities list - Benefits - Pay - Schedule Also there is a paragraph about "If you... are excited to deliver great values..." that's more about company culture, maybe include in About the role or a separate section? Could be part of About the role. Now, metadata: Location 01828 - Myrtle Beach, Address, Zip Code, Position Type, etc. I'll fold into a short

        at the end or beginning. Maybe a

        with "Location: Myrtle Beach, SC (1120 Seaboard Street, 29577). Position Type: Regular Part-Time." But the rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So I'll include a short

        with location and position type. Now, ensure no filler text. The pay is specific: $14.75 per hour. Benefits are specific. Schedule is specific. Now write HTML. Let's draft:

        About the role

        Join our team as a Shortage Control Associate and contribute to a secure shopping environment while delivering exceptional customer service! As a Shortage Control Associate (SCA), your role directly impacts the store's security and the overall shopping experience for our customers. By exhibiting command presence, knowledge of theft trends, and a positive impression of control, your presence at store entrances, exits, and high-risk areas will contribute to mitigating theft and creating a safe and enjoyable shopping environment. You will engage with our customers and associates in a manner consistent with our company core values by providing a confident, friendly, and energetic greeting with eye contact and a smile with every interaction. Your discipline, awareness of your surroundings, and commitment to maintaining safety and security standards will be critical as you monitor the entrance for the entire duration of every shift with a focus on reducing opportunities for theft, shoplifting, and other dishonest activities. Your confidence, positive attitude and expertise in store shortage reduction programs will positively influence behaviors and allow you to effectively build trust and respect amongst customers and associates. You will be a valuable partner to store and field leadership by identifying and reporting theft incidents and/or suspicious subject(s) to your Manager on Duty once identified.

        Responsibilities

        Command Presence

        ... but can't use h4? The rule didn't forbid h4, but says use

        for section headings. Might be okay to use h4 for subsections. However, to be safe, I'll use within list items. But the responsibilities are grouped. I'll create three separate lists each preceded by a

        Command Presence

        then

        . That's semantic enough. But the rule: "Use
        • for any list of duties/requirements/benefits, and

          for prose." So I can have a

          with bold label then a

          . That's fine. Let's do:

          Responsibilities

          Command Presence

          • Maintain a professional appearance at all times, wearing the designated dress standards, radio and earpiece
          • Stand positioned at the front of the store, remaining vigilant and aware of your surroundings
          • Greet every customer entering or exiting the store with a warm smile and a loud, friendly greeting, promoting a sense of control and security
          • Create a secure environment and reduce opportunities for theft

          Knowledge and Communication

          • Possess a knowledge mastery of top shortage areas and support programs aimed at theft reduction
          • Effectively communicate information about theft prevention during store rallies, collaborating with the Manager on Duty
          • Conduct bag and package checks on store and corporate associates, ensuring adherence to safety and security standards
          • Understand the role you play in keeping your store and assets safe and secure

          Support and Guidance

          • Provide support in training associates on shortage reduction programs and processes
          • Role-model safety as a top priority and address any unsafe practices promptly

          Requirements

          • 1+ years of experience in customer service, hospitality, retail, Asset Protection, Loss Prevention, or Operations is preferred
          • Ability to stand and walk for extended periods of time and to visually monitor store environment
          • Ability to maintain confidentiality is required
          • Ability to review, analyze and comprehend business trends
          • Ability to exhibit a positive demeanor, strong posture, and energetic greeting
          • Ability to work in a fast paced, high-pressure environment with detailed focus and disciplined decision making
          • Excellent communication with customers and co-workers
          • Excellent leadership skills that support fostering productive business relationships

          Benefits

          • Competitive wage
          • Flexible hours
          • Associate discount
          • Part-time associates (based on hours worked) may be eligible for medical coverage and a 401(k) plan
          • Part-time associates may be eligible for up to 4 hours of paid time off annually after one year of service
          • Up to 8 paid holidays
          • Paid sick time in accordance with applicable law
          • Training and development opportunities

          Pay

          Base pay: $14.75 per hour

          Schedule

          Flexible schedule required, including nights, weekends, and holidays as needed.

          Location

          Myrtle Beach, SC (1120 Seaboard Street, 29577). Position Type: Regular Part-Time.

          But the rule says "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it." I included Location as a heading? The example headings include "Schedule" but not "Location". However, location is not in the example list. But it's metadata. I'll fold into a short

          at the end without a heading. Maybe just a

          at the end. Also, the posting includes "We