Product Operations Lead | Rehoboth Beach Pop Up Outlet ( 7 Month Contract)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all content must be preserved, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". So we need to parse the posting. Let's extract sections: - About the role / Who We Are: The "Who We Are" paragraph about lululemon. Also maybe "Job Summary". Could combine as "About the role". Provide prose. - Responsibilities: "Core Responsibilities Of The Job" bullet list. - Requirements: "Job Requirements" includes Eligibility, Schedule/Availability, Experience, Job Assets (nice to have). Also "What We Look For" includes competencies (Inclusion & Diversity etc). Those could be under Skills or Qualifications. - Qualifications: maybe "Job Assets" and "What We Look For" could be qualifications/skills. - Skills: The list of competencies (Inclusion & Diversity, Integrity, Adaptability/Agility, Leadership, Collaboration and Teamwork, Decision Making/Problem Solving, Planning and Organizing, Interactive Communication). Also maybe "Work Context" could be under Skills? But it's more about environment. - Benefits: "Compensation & Benefits Package" includes base pay range, target bonus, total target base pay range, plus description of compensation offerings, bonus program, equity offerings, etc. Also list of benefits: extended health and dental benefits, 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, leadership series. Also note about incentive programs eligibility. - Pay: Could be separate section for Pay, but we already have compensation details. The instruction says: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits into one "Compensation & Benefits" section. However they have separate headings possible: Pay, Benefits, Schedule. But we need to include a section only when posting has real specific content. The posting includes Pay details (base pay range, target bonus, total target base pay range). It also includes Benefits details. So we could have two sections: Pay and Benefits, or combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one "Compensation & Benefits" section. But they gave headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include only those with content. We have content for About the role, Responsibilities, Requirements (eligibility, schedule, experience, job assets), Qualifications (maybe job assets?), Skills (the competencies list), Benefits, Pay, Schedule (schedule/availability). So we could include all. But we must avoid filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID. We must remove duplicated lines. There's some duplication? Not obvious. We need to format: Use

  for section headings. Use

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

    for prose. Thus each section:

    About the role

    ...

    For Responsibilities:

    Responsibilities

    • ... each bullet. Similarly for Requirements: maybe break into sub-sections? But we can just list items as
      • . However there are subheadings like Eligibility, Schedule/Availability, Experience, Job Assets. Could we keep them as part of list items? Might be okay. But we could also make subheadings using

        ? Not allowed; only headings allowed are

        for section headings. So we cannot use

        . So we need to embed subheadings within

        or

        ? Probably we can keep them as plain text within

        or

        . The instruction: Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those specific headings. So we cannot add other headings. So we need to put all content under those headings, using

        and

        • . So for Requirements we can have a
          with items that include the eligibility, schedule, experience, job assets. Similarly for Qualifications we can have list of qualifications (maybe education, experience, etc). For Skills we list the competencies. For Benefits we list benefits. For Pay we list pay details. For Schedule we list schedule details. But note that Schedule/Availability appears also under Requirements. However we have a separate Schedule section. To avoid duplication, we could put schedule info only under Schedule section, not under Requirements. But the posting includes schedule info under Requirements. We need to preserve ALL substantive information. So we need to include schedule info somewhere. If we make a Schedule section, we can put schedule info there, and not duplicate elsewhere. But we must not lose the schedule info from Requirements. We could keep schedule info only under Schedule section and omit from Requirements. That would still preserve the info (just moved). That's acceptable as long as we don't lose info. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Moving it is okay as long as we keep it. So we can put schedule info under Schedule section. Similarly, Pay info appears under Compensation & Benefits Package. We'll put under Pay section. Benefits info also under Compensation & Benefits Package; we can put under Benefits section. Now we need to decide what goes under Requirements: Eligibility, Experience, Job Assets (nice to have). Also maybe "Must be legally authorized to work..." etc. Qualifications: maybe education? Actually Job Assets includes education: "High school diploma/GED/equivalent, or above". That's a qualification. Also "What We Look For" includes competencies, but those are more Skills. So Qualifications could be education and maybe experience? But experience is also under Requirements. We'll keep experience under Requirements. Thus: - About the role: combine Who We Are and Job Summary. - Responsibilities: list of core responsibilities. - Requirements: list of eligibility, experience, job assets (nice to have). Could also include "Must be legally authorized to work..." and "Schedule/Availability"? but we moved schedule to Schedule section. - Qualifications: maybe education (high school diploma/GED/equivalent or above). Also maybe "Some experience with inventory management..."? That's experience, but we already have experience under Requirements. Could also include "For Experiential stores with food/beverage service only: Food safety and/or liquor service certification". That's a qualification (conditional). We'll include under Qualifications. - Skills: list of competencies (Inclusion & Diversity, Integrity, Adaptability/Agility, Leadership, Collaboration and Teamwork, Decision Making/Problem Solving, Planning and Organizing, Interactive Communication). Also maybe "Work Context" could be under Skills? But it's more about environment; maybe we can put under Skills as a paragraph? But it's not a list. Could be a

          . However the instruction: Use

          • for any list of duties/requirements/benefits. For prose use

            . So Work Context is prose, not a list, so we can put under Skills as a

            . But Skills section heading expects list of skills; we can still have a

            describing work context. That's okay. - Benefits: list of benefits (extended health and dental benefits, 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, leadership series). Also note about incentive programs eligibility etc. Could be a

            note. - Pay: base pay range, target bonus, total target base pay range, plus description of compensation philosophy etc. Could be a

            with details. - Schedule: schedule details: work schedule can vary, shifts typically mornings, afternoons, evenings, weekends, holidays; peak times may include early mornings or late nights/overnights. Now we need to ensure we don't include boilerplate like "Note: The incentive programs, benefits, and perks have certain eligibility requirements. The Company reserves the right to alter these incentive programs, benefits, and perks in whole or in part at any time without advance notice." That's not boilerplate? It's a note about benefits; it's substantive? It's a note about eligibility and right to alter. Might be considered boilerplate legal. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This note is legal-ish about benefits alteration. Might be considered boilerplate. Safer to remove it. Also the sentence: "At Lululemon, Investing In Our People Is a Top Priority. We Believe That When Life Works, Work Works. We Strive To Be The Place Where Inclusive Leaders Come To Develop And Enable All To Be Well. Recognizing Our Teams For Their Performance And Dedication, Other Components Of Our Total Rewards Offerings Include Support Of Career Development, Wellbeing, And Personal Growth" That's prose about benefits; we can keep as part of Benefits section. Also "As part of our offerings, employees in this position may be eligible for our competitive bonus program and equity offerings, subject to program eligibility requirements." That's part of Pay/Benefits. Now we need to ensure we don't include duplicated lines. There's some duplication? Not obvious. Now produce HTML fragment. Let's craft each section. About the role: Combine Who We Are paragraph and Job Summary. 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 Product Operations Lead is a part of the store leadership team responsible for executing on the store product strategy, including product operations and inventory management. They are responsible for leading inventory shifts, overseeing all back of house (BOH) product operations, and ensuring both the floor and BOH are stocked and well-organized. The Product Operations Lead provides input to team member performance evaluations, recommendations into store hiring decisions, and acts as Supervisor on Duty (SOD) while leading inventory shifts. The Product Operations Lead also oversees and delivers a world-class guest (i.e., customer) experience when scheduled to work on the floor." We'll combine into one

            maybe two paragraphs. Responsibilities: list each bullet from Core Responsibilities Of The Job. Let's extract bullets: - Collaborate with store leadership to bring product strategy to life. - Proactively plan, prioritize, manage, and lead inventory processing and accuracy activities in accordance with standard operating procedures (SOPs). - Ensure execution of product actions (e.g., pull backs, consolidations, repricing). - Engage team members in inventory management by creating a fun and productive atmosphere for the shift. - Monitor product levels and communicate findings to support sell-through strategy and optimal product availability for the guest. - Review and interpret daily business data and metrics to inform actions, for example analyzing product sell-through data to provide recommendations to store leadership regarding product focus or, for outlets, pricing. - Participate