Jobs · OTHR · Indiana

H&M Seasonal Sales Advisor - Tippecanoe mall

H&M · Lafayette, IN · 4 wk ago
On-siteOTHR$14/hrPart-time
We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only when posting has real specific content. Must not repeat job title as heading. Must not put Job ID etc. Must preserve all substantive info, no invented or summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Additional Information" etc if it's boilerplate? But we need to keep substantive info like Pay Rate, Benefits, etc. The posting includes "Compensation: Sales Associates Pay Rate $14.00 per hour". That's pay. Also benefits described: staff discount card, H&M Incentive Program (HIP), global benefits, local perks, etc. Also schedule? Not mentioned. So we should not create Schedule section. Also maybe "Qualifications" section: they have "Qualifications Who You Are". Also "Skills"? Not explicit but we could treat "Qualifications" as covering skills. The instruction says use headings for those categories if content exists. We have "About the role" content: first paragraph after "About the Role". Also "A Day in the Life" includes responsibilities bullet list. That could go under Responsibilities. Also "General Information" includes sub-sections: Fashion & Trend Awareness, Team & Development, Retail Operations/ Visual & Commercial Execution. Those are responsibilities/duties. So we can combine under Responsibilities. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like "welcoming & guiding customers through the store & OMNI experience where available", etc. Must not omit any detail. That's a lot. We need to output as HTML with

for prose and

  • for lists. We must not include boilerplate like EEOC, diversity statements? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The posting includes a diversity statement under "Why You'll Love Working at H&M" and later "Inclusion & Diversity". Those might be considered EEO boilerplate? It's about diversity and inclusion; but it's not exactly EEO statement; it's part of benefits/culture. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Likely we should remove the diversity statement sections. However, we need to preserve substantive information; diversity statement may be considered boilerplate but it's also part of why you'll love working. Might be considered fluff but still substantive? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should cut those paragraphs. Also remove "Additional Information" like Job Status, EEOC Code, Compensation (we keep compensation as Pay), but we need to keep Pay Rate. The "Additional Information" includes Job Status: Hourly, Non-Exempt, EEOC Code: SLS, Compensation: Sales Associates Pay Rate $14.00 per hour**. Also note about compensation range. We'll keep Pay section with that info. Also "Benefits:" section we keep. Also "Company Description" maybe not needed? It's somewhat boilerplate but could be considered substantive? It's describing H&M. Might be considered boilerplate but not EEO. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description may be considered not required but it's substantive info about the company. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company description if it's substantive. But it's generic; still it's info about the company. Might be okay to keep. However, we need to avoid creating thin sections. Could put under "About the company" but not a prescribed heading. We only have prescribed headings. Could we put under "About the role"? No. Could we add a

    after the headings? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but better to stick to those. The company description could be placed under "About the role"? Not really. Could be placed under a

    without heading? The instruction says use

    for section headings (list). It doesn't say you cannot have other headings, but to be safe we could incorporate company description into a

    after the headings, maybe as part of "About the role"? Might be okay. But we need to preserve all substantive info: includes "H&M Fashion USA, Inc. – Maki Assessment Tool:" etc. That's a lot of detail about assessment tool, cookies, privacy, etc. Many of those are legal/boilerplate (cookie notice, privacy, etc.) Should be removed per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should cut the Maki assessment tool details, cookie notice, privacy notice, etc. Also the "Additional Information" includes Job Status, EEOC Code, Compensation (we keep compensation). The "Additional Information" also includes note about compensation range etc. We'll keep that in Pay section. Also "Benefits:" we keep. Also "Inclusion & Diversity:" we should remove as EEO boilerplate. Also "Company Description:" maybe keep? It's not EEO but could be considered boilerplate but it's descriptive. I'd keep it as a

    maybe under a heading "About the company"? Not in list. Could we treat it as part of "About the role"? Not ideal. Perhaps we can add a heading "About the company" but not in the prescribed list; risk of violating instruction? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be interpreted that we should only use those headings for sections. Safer to not add other headings. So we can place company description as a

    without a heading, maybe after the sections. That's allowed. Now we need to decide which sections to include: - About the role: we have description after "About the Role". Keep that. - Responsibilities: we have "A Day in the Life" bullet list and also the sub-sections under General Information (Fashion & Trend Awareness, Team & Development, Retail Operations/ Visual & Commercial Execution). Those are responsibilities/duties. So we will create a Responsibilities section with

    • items covering all duties. Must preserve all details; we need to list each duty as separate
    • . Might be many items; we need to ensure we don't lose any. Let's extract duties from the text: From "A Day in the Life Working at H&M means no two days are ever the same, but a typical day will include the following responsibilities*" then bullet list with asterisks? Actually the bullet list appears as lines starting with maybe no bullet but each line is a responsibility. Let's list them: - Customer Sales & Profit Provide excellent customer service: welcoming & guiding customers through the store & OMNI experience where available, supporting them with direct customer service Willingness to engage and have conversations with customers to provide excellent service Guide customers through our fashion trends, stories & products in all areas of the store Ability to effectively promote and sell our products to customers Actively promote our Customer Loyalty App (Hello Member) & in-store sustainability initiatives Representing yourself and the H&M brand positively during all customer interactions Support with commercial or operational actions to reach sales targets with store management team - General Information Fashion & Trend Awareness Keep up-to-date with fashion scene, trends, tendencies, styles, brands, products, competitors, and relevant influencers, etc. Use your product & fashion knowledge to share relevant information to customers Team & Development Retain and share your service, fashion and store operations knowledge and skills with colleagues Follow all procedures, routines, and legal requirements in all areas of the store Give & receive feedback with your colleagues to learn, develop & support each other Participate in relevant available Onboarding, introduction processes & trainings and courses relevant for your role & future development Retail Operations/ Visual & Commercial Execution Complete full garment cycle from unpacking and refill to steaming and ensure good garment care Operate fitting room and checkout areas according to best practice & processes Contribute to a clean and tidy sales floor and back of house (including stockrooms) Support with garment presentation, execution and maintain attractive merchandise displays, clear trends & stories according to visual & commercial guidelines Ensure good stock levels with replenishment routines on sales floor Upkeep & follow best practice for any in-store OMNI Services & in-store tech services/tools, etc (Instore Care App, Click & Collect, Smart Store etc) Support with opening and closing of the store Following all H&S guidelines and legal requirements applicable to role and responsibilities Also there is earlier paragraph under About the Role: "As a Sales Advisor, you'll be responsible for providing excellent customer service, welcoming & guiding customers through your store to actively sell our products and providing customers with support & guidance. You'll use your fashion and product knowledge to provide our customers with all the relevant information they need for the best experience. You'll also work on garment refill & care, presentation and contribute to a clean and tidy sales floor and back of house, working closely with the rest of your store team to deliver an excellent customer experience." These are also responsibilities; we should include them. Thus Responsibilities section will combine all these. Now Requirements: The posting has "Qualifications Who You Are" which includes personal attributes and experience. That could be considered Requirements or Qualifications. The instruction includes both Requirements and Qualifications headings. We need to decide where to put content. The posting has a section titled "Qualifications". So we should put that under Qualifications heading. Requirements maybe not present; we could omit Requirements if no specific content. However, there is also "Experience working with customer service in fashion, retail or other service-related industries" and "You have sales experience working in a dynamic and collaborative environment that you can apply to your role". That's qualifications. So we put under Qualifications. Skills: Not explicitly listed; maybe we could treat some of the personal attributes as skills, but we have Qualifications covering them. The instruction says prefer a few substantive sections over many thin ones. So we might omit Skills if no distinct content. Benefits: we have Benefits section described. Pay: we have Compensation: Pay Rate $14.00 per hour. Schedule: not present, omit. Now we need to ensure we don't include boilerplate like "Job Status: Hourly, Non-Exempt EEOC Code: SLS". That's metadata; we could fold minor metadata into a short

      or drop it. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it. So we could include Job Status etc as a short

      maybe under About the role? Or we could drop it. Since it's minor metadata, we could drop it. But we need to preserve ALL substantive information; is Job Status substantive? It's about hourly non-exempt; could be considered substantive but minor. The instruction says fold minor metadata into a short

      or drop it. So we can include a short

      with that info. Similarly, "Additional Information Job Status: Hourly, Non-Exempt EEOC Code: SLS Compensation: Sales Associates Pay Rate $14.00 per hour** ..." We'll extract Pay Rate for Pay section, and maybe include Job Status etc as a short

      . Now we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate

Similar jobs