Assistant Store Manager - Short Hills

We need to output HTML fragment with sections: About the role? Actually we have description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have description: "ANINE BING is looking for a Assistant Store Manager to join our Flagship store location in Short Hills, New Jersey. The Assistant Store Manager works closely with the Store Manager and Sales team to drive a client-first experience..." That's about the role. Could be About the role. Responsibilities: list of duties: bullet points under "Job Duties Include". We need to put those as

• . Requirements: list of requirements after "Requirements". Provide bullet list. Qualifications: maybe not separate; we could combine with Requirements? But we have separate sections: Requirements and Qualifications. The posting has "Requirements" then bullet list. No separate Qualifications. Could we treat Requirements as Qualifications? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we can have Requirements section with bullet list. Qualifications maybe not present; we skip. Skills: maybe we can extract from requirements: "Proficient in managing and achieving sales goals, budgeting, and retail math", "Strong coaching and performance management abilities", "Tech savviness and experience using Microsoft Office (Excel, Word) & G Suite". Could be a Skills section. But we already have Requirements covering many. To avoid duplication, we could keep Requirements as bullet list and not create Skills unless distinct. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one Requirements section. But we need to follow headings list; we can choose which to include. Likely include About the role, Responsibilities, Requirements, Benefits, Pay. Schedule? The posting mentions flexible work schedule including nights, weekends and retail holidays. That's schedule info. So we can include Schedule section with that statement. Pay: posting includes "New Jersey pay range $27 - $30 USD". So include Pay. Benefits: there is Benefits & Perks section with details. So include Benefits. Thus sections: About the role (intro paragraph), Responsibilities (list), Requirements (list), Benefits (list maybe), Pay (paragraph), Schedule (paragraph). Ensure we don't repeat job title as heading. We need to preserve all substantive information; not invent or summarize away detail. Must not include boilerplate like EEO etc. Remove those paragraphs. We need to output only HTML fragment, no /, no markdown fences. Let's craft. About the role: combine first two sentences: "ANINE BING is looking for a Assistant Store Manager to join our Flagship store location in Short Hills, New Jersey. The Assistant Store Manager works closely with the Store Manager and Sales team to drive a client-first experience and support every aspect of the ongoing success and development of their designated Retail location, including operational excellence, curating memorable in-store experiences, and establishing a healthy team dynamic. The ideal Assistant Store Manager is passionate about clienteling, team building, fashion, and styling and seeks to grow personally and professionally in their ANINE BING journey. The person in this role must be able to balance driving sales with rolling up their sleeves to get the job done in-store." That's fine. Responsibilities: list each duty from "Job Duties Include". Let's extract bullet points: - Be the ultimate brand ambassador. Communicate ANINE BING’s values and unique story to our clients & peers - Build lasting relationships with clients by providing best-in-class service in a personalized and elevated ceremony - Work closely with the Store Manager to lead and support driving daily sales, team leadership, and store operations with a focus on business and KPI growth - Seek fashion and product knowledge to build your styling expertise while teaching and mentoring your team to do the same - Drive sales through personal client outreach, setting repeat in-store/virtual appointments, and developing external consignment business - Maintain a clean and organized presentation of the store space. Support visual merchandising standards and directives. - Assist with daily store operations, (not limited to) inventory management, online order fulfillment, cash management, cycle counts, and store maintenance needs. - Carry out all duties and responsibilities consistent with the position and maintain awareness as the business evolves over time We need to keep each as
• . Ensure we keep punctuation inside. Requirements: bullet list from "Requirements". Items: - 3-5 years of retail experience in the contemporary, advanced contemporary, or luxury market - Exceptional interpersonal and customer service skills, driven to create and foster customer relationships - Proactive and positive handling of customer concerns, demonstrating a customer-centric approach - Proficient in managing and achieving sales goals, budgeting, and retail math - Strong coaching and performance management abilities with experience focusing on building and maintaining client relationships and teaching team members. - Highly motivated, goal-oriented, and adaptable to a fast-paced environment, with a positive and engaging leadership style - Tech savviness and experience using Microsoft Office (Excel, Word) & G Suite (Google Docs, Sheets, etc.) - Must be able to work a flexible work schedule including nights, weekends and retail holidays - Ability to regularly stand, walk, bend, and move throughout the store during shifts - Ability to meet physical demands, including but not limited to: standing and walking for extended periods; frequent bending, reaching, squatting, and climbing ladders; lifting and carrying up to 50 pounds; moving merchandise and fixtures; operating POS systems; and performing all essential job functions in a fast-paced retail environment, with or without reasonable accommodation. Note: The flexible work schedule appears also in schedule; but we can keep it in requirements as it's a requirement. However schedule section will also mention flexible schedule. Might duplicate but okay. Could remove from requirements to avoid duplication but we must preserve all substantive info; removing would lose info. Could keep both but it's okay duplication? The instruction: preserve ALL substantive information; do not invent or summarize away detail. Duplication is not prohibited but better to avoid redundancy? It says remove duplicated lines. So we should not duplicate the same line. The flexible schedule appears both in requirements and schedule. We should keep it only once. Where does it belong? It's a requirement (must be able to work flexible schedule). Also schedule info. We could place it under Requirements and not repeat in Schedule; but schedule section could mention that schedule is flexible (nights, weekends, retail holidays) but that's same. To avoid duplication, we could place schedule info elsewhere? The schedule section could be brief: "Schedule: Flexible work schedule including nights, weekends, and retail holidays." That's essentially same as requirement line. If we include it in Requirements, we could omit from Schedule to avoid duplication. But schedule section may be considered separate; but we can still include schedule section with that info, but then we would have duplicate content. The instruction says remove duplicated lines. So we should not duplicate. So we need to decide where to put it. Probably better to put under Requirements as it's a requirement. Then Schedule section could be omitted or we could note that schedule is flexible (but that's duplicate). Since we have schedule info already in requirements, we could skip Schedule section entirely. However the posting does mention schedule explicitly: "Must be able to work a flexible work schedule including nights, weekends and retail holidays". That's a requirement. So we can treat that as part of Requirements. Then we don't need a separate Schedule section. The instruction says include a section ONLY when posting has real, specific content for it. If we treat schedule as part of requirements, we still have schedule content but not as separate heading. That's okay. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Benefits: list from "Benefits & Perks". Items: - Work/Life Balance: Flexible work schedules and encouraged paid time off - Wellness: ANINE BING covers 75% of costs for your medical, dental, and vision insurance and offers an array of other benefits for you and your dependents, including a generous parental leave program - And more: Generous employee discount, commission, and wardrobe We need to keep as list items. Pay: "New Jersey pay range $27 - $30 USD". Could be a paragraph. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  New Jersey pay range $27 - $30 USD

  Make sure no extra whitespace? It's fine. Check for any boilerplate removed: EEO paragraph, "More About ANINE BING", "Working at ANINE BING", "Full Compensation Packages Are Based On Candidate Experience" maybe we kept pay line but removed that sentence. The line "Full Compensation Packages Are Based On Candidate Experience" is boilerplate; we should drop it. We kept only the pay range line. Also "ANINE BING seeks to empower its employees..." is EEO boilerplate; drop. Also "More About ANINE BING" paragraph about history; drop. Now ensure we didn't miss any substantive info: The intro about "ANINE BING is a Los Angeles-based fashion house started in 2012..." is boilerplate? It's more about company; maybe considered substantive? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview might be considered not boilerplate but could be considered extra; but it's not explicitly listed as boilerplate. However it's not directly about the role; but it's substantive info about the company. The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should keep it if it's substantive. However earlier we said we would drop "More About ANINE BING". That paragraph is about company history. Might be considered substantive but not required for the role. The instruction does not explicitly say to drop company overview. It says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview is not those. So we should keep it. However we already dropped it; we need to reconsider. We need to preserve ALL substantive information; we cannot drop company overview unless it's considered boilerplate. It's not listed as boilerplate. So we should keep it. But we need to decide where to place it. Could be part of About the role or a separate section like "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could incorporate company overview into About the role paragraph. That would be okay: we can expand About the role to include company description. That would preserve info. Thus About the role paragraph should include: "ANINE BING is a Los Angeles-based fashion house started in 2012 that blends elements of Scandinavian simplicity with American energy to offer modern wardrobe essentials for women seeking a timeless yet rebellious approach to everyday style. Since its launch, ANINE BING has built a global brand represented across 90+ countries, including brick-and-mortar retail stores in cities worldwide. Headquartered in Los Angeles, ANINE BING has over 200 employees and is backed by key investors, which include Index Ventures founder Danny Rimer (Facebook, Dropbox, Roblox, Net-A-Porter), Greycroft Partners founder Dana Settle (Bumble, Cuyana, Farfetch), and Felix Capital founder Frederic Court (Goop, Farfetch, Vitrue, Dailymotion)." plus the earlier role description. We need to ensure we don't duplicate any lines. We'll combine. Now About the role paragraph will be long but okay. Now check for any other substantive info: "Working at