Jobs · Business Development · Kansas

Seasonal Retail Sales Associate - Emporia Pavilions

Old Navy · Emporia, KS · 1 mo ago
Business DevelopmentPart-time
We need to output HTML fragment with sections: About the role (but note there is "About The Role" heading in text). Also "What you'll do" (responsibilities). "Who you are" (requirements/qualifications). "Benefits at Old Navy". Also maybe "About Old Navy" is intro but not a section heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections only when posting has real, specific content. So we need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (from "What you'll do"). Requirements/Qualifications (from "Who you are" and the bullet list of eligibility). Benefits (from "Benefits at Old Navy"). We should not include Pay or Schedule unless present; they are not explicit. There's mention of flexible schedule but not specific schedule details; we should not create Schedule section because it's not specific content? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated, so include Benefits. Schedule: they mention flexible schedule but not specific schedule; maybe we could include Schedule? The instruction says only if posting actually states them. It does state "Be available to work a flexible schedule based on business needs, including evenings, weekends, and holidays, with or without reasonable accommodation." That's schedule info. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we could include Schedule section with that content. But they also said "Prefer a few substantive sections over many thin ones." Might be better to incorporate schedule info into Requirements or Responsibilities? But schedule is a condition of employment, could be part of Requirements. However they gave example headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Schedule section. But we need to decide: The posting includes schedule requirement; we could put that under Requirements or a separate Schedule section. Since they want sections only when posting has real, specific content for it, schedule is specific enough. However they also say "Prefer a few substantive sections over many thin ones." Adding Schedule may be thin but still substantive. Could combine schedule into Requirements. I'd lean to include Schedule as its own section because it's clearly about schedule. But we must not include placeholder text like "varies", "TBD". The schedule content is specific: flexible schedule including evenings, weekends, holidays. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Could also include Qualifications but we have Requirements covering qualifications. Might combine Requirements and Qualifications into one section? The instruction list includes both; but we can choose to have Requirements section covering both. To avoid thin sections, we can have Requirements (including qualifications). Benefits separate. Schedule separate. Now we need to strip boilerplate: The EEO statement, equal-opportunity, etc. Also "For eligible employees Gap Inc. is an equal-opportunity employer..." etc. Remove that. Also "See more of the benefits we offer." maybe keep? It's vague; but it's part of benefits section; we can keep as prose but it's not specific. Might be considered boilerplate? It's a generic line; but it's part of benefits description. I'd keep it as it's not duplicate. Also remove "About Old Navy" intro? It's not a section heading but could be kept as a

before sections? 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 "About Old Navy" is not a heading but could be considered introductory text. Should we keep it? It's substantive about company; but not required for job posting? Might be considered boilerplate? It's describing the company; could be kept as a

before sections. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that intro as a

. However they said use

for section headings; we can have a leading

for the About Old Navy paragraph. Thus output:

About Old Navy Forget what you know about old-school industry rules....

then

About the role

As a Brand Associate, you’re an integral part of our team and bring our brand to life for our customers....

then

Responsibilities

  • ...
then

Requirements

  • ...
then

Benefits

  • ...
then

Schedule

Be available to work a flexible schedule based on business needs, including evenings, weekends, and holidays, with or without reasonable accommodation.

We need to ensure we preserve all substantive information from each section. Let's extract content. About Old Navy paragraph: "About Old Navy 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." We need to keep that exactly? Might need to preserve punctuation. We'll output as a single

with that text. About The Role paragraph: "About The Role 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 need to keep that as

under About the role heading. What you'll do list: bullet points: - 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: "issueseturns". Likely "issues returns". We'll keep as given? Probably should keep original text: "Handle all customer interactions and potential issueseturns courteously and professionally." We'll keep exactly as in source? Might be a mistake but we must preserve. We'll keep as is. - Execute operational processes effectively and efficiently. We need to put each as

  • . Who you are paragraph: "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 fastpaced environment.A problem solver with a focus on continuous improvement, who is always learning, open to feedback and takes action as required." Note there are missing spaces after periods. We'll keep as is. Then eligibility list: "To be considered for this role, applicants must: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 available to work a flexible schedule based on business needs, including evenings, weekends, and holidays, with or without reasonable accommodation.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." We need to put each as
  • under Requirements (or maybe split into Requirements and Schedule). Since we have Schedule separate, we could put schedule bullet there. But the schedule bullet is also part of eligibility. We could keep schedule bullet in Requirements and then have Schedule section maybe redundant. Better to keep schedule bullet in Requirements and not have separate Schedule section, to avoid thin sections. However the instruction says we can create Schedule section if posting actually states them. It does state schedule. But we prefer fewer sections. I'd combine schedule into Requirements. Thus Requirements section will include all eligibility bullets (including schedule). We'll not create separate Schedule. Now Benefits section: "Benefits at Old Navy 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.*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." We need to split into
  • items. The asterisks denote separate benefits. We'll treat each sentence after asterisk as a bullet. Also first sentence about merchandise discount is a benefit. So 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. - 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. We need to preserve the asterisks? Probably not needed; we can drop them. Keep the text. Now we need to remove boilerplate: EEO statement etc. Also "For eligible employees Gap Inc. is an equal-opportunity employer..." etc. Remove that. Also remove "See more of the benefits we offer." maybe it's not boilerplate but it's vague; but it's part of benefits; we keep. Now ensure we don't repeat job title as heading. The job title is "Brand Associate". Not used as heading. Now produce HTML fragment. We'll start with

    About Old Navy ...

    Then

    About the role

    About The Role 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.

    Then

    Responsibilities

  • Similar jobs