PT Sales Supervisor: Set Active

We need to output HTML fragment with sections: About the role (but we already have About the Brand then About the Role). The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings. Preserve all substantive info. Remove boilerplate etc. We need to include sections only when posting has real specific content. The posting includes: About the Brand (maybe we keep? It's not a required heading but we can include as a section? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow the pattern. Probably we should include About the Brand as a heading? It's not in the list but could be considered a section. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can also use other headings like About the Brand. But they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can include About the Brand. We need to include Pay section because they gave hourly pay range. Benefits: they gave Leap Perks with medical, dental, vision, 401(k), PTO, employee discount, wardrobe allotment. So Benefits section. Schedule: they gave flexible availability including days, evenings, weekends, holidays. That's schedule info. So we can include Schedule. Responsibilities: we have "What You'll Do" with bullet points. That's responsibilities. Requirements: "Position Requirements" list. Qualifications: maybe same as requirements? Could combine. But we can have Requirements and Qualifications separate if distinct. The posting has "Position Requirements" list; no separate qualifications. So we can just have Requirements. Skills: maybe not separate; we can embed in Requirements. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include boilerplate like EEO etc. The Leap Perks includes diversity statement; that's boilerplate? It's about diversity and inclusion; might be considered boilerplate but it's part of benefits? It's more EEO. Probably we should remove that diversity statement as boilerplate. Also remove "Leap celebrates diversity..." etc. Also remove "AllOne Health Employee Assistance Program" maybe keep as benefit? It's a benefit. Keep. We need to preserve all substantive information. So keep medical, dental, vision benefits, 401(k), accrued PTO, employee discount and wardrobe allotment, bonus eligible. We need to format Pay: hourly pay range $20/hr – $22/hr. Also mention bonus eligible. Could be in Pay section. Schedule: flexible availability including days, evenings, weekends, holidays. Now produce HTML fragment. Structure:

  About the Brand

  ... brand description ...

  About the Role

  ... role description ...

  Responsibilities

  • Drive Sales Performance...
  ...
  But we need to break down responsibilities into bullet points as per "What You'll Do" sections: Drive Sales Performance, Deliver an Exceptional Customer Experience, Lead & Develop the Team, Lead Daily Store Operations. Each has sub-bullets. We could keep as nested lists? The instruction: use
  • for any list of duties/requirements/benefits. Could do top-level
    with each main duty as
    • and inside maybe
      for subpoints. That's okay. Similarly Requirements list. Benefits list. Schedule maybe as

      or

      . Since it's a list of availability, we can do
      . Pay: maybe

      . Let's extract text. About the Brand paragraph: "Hey! We’re SET. We’re here to simplify the way you get dressed. In an effort to be more effortless, we design athleisure that blurs the line between form and function. Whether you're getting active or actively chilling on the couch, our elevated essentials take you there. We’re a community first and a brand second. Seriously. Everything we create is with you in mind— from styles and colors, to what's to come and what's coming back. We believe open communication is key, because we’re at our best when you feel yours. We love to share what's going on BTS (behind the SET). Production planning, photoshoots, business day-to-day, what's up next, the good, the bad and the challenging. We're big on keeping it real and we'll always share the "why," because you deserve it." We keep that. About the Role: "We are seeking a passionate and results-driven Sales Supervisor to join our boutique, powered by the Leap Platform. This opportunity is ideal for a hands-on retail leader who thrives on the sales floor, develops teams, and creates exceptional customer experiences.As a key member of the leadership team, you will serve as the Leader on Duty, partnering with the Store Manager/General Manager to drive sales performance, lead daily operations, and ensure the team delivers an elevated in-store experience. When the Store Manager is not present, you will confidently oversee the business, ensuring sales goals are achieved, brand standards are maintained, and customers receive exceptional service." We keep that. Responsibilities: Under "What You'll Do" we have headings: Drive Sales Performance - Lead the team in achieving daily sales goals and key performance metrics through active coaching, floor leadership, and strong selling behaviors. - Monitor business performance throughout the day, identifying opportunities and adjusting priorities to maximize results. - Reinforce product knowledge, storytelling, and personalized selling techniques to elevate the customer experience. Deliver an Exceptional Customer Experience - Create meaningful customer connections through authentic engagement, product expertise, and personalized service. - Coach associates to deliver thoughtful recommendations and experiences that drive customer loyalty and repeat business. Lead & Develop the Team - Serve as a trusted leader on the sales floor by providing coaching, feedback, recognition, and ongoing support to develop a high-performing team. - Partner with store leadership to onboard new team members, reinforce training, and foster a culture of accountability and collaboration. Lead Daily Store Operations - Serve as Leader on Duty by overseeing daily store execution and ensuring the team is prepared to deliver an exceptional customer experience. - Execute brand standards across visual merchandising, inventory management, shipment processing, and daily operations while maintaining compliance with company policies. - Support store events, activations, new store openings, and market initiatives as needed. Key Performance Indicators (KPIs) maybe could be considered responsibilities? But we could treat as separate section? The instruction says include a section only when posting has real specific content. KPIs are specific. Could be a section "Key Performance Indicators". But they didn't list KPI as example heading; but we could still use

      . However they said use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That implies we should stick to those headings. KPI could be part of Responsibilities. Safer to not create extra heading. We'll incorporate KPI bullets under Responsibilities maybe as a sublist? But we can just keep them as part of Responsibilities list. We could add a separate

      Key Performance Indicators

      but that deviates from instruction. I'd avoid. Thus Responsibilities will include all bullet points under those headings. Now Requirements list: "Position Requirements 1–3 years of retail leadership or supervisory experience in boutique, specialty, premium, or customer-focused retail environments. Demonstrated ability to lead a team, coach selling behaviors, and drive sales results in a fast-paced environment. Strong customer-focused selling skills with the ability to build relationships, provide product expertise, and create memorable experiences. Strong communication skills with the ability to provide feedback, motivate others, and build positive team relationships. Oversees daily sales floor standards, including organization, replenishment, cleanliness, and overall store presentation. Experience with retail technology, including Shopify, Endear CRM, Slack, and Google Workspace preferred. Flexible availability, including days, evenings, weekends, and holidays. Ability to actively lead on the sales floor, including standing, walking, climbing ladders, and lifting up to 50 lbs. Must be at least 18 years of age." Note flexible availability also appears in Schedule; we might duplicate. We'll keep in Requirements but also maybe Schedule section. To avoid duplication, we could move flexible availability to Schedule and remove from Requirements. But the instruction says preserve ALL substantive information; we can keep it in both places? Might be duplication but okay. Better to keep in Requirements and also have Schedule section referencing flexible availability. Could be duplicate but still preserving. However they said remove duplicated lines. So we should not duplicate identical lines. So we should place flexible availability only once. Where does it belong? It's a requirement but also schedule. Probably better to put under Schedule section and remove from Requirements. But then we lose that requirement info? It's still there under Schedule. So we keep it under Schedule. Thus Requirements list excludes flexible availability line. Now Benefits: from Leap Perks: "Bonus eligible Medical, dental, and vision benefits (must average 32+ hours per week) AllOne Health Employee Assistance Program 401(k) Accrued PTO:Full-time hourly employees can accrue up to two weeks (80 hours) of paid time off annually, excluding restricted dates during busy retail seasons, with manager approval. Part-time hourly employees accrue PTO in accordance with local laws. Employee discount and wardrobe allotment for participating Leap brands" We should remove the diversity statement at end. Now Pay: "Hourly Pay Range: $20/hr – $22/hr. Compensation will be determined based on the candidate's experience, skills, competencies, and qualifications. This role is bonus eligible." We already have bonus eligible in Benefits; but we can mention in Pay as well. To avoid duplication, we could keep bonus eligible only in Benefits. But Pay section should contain pay range. We'll mention compensation determination. Now Schedule: "Flexible availability, including days, evenings, weekends, and holidays." Now produce HTML. We need to wrap each section in

      heading then content. For lists, use

      • . For prose,

        . Let's craft. About the Brand:

        ...

        About the Role:

        ...

        Responsibilities:

        Responsibilities

        then
        with each main duty as
        • containing maybe sub
          . We'll do nested. Requirements:

          Requirements

          each line. Benefits:

          Benefits

          each line. Pay:

          Pay

          ...

          Schedule:

          Schedule

          Flexible availability, including days, evenings, weekends, and holidays.

          Check for any leftover boilerplate: The Leap Perks includes "Leap celebrates diversity and is committed to fostering an inclusive workplace..." we removed. Also remove "AllOne Health Employee Assistance Program" we kept. Check for any duplicated lines: we removed flexible availability from Requirements. Now ensure we didn't miss any substantive info: The "About the Role" includes "powered by the Leap Platform". Keep. The "What You'll Do" includes all bullet points. The "Key Performance Indicators" we omitted; but its content is similar to responsibilities; we might lose some nuance. However the KPI section repeats similar points but maybe adds nuance: "Sales Leadership & Business Performance: Leads the team to achieve daily sales goals and key performance metrics through effective coaching, floor leadership, and commercial execution." etc. That