Seasonal Educator | River MarketPlace

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" description, "Job Summary", "Key Responsibilities Of The Job", "Key Skills & Core Values You Bring", "Job Requirements", "Job Assets (i.e., nice to have; not required)", "Compensation & Benefits Package". Also maybe "Eligibility", "Availability", "Willingness Requirements". But we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can adapt headings to match content. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings if we have content. We must not repeat job title as heading. We must not put Job ID etc. We must include a section only when posting has real specific content. We must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Compensation & Benefits Package with base pay range, target bonus, benefits list. So we can have sections: About the role (maybe "Who We Are" and "Job Summary" combined?), Responsibilities (Key Responsibilities), Requirements (Job Requirements + Eligibility etc?), Skills (Key Skills & Core Values You Bring), Benefits (Compensation & Benefits Package). Pay maybe part of Benefits? But we could have Pay section separate if we want. However instruction: Prefer a few substantive sections over many thin ones. So we could combine Pay and Benefits into one Benefits section. But they said use headings like Benefits, Pay, Schedule. We could have a Benefits section that includes pay and benefits. Or we could have Pay and Benefits separate if we have content. Since we have both pay and benefits details, we could split: Pay section with base pay range and target bonus; Benefits section with extended health, dental, mental health, PTO, savings, employee discount, fitness classes, etc. That seems reasonable. We also need to include Schedule? The posting mentions "Willing to work a flexible schedule including evenings, weekends, and holidays." That's schedule info. So we could have a Schedule section. We also need Requirements section: eligibility, availability, willingness requirements, maybe also job assets? Job assets are nice-to-have, could be under Qualifications? But we have Qualifications heading maybe for required qualifications. Could treat Job Requirements as Requirements, and Job Assets as Qualifications (nice to have). Or we could have Requirements (required) and Qualifications (nice to have). Let's map: - About the role: combine "Who We Are" and "Job Summary". - Responsibilities: "Key Responsibilities Of The Job". - Requirements: eligibility, availability, willingness requirements (must be legally authorized, 18+, proof of right to work, flexible schedule, willingness to work in bright lights/loud music, move boxes up to 30 lbs, work as team/independently). Also maybe "Must be legally authorized to work..." etc. - Qualifications: Job Assets (nice to have): high school diploma/GED/equivalent. - Skills: "Key Skills & Core Values You Bring". - Pay: base pay range and target bonus. - Benefits: extended health/dental/mental health, paid time off, savings/retirement plan matching, employee discount, fitness & yoga classes, parenthood top-up, development courses, people networks/mentorship/leadership series. - Schedule: maybe we already covered in Requirements (flexible schedule). But we could still have a Schedule section detailing willingness to work flexible schedule including evenings, weekends, holidays. We must not create sections with filler like "commensurate with experience". We have actual content. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "In keeping with our mission, please connect with us at accommodations@lululemon.com if you have questions..." That's like an accommodation request; not exactly boilerplate but maybe considered application instructions? It's not about applying; it's about accommodation request. Might be okay to keep? The instruction: remove application instructions. That line is about accommodation request, not exactly applying. Might keep? Safer to remove? It's not a core job description; it's about accommodations. Could be considered part of Requirements? But it's not a requirement. I'd remove it. Also remove duplicated lines: there may be none. Now produce HTML fragment: use

for each section heading, then content in

or

• . For lists, use
  • . For prose, use

    . We need to preserve all substantive information. Let's extract details. Who We Are: "lululemon is an innovative performance apparel company for yoga, running, training, and other athletic pursuits. Setting the bar in technical fabrics and functional design, we create transformational products and experiences that support people in moving, growing, connecting, and being well. We owe our success to our innovative product, emphasis on stores, commitment to our people, and the incredible connections we make in every community we're in. As a company, we focus on creating positive change to build a healthier, thriving future. In particular, that includes creating an equitable, inclusive and growth-focused environment for our people." Job Summary: "The Educator role is the foundation of our success as an organization. Educators are experts in creating world-class customer service, or guest experience, in our retail stores. They are responsible for engaging and connecting with our guests, sharing top-quality product education, and speaking authentically about our community and culture." Combine these into About the role section. Responsibilities: list bullet points from "Key Responsibilities Of The Job". Let's extract each bullet: - Guest (i.e., Customer) Experience - Interact with guests to ensure a great guest experience in a manner that values guests’ time. - Assess guests’ needs to provide customized, effective purchase and return solutions and support. - Provide technical product education by articulating the value and benefit of the product. - Facilitate a seamless end-to-end guest experience by conducting accurate and timely guest transactions and executing market-relevant omnichannel programs (e.g., buy online/pickup in store, phone sales, and ship from store options) according to company standards. - Move dynamically on the floor to continuously engage with guests and attend to guest or store needs. - Receive guest feedback and partner with store leadership to take appropriate action and “make it right” for guests. - Working With Others - Contribute to a respectful and inclusive team environment by welcoming and celebrating differences to ensure a supportive and engaging experience for all team members and guests. - Establish supportive and productive relationships with all team members. - Collaborate with team members to ensure optimal guest experience and support store operations. - Operations - Perform product presentation tasks (e.g., put items back in place, restock or add depleted items to the floor from inventory, destock or relocate items) according to company standards. - Use in-store technology to support store operations and provide positive guest experiences. - Perform cleaning tasks as needed throughout the shift to maintain the luxury environment of the store. - Understand and adhere to people safety policies and procedures to maintain a safe work environment. - Perform work in accordance with applicable policies, procedures, and laws or regulations. We'll put these as

    • under Responsibilities. Skills: "Key Skills & Core Values You Bring" list: - Inclusion & Diversity: Creates/supports an inclusive environment that values/celebrates differences - Integrity/Honesty: Behaves in an honest, fair, and ethical manner - Guest Experience: Enjoys working and connecting with, understanding, and helping guests - Personal Responsibility: Accepts responsibility/accountability for actions; is dependable - Self-Awareness: Is aware of how words or actions may be perceived by or affect others - Collaboration and Teamwork: Works productively with others to achieve goals; seeks diverse perspectives - Enthusiasm: Is enthusiastic about one’s own work; looks for ways to make work fun and engaging We'll list each as
    • . Requirements: includes eligibility, availability, willingness requirements. Eligibility: - Must be legally authorized to work in the country in which the store is located - Must be 18 years of age or older - Must have proof of the Right to Work and evidence relating to associated local legislative requirements (EMEA only) Availability: - Willing to work a flexible schedule including evenings, weekends, and holidays Other Willingness Requirements: - Willing to work in an environment with bright lights and loud music - Willing to move through a store for most of a shift to help guests and accomplish work - Willing to move boxes weighing up to 30 lbs (13.6 kg) - Willing to work as part of a team and also complete some work independently We'll combine these into Requirements section as list. Qualifications (nice to have): Job Assets: - Education: High school diploma, GED, or equivalent Pay: - Base Pay Range: $18.00 - $20.71/hour, subject to minimum wage in the location - Target Bonus: $2.00/hour - Total Target Base Pay Range: $20.00 - $22.71/hour - Note: compensation offerings grounded in pay-for-performance philosophy; base pay based on market location and may vary depending on job-related knowledge, skills, experience, internal equity. - Employees eligible for competitive bonus program, subject to program eligibility requirements. We'll include these as prose or list. Benefits: - Extended health and dental benefits, and mental health plans - Paid time off - Savings and retirement plan matching - Generous employee discount - Fitness & yoga classes - Parenthood top-up - Extensive catalog of development course offerings - People networks, mentorship programs, and leadership series (to name a few) - Note: incentive programs, benefits, perks have eligibility requirements; company reserves right to alter. Schedule: - Willing to work a flexible schedule including evenings, weekends, and holidays (already in Requirements but we can also put here). To avoid duplication, maybe we put schedule info only in Schedule section and not duplicate in Requirements. But Requirements already includes availability. However we can keep both but avoid duplication? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's in original? The original has availability under "Availability Willing to work a flexible schedule including evenings, weekends, and holidays". Also under "Other Willingness Requirements" there is no schedule mention besides that. So we could keep it in Requirements and not have separate Schedule section. But we need a Schedule section only if posting has real specific content for it. It does have that content (flexible schedule). So we could have a Schedule section with that detail. However then we would have the same info in two places (Requirements and Schedule). That's duplication but it's still preserving info. Might be okay but could be considered redundant. The instruction: Prefer a few substantive sections over many thin ones. Having both Requirements and Schedule may be thin. Better to put schedule info under Requirements (or Availability) and not create a separate Schedule section. Since they gave example headings including Schedule, but we can omit if we think it's thin. However we have Availability content; we could treat that as part of Requirements. So we won't create a Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Benefits. Now produce HTML. We need to wrap each section:

      Section Title

      then either

      or

      • . For multiple paragraphs, we can use

        for each. Let's craft. About the role: combine Who We Are and Job Summary into maybe two paragraphs. Responsibilities: we can have a

        with nested? We'll just flat list. Requirements: list. Qualifications: list (maybe one item). Skills: list. Pay: maybe a
        with details