Jobs · Business Development · Florida

Seasonal Retail Sales Associate - Miami International

Old Navy · Miami, FL · 1 mo ago
Business DevelopmentPart-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. From posting: - About Old Navy (intro) maybe not needed as 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. So we can include "About the role" heading? There's a section "About The Role". That's appropriate. - Responsibilities: "What you'll do" list. - Requirements: "Who you are" bullet list? Actually "Who you are" includes traits; also "To be considered for this role, applicants must:" list of requirements. - Qualifications: maybe not separate; but we could combine with Requirements? The instruction: include a section only when posting has real specific content. There's no explicit "Qualifications" separate from requirements. Could we treat "Who you are" as Qualifications? Might be okay. But we need to decide. - Skills: maybe not explicit; but we could infer from "good communicator", etc. Might be too thin. Better to omit Skills if not explicit. - Benefits: there is "Benefits at Old Navy" with list. - Pay: not mentioned. - Schedule: mention flexible schedule, evenings, weekends, holidays. Thus sections: About the role, Responsibilities, Requirements (or Who you are), Benefits, Schedule. We need to use

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

    for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes EEO statements at end: "For eligible employees Gap Inc. is an equal-opportunity employer..." etc. That's boilerplate; remove. Also remove duplicated lines? Not seeing duplicates. We need to keep all substantive info: About Old Navy intro? Might be considered part of About the role? The instruction: Use

    for section headings (e.g. About the role...). The "About Old Navy" paragraph is introductory about company; could be placed under About the role? But maybe we should include it as a paragraph before headings? The instruction says output only HTML fragment; we can include a

    for the About Old Navy intro before headings. It's not a heading; it's prose. That seems okay. Then

    About the role

    then maybe a

    summarizing the role description? The posting has "About The Role As a Brand Associate, you’re an integral part..." That's prose. We'll put that in a

    . Then Responsibilities: heading

    Responsibilities

    then
      with each duty from "What you'll do". Need to preserve each bullet exactly. List items: - 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". Should be "issues returns". We'll keep as is? Probably keep original text: "Handle all customer interactions and potential issueseturns courteously and professionally." Might be a mistake but we must preserve ALL substantive information; do not invent or summarize away detail. So we keep exactly as given. - Execute operational processes effectively and efficiently. Now Requirements/Qualifications: We have "Who you are" list of traits, and then "To be considered for this role, applicants must:" list. We could combine into Requirements section with two sub-lists? But we need to use
      • for any list. Could have one
          with all items. However some are traits, some are mandatory requirements. We'll keep them together. List items from "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. Then from "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'll put all in one
            . Now Benefits: heading

            Benefits

            then
              with each benefit. 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.* (Note there is asterisk and then sentence; we need to preserve as given. Might be two separate bullet? Actually it's one bullet with asterisk then sentence. We'll keep as one bullet: "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. Note there are asterisks after some items; we keep them. Now Schedule: heading

              Schedule

              then

              with the flexible schedule statement? The posting mentions schedule in requirements: "Be available to work a flexible schedule based on business needs, including evenings, weekends, and holidays, with or without reasonable accommodation." That's already in Requirements. But we could still have a Schedule section if there is specific content. However the instruction: include a section ONLY when the posting has real, specific content for it. The schedule content is already in Requirements; but we could still have a Schedule section if we want to avoid duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we put schedule info only in Requirements, that's fine; we don't need a separate Schedule section unless there is additional schedule info elsewhere. There's no separate schedule details. So we should not create a Schedule section because it would be duplicate or thin? Actually we could move the schedule bullet to Schedule section and remove from Requirements to avoid duplication? But then we would lose that requirement from Requirements section; we need to preserve all info. Could keep it in both places? That would be duplication, which we should avoid (remove duplicated lines). So we need to decide where to place it. The requirement about schedule is a requirement; it's also schedule info. The instruction says we can have a Schedule section if posting actually states them. It does state schedule flexibility. So we could create a Schedule section with that sentence, and remove it from Requirements to avoid duplication. However the requirement list also includes other items; we could keep the schedule bullet in Requirements as it's a requirement, but then we would have duplicate content if we also have Schedule section. The instruction says remove duplicated lines. So we should not duplicate. So we need to choose one place. Which is more appropriate? The schedule bullet is a requirement (availability). It could be placed under Requirements. The Schedule section is for schedule details; but we have only that bullet. If we put it under Schedule, we still need to keep the requirement elsewhere? Actually the requirement is about availability; that's the schedule requirement. So we could treat it as schedule requirement and put it under Schedule section, and not duplicate in Requirements. However the Requirements section would then lose that bullet; but we could still keep other requirements. That's okay as long as we preserve all info somewhere. So we can move schedule bullet to Schedule section. Thus Requirements section will have all items except the schedule bullet. Now we need to ensure we don't create Pay section (no pay info). Skills section (no explicit skills). Benefits we have. Now we need to output HTML fragment only. Let's craft:

              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.

              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.

              Responsibilities

              • 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 issueseturns courteously and professionally.
              • Execute operational processes effectively and efficiently.

              Requirements

              • 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.
              • 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 3

Similar jobs