Seasonal Retail Sales Associate - Tanger Out Savannah

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. We must not repeat job title. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines. Preserve all substantive info. We need to parse the posting. Content: - Intro about Old Navy (company description). Could be considered "About the role"? Actually there is "About Old Navy" then "About The Role". The "About Old Navy" is company overview; maybe we can treat as part of "About the role"? But heading "About the role" is for role description. The "About Old Navy" is more about company; maybe we can include under "About the role" as description? However guidelines: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include the role description and maybe company overview? The role description includes "As a Brand Associate, you’re an integral part...". The "About Old Navy" is separate but could be considered part of "About the role"? Might be okay to include under "About the role". However we must not create sections with filler. We have content for About the role (the paragraph after "About The Role"). Responsibilities: The bullet list under "What you'll do". Those are duties. Requirements: The list under "Who you are" and "To be considered for this role, applicants must:" includes qualifications like age, work authorization, etc. Also "Who you are" includes traits: good communicator, customer-focused, passionate, problem solver. Those could be Qualifications or Skills. We need to map. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which content goes where. Let's extract: Company overview (About Old Navy) - maybe not needed as separate heading; could be omitted? But we must preserve ALL substantive information. If we omit it, we lose info. Could we put it under "About the role"? The heading "About the role" could include both company overview and role description. That seems acceptable. Responsibilities: The list of duties under "What you'll do". We'll put each as

. Requirements: Could be the mandatory eligibility criteria: age 16+, work authorized, no visa sponsorship, willing to learn tech, flexible schedule, able to perform essential functions (standing, walking, lifting up to 30 lbs). Those are requirements. Qualifications: Could be the "Who you are" traits: good communicator, customer-focused service provider, passionate about retail, problem solver, continuous improvement, learning, open to feedback, takes action. Those are qualifications. Skills: Could be specific skills like product knowledge, suggestive selling, omni-channel, operational processes, technology tools (mobile devices, apps, registers). Might be overlapping. But we can put some under Skills. Benefits: The list under "Benefits at Old Navy": merchandise discount 50% off regular-priced merchandise at Old Navy, Gap, Banana Republic and Athleta, 30% off at Outlet; competitive PTO; up to five “on the clock” hours each month to volunteer; extensive 401(k) plan with company matching up to 4%; employee stock purchase plan; medical, dental, vision, life insurance; see more benefits (we can ignore "see more"). Pay: Not mentioned. So we should NOT include Pay section. Schedule: Not explicitly mentioned except flexible schedule based on business needs, including evenings, weekends, holidays. That's a schedule requirement. Could be placed under Requirements or maybe Schedule section. Since we have schedule info, we can create a Schedule section with that detail. However the requirement also includes flexible schedule; we could put under Schedule. But we also have schedule mention in requirements. To avoid duplication, we could put schedule info under Schedule section and not repeat under Requirements. However the requirement also includes "Be available to work a flexible schedule based on business needs, including evenings, weekends, and holidays, with or without reasonable accommodation." That's schedule. So we can put that under Schedule. Thus Requirements: age, work authorization, no visa sponsorship, willingness to learn tech, ability to perform essential functions (standing, walking, moving, lifting up to 30 lbs). Also maybe "Be able to perform the essential functions of the role, including standing, walking, moving throughout the store, and lifting up to 30 pounds, with or without reasonable accommodation." That's a requirement. Qualifications: the "Who you are" traits. Skills: maybe product knowledge, suggestive selling, omni-channel, operational processes, technology tools. But we need to ensure we don't create thin sections. Let's see if we have enough for each. About the role: we have company overview + role description paragraph. Responsibilities: we have a list of duties (multiple lines). Good. Requirements: we have age, work auth, no visa, tech willingness, essential functions. That's enough. Qualifications: we have good communicator, customer-focused, passionate about retail, problem solver, continuous improvement, learning, open to feedback, takes action. That's enough. Skills: we have product knowledge, suggestive selling, omni-channel, operational processes, technology tools (mobile devices, apps, registers). That's enough. Benefits: we have discount, PTO, volunteer hours, 401(k) match, stock purchase, insurance. Good. Schedule: we have flexible schedule including evenings, weekends, holidays. That's enough. Pay: none -> omit. Now we need to output HTML fragment with

headings and appropriate

• for lists,

  for prose. We must not include any boilerplate like EEO, equal-opportunity, etc. Also remove duplicated lines. Ensure we preserve all substantive info. Let's extract exact sentences. About Old Navy paragraph: "Forget what you know about old-school industry rules. When you work at Old Navy, you’re choosing a different path. From day one, we’ve been on a mission to democratize fashion and make shopping fun again. Our teams make style accessible to everyone, creating high-quality, must-have fashion essentials for the whole family, with love, season after season. We opened our first store in 1994 in San Francisco and have been on a roll ever since. We cultivate a community of playful personalities that thrive in a fast-paced environment where our employees can be their most authentic selves. Here, we’re family." About The Role paragraph: "As a Brand Associate, you’re an integral part of our team and bring our brand to life for our customers. You’re responsible for engaging and connecting with our customers by providing excellent customer service resulting in brand loyalty. You’re an expert in product and use your knowledge and experience to educate, inform, inspire and wardrobe the customer. Through collaboration with your leadership team, you’ll deliver a best-in-class customer experience using an omni-channel approach." We could combine these two paragraphs under About the role heading. Now Responsibilities (What you'll do) list: - Consistently treat all customers and employees with respect and contribute to a positive work environment. - Promote loyalty by educating customers about our loyalty programs. - Seek out and engage with customers to drive sales and service using suggestive selling. - Enhance customer experience using all omnichannel offerings. - Be accountable to personal goals which contribute to overall store goals and results. - Support sales floor, fitting room, cash wrap, back of house, as required. - Maintain a neat, clean and organized work center. - Handle all customer interactions and potential issues returns courteously and professionally. (Note: there's a typo "issuesreturns". Likely "issues returns". We'll keep as given: "Handle all customer interactions and potential issues returns courteously and professionally." Might be "Handle all customer interactions and potential issues/returns courteously and professionally." We'll keep as is but maybe fix? We should preserve original text exactly? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the text as is, but we can correct obvious typo? That would be inventing? Changing text could be considered altering. Safer to keep as is: "Handle all customer interactions and potential issuesreturns courteously and professionally." That seems odd but we keep. - Execute operational processes effectively and efficiently. Now Requirements (eligibility): - Be at least 16 years of age. - Be legally authorized to work in the United States. - Not require current or future employment visa sponsorship to work in the United States. - Be willing to learn and use technology tools, including mobile devices, apps, and registers, used in day-to-day operations. - Be able to perform the essential functions of the role, including standing, walking, moving throughout the store, and lifting up to 30 pounds, with or without reasonable accommodation. Also "Be available to work a flexible schedule based on business needs, including evenings, weekends, and holidays, with or without reasonable accommodation." That's schedule; we will move to Schedule section. Now Qualifications (Who you are): - A good communicator with the ability to effectively interact with customers and your team to meet goals. - A customer-focused service provider both on and off the sales floor to help deliver an exceptional experience for our customers. - Passionate about retail and thrive in a fast-paced environment. - A problem solver with a focus on continuous improvement, who is always learning, open to feedback and takes action as required. Now Skills: Could be derived from responsibilities and other parts: product knowledge, suggestive selling, omni-channel, operational processes, technology tools. But we already have technology tools in Requirements; maybe we move that to Skills. However we need to avoid duplication. Let's think: The requirement includes willingness to learn and use technology tools. That's a requirement but also a skill. Could be placed under Skills. But we already used that as a requirement. Might be okay to have it in both? Duplication is discouraged. Better to assign each piece to one section. Let's allocate: Requirements: age, work auth, no visa, essential functions (standing, walking, lifting). (We could also include willingness to learn tech as a requirement but maybe better as Skill.) Schedule: flexible schedule including evenings, weekends, holidays. Skills: product knowledge, suggestive selling, omni-channel offerings, operational processes, technology tools (mobile devices, apps, registers). Also maybe "educate, inform, inspire and wardrobe the customer" but that's more responsibility. Qualifications: good communicator, customer-focused, passionate about retail, problem solver, continuous improvement, learning, open to feedback, takes action. Now Benefits: list. - Merchandise discount for our brands: 50% off regular-priced merchandise at Old Navy, Gap, Banana Republic and Athleta, and 30% off at Outlet for all employees. - One of the most competitive Paid Time Off plans in the industry.*Employees can take up to five “on the clock” hours each month to volunteer at a charity of their choice.* (The asterisk and note; we keep as is.) - Extensive 401(k) plan with company matching for contributions up to four percent of an employee’s base pay.* - Employee stock purchase plan.* - Medical, dental, vision and life insurance.* - See more of the benefits we offer. (This is maybe boilerplate? It's a call to action; but it's substantive? It's a reference; we could keep but it's not specific benefit. Might be considered filler. The instruction: Remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "See more of the benefits we offer." is like a link; maybe we can drop as it's not substantive detail. Safer to omit. Now Schedule: "Be available to work a flexible schedule based on business needs, including evenings, weekends, and holidays, with or without reasonable accommodation." Now we need to ensure we don't have any heading with empty content. Let's craft HTML. We'll start with

  About the role

  then

  containing both