Shift Supervisor - Full Time

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc as headings; can fold minor metadata into short

or drop it. Remove boilerplate like EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Intro paragraph: "Join Trulieve – Where Passion Meets Purpose If you're interested in being part of one of the nation's fastest-growing industries, Trulieve may be the perfect place for you. We are proud to be recognized on TIME's America's Best Companies 2026 List, an honor awarded to top-performing U.S. organizations based on employee satisfaction, financial strength, and sustainability transparency. Trulieve was one of only two cannabis companies to receive this distinction. If you have passion for helping others and want to make a meaningful impact through your work, this may be the role for you. At Trulieve, we strive to bring our patients the relief they need in products they can trust. Our plants are hand-grown in carefully controlled environments designed to minimize unwanted chemicals and pests, keeping the cultivation process as natural as possible every step of the way. To learn more about Trulieve and our mission, please visit www.trulieve.com" - Then metadata: Requisition ID: 21293 Remote Work Available: No Job Title: Shift Supervisor - Full Time Department: Retail Reports To: General Manager FLSA Status: Regular Non-Exempt Salary: $17.00 an hour - Role Summary: paragraph. - Key Duties And Responsibilities: bullet list (but not bullet in text; each line starts with a dash? Actually each line is a sentence starting with a verb). We'll need to put in

• . - Skills And Qualifications: bullet list. - Additional Minimum Qualifications: bullet list. - Physical Requirements: bullet list. - Work Schedule: paragraph. - Then "Equal Opportunity Employer ..." boilerplate to remove. - Also "Salary will be commensurate with experience." This is filler; we should not create Pay section if only says commensurate with experience (no specific number). However we have Salary: $17.00 an hour from metadata. So we have specific pay. So we can include Pay section with that. - Benefits: "A comprehensive benefits package including paid time off is offered with this position." That's specific enough? It mentions comprehensive benefits package including paid time off. That's substantive. So we can include Benefits section. - Schedule: "Up to 40 hours weekly with flexible hours depending on store needs. Must be available to work evenings, weekends, and holidays." That's specific. So include Schedule. - About the role: maybe the Role Summary paragraph qualifies as About the role. Could also include intro paragraph about company? But we need sections only when posting has real specific content. The Role Summary is specific. So we can have About the role (or Role Summary). Use heading About the role. - Responsibilities: Key Duties And Responsibilities. - Requirements: maybe Additional Minimum Qualifications? Or Skills And Qualifications? The spec says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. We have: - About the role: Role Summary paragraph. - Responsibilities: Key Duties And Responsibilities. - Requirements: maybe Additional Minimum Qualifications (must possess driver's license, background checks, age, etc.) Could also include some from Skills And Qualifications? But we have separate Skills and Qualifications headings. So we need to split: Skills And Qualifications -> Skills heading? Actually we have both Skills and Qualifications headings separate. The posting has "Skills And Qualifications" and "Additional Minimum Qualifications". We could treat "Skills And Qualifications" as Skills heading, and "Additional Minimum Qualifications" as Qualifications heading. Or vice versa. Let's decide: Skills: interpersonal skills, communication, cash handling, etc. Qualifications: high school diploma, prior management experience, etc. Actually the posting lists under Skills And Qualifications: High School Diploma required, Prior management experience..., Must have prior cash handling experience, Strong interpersonal skills..., Able to communicate..., Ability to interact... So that's a mix of qualifications and skills. Then Additional Minimum Qualifications includes driver's license, background checks, age, etc. We need to follow the instruction: Use headings Skills and Qualifications separately. So we need to decide what goes where. Probably Skills: interpersonal skills, communication, cash handling, etc. Qualifications: education, experience, etc. Additional Minimum Qualifications could also go under Qualifications. Thus: - Skills: Strong interpersonal skills and professionalism to communicate..., Able to communicate in conversational English..., Ability to interact with customers and team members respectfully and politely. - Qualifications: High School Diploma required, Prior management experience..., Must have prior cash handling experience, Must possess a valid driver’s license..., Must be able to pass level 1 and level 2 background check, Must be at least 21 years of age, Must function independently..., Must be able to relate to and work with patrons..., etc. But we also have Physical Requirements separate; not in the list of headings but we could include as a separate section? The allowed headings list does not include Physical Requirements. However we must preserve all substantive info. We could incorporate Physical Requirements under Responsibilities or maybe under a separate heading not listed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should use those headings. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should only use those headings; we shouldn't add other headings like Physical Requirements. But we need to preserve that info. Perhaps we can fold Physical Requirements into Responsibilities or Requirements? Could be under Responsibilities as part of duties? Or under Requirements as physical requirements. The spec 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 use those for section headings. It might be okay to add other headings if needed, but better to stick to those. We could put Physical Requirements under Responsibilities as a bullet list? But that might misrepresent. However we can include a

  for Physical Requirements if we consider it a section; but the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not an exhaustive list. So we can add Physical Requirements heading if we want. But to be safe, maybe we incorporate it under Responsibilities or Requirements. I'd put under Responsibilities as "Physical Requirements" as a sub-list? But we need to keep structure simple: just

  • . Could add a heading Physical Responsibilities? Not ideal. Better to follow the instruction: Use those headings. So we need to map all content into those categories. Physical Requirements could go under Requirements (as they are job requirements). So we can include physical requirements under Requirements heading. Thus: - About the role: Role Summary paragraph. - Responsibilities: Key Duties And Responsibilities. - Requirements: Additional Minimum Qualifications + Physical Requirements (maybe also some from Skills And Qualifications that are more qualification-like). But we also have Qualifications heading separate. So we need to split. Let's define: - Qualifications: Education/experience requirements: High School Diploma required, Prior management experience..., Must have prior cash handling experience. - Skills: Interpersonal skills, communication abilities, ability to interact respectfully. - Requirements: Additional Minimum Qualifications (driver's license, background checks, age, etc.) + Physical Requirements. That seems logical. Now Benefits: "A comprehensive benefits package including paid time off is offered with this position." Pay: Salary: $17.00 an hour. Schedule: Up to 40 hours weekly with flexible hours depending on store needs. Must be available to work evenings, weekends, and holidays. Now we need to output HTML fragment only, no markdown. We'll produce:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Qualifications

    • High School Diploma required
    • Prior management experience, preferably in retail and/or customer service area is a plus
    • Must have prior cash handling experience

    Skills

    • Strong interpersonal skills and professionalism to communicate with all levels of management and staff; ability to uphold a strict level of confidentiality and discretion
    • Able to communicate in conversational English to work effectively with customers and team members, operate electronic equipment (computer, scanner, printer, etc.), comprehend safety procedures, and utilize telecommunication devices
    • Ability to interact with customers and team members respectfully and politely

    Requirements

    • Must possess a valid driver’s license and pass a MVR background check (delivery locations only)
    • Must be able to pass a level 1 and level 2 background check
    • Must be at least 21 years of age
    • Must function independently, and have flexibility, personal integrity, and the ability to work effectively with residents, personnel, and support agencies
    • Must be able to relate to and work with patrons of different ages, abilities, and patrons that at times are experiencing emotional distress, or displaying a hostile attitude
    • While performing the duties of this job, the employee is: Constantly required to move/traverse throughout entire facility, including tight spaces; accurately communicate and exchange sensitive information and ideas with others, including members of the public; observe/inspect details at varying ranges; operate computing devices; Frequently required to manipulate objects of varying sizes and weights (e.g., products, packaging, tools, office machinery): push/pull objects up to 50lbs; lift/carry/position objects up to 50 lbs.; ascend/descend stool/ladder/steps; position self and/or objects at floor level (e.g., crouch, stoop, kneel, crawl); Must have visual and auditory acuity with or without job aids to perform all functions of the position; Occasionally required to remain in a seated position
    But the physical requirements paragraph is long; we could split into multiple
  • for readability but it's okay as one. We need to ensure we didn't miss any substantive info: The intro paragraph about company mission etc. Should we include that? It's not under any heading but could be part of About the role? The About the role currently only has Role Summary. Could we add the introductory paragraph as part of About the role? The instruction: "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." The intro paragraph is not minor metadata; it's about company. Could be part of About the role. However the Role Summary already covers responsibilities. The intro paragraph is more about company. Might be okay to include as a separate

    before any headings? The instruction says output ONLY the HTML fragment; we can include a

    for introductory content before headings. It didn't forbid that. It said use

    for section headings (e.g...). It didn't say we cannot have other

    outside sections. So we can include an introductory paragraph about Trulieve before the sections. Thus we can start with a <