H&M Sales Advisor - Seasonal
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. Must not invent or summarize away detail. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes compensation: "Compensation: Sales Associates Pay Rate $15.75 per hour". That's pay. Schedule? Not explicit schedule (maybe hourly, non-exempt). It says "Job Status: Hourly, Non-Exempt". That's schedule type (hourly). Could treat as schedule. But we need to check if schedule is present: "Job Status: Hourly, Non-Exempt". That indicates schedule type (hourly). So we can include Schedule section with that info. Benefits: there is a Benefits paragraph describing benefits. So include Benefits.
We need sections: About the role (present). Responsibilities (present). Requirements/Qualifications? The posting has "Qualifications Who You Are" and also "Additional Information" includes job status, compensation, etc. There's also "Why You'll Love Working at H&M" which is more about benefits/culture. Also "Additional Information" includes job status, compensation, etc. There's also "General Information" sections like "Fashion & Trend Awareness", "Team & Development", "Retail Operations/ Visual & Commercial Execution". Those could be considered responsibilities or requirements. We need to decide how to structure.
We must not repeat job title. Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content accordingly.
About the role: The initial paragraph under "About the Role". Use that.
Responsibilities: The bullet list under "A Day in the Life" and the subpoints under "Customer Sales & Profit", also the "General Information" sections (Fashion & Trend Awareness, Team & Development, Retail Operations/ Visual & Commercial Execution) could be responsibilities. But we need to avoid duplication. Could treat those as responsibilities.
Requirements: Might be minimal; maybe none explicit besides "You should also be communicative, creative and curious, motivated, flexible, decisive, and action-oriented. You should also enjoy working in a collaborative and dynamic environment. You have sales experience working in a dynamic and collaborative environment that you can apply to your role Experience working with customer service in fashion, retail or other service-related industries". That's more qualifications/skills. Could put under Qualifications.
Skills: Could list specific skills like fashion & trend awareness, customer service, sales, visual merchandising, garment care, etc. But we need to avoid filler. Might be better to combine Qualifications and Skills? But we need separate headings only if content exists.
We have "Qualifications Who You Are" paragraph describing personal attributes and experience. That's qualifications.
We have "Why You'll Love Working at H&M" describing benefits and culture; but we already have Benefits section for tangible benefits. The "Why You'll Love Working at H&M" includes things like valuing diverse backgrounds, colleague resource groups, global talent community, wellbeing, benefits, employee discount. Some of that overlaps with Benefits. We'll extract substantive benefit info: staff discount card, H&M Incentive Program (HIP), local market perks, etc. Also mention comprehensive benefits: health insurance, wellness, family support, company match retirement, paid leave, paid time off, community day. That's in the Benefits paragraph.
Thus Benefits section will include those details.
Pay: compensation $15.75 per hour.
Schedule: Job Status: Hourly, Non-Exempt.
Now we need to ensure we don't include boilerplate like EEOC, etc. Remove lines about EEOC Code, etc. Also remove "Additional Information Job Status: Hourly, Non-Exempt EEOC Code: SLS Compensation: ..." We'll keep only Job Status and Compensation.
Also remove "This position is subject to a 90 day contract." That's substantive? It's a detail about contract length. Should we keep? It's substantive info about the job. It's not boilerplate. Should we include? It's under Additional Information. Could be placed maybe under About the role or Responsibilities? It's a job condition. Could be placed under About the role or maybe a separate section like "Contract". But we only have allowed headings. Could put under About the role as a sentence. Or under Responsibilities? Probably better to add a sentence in About the role or maybe under Qualifications? I'd add a sentence in About the role after the description: "This position is subject to a 90‑day contract." That preserves info.
Also remove "*This job posting highlights the most critical responsibilities and requirements of the job and is not all-inclusive..." That's boilerplate-ish but it's a disclaimer. Might be considered boilerplate; we should remove per instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a disclaimer about completeness; maybe considered boilerplate. Safer to remove.
Also remove "**H&M, in good faith, has assessed this posted range..." etc. That's also disclaimer about compensation; could be considered boilerplate. Remove.
Also remove "We are committed to providing reasonable accommodations..." etc. That's EEO/accommodation statement; remove.
Also remove "Benefits: We offer all our employees at H&M Group attractive benefits..." That's substantive benefits; keep.
Also remove "In addition to our staff discount, all our employees are included in our H&M Incentive Program – HIP." Keep.
Also remove "In addition to our global benefits, all our local markets offer different competitive perks and benefits." Keep.
Also remove "Please note that they may differ between employment type and countries." That's maybe boilerplate but it's a qualifier; could keep as part of benefits description.
Also remove "Inclusion & Diversity: ..." That's EEO/diversity boilerplate; remove.
Also remove "Company Description: H&M is a fashion brand..." That's maybe not boilerplate but could be considered generic; but it's substantive about company. Might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed to remove, but could be considered boilerplate? It's not legal/EEO. Might keep as part of About the role? But we already have About the role describing role. Company description could be separate but we don't have a heading for company. Could incorporate into About the role as a sentence? Might be okay to keep as a paragraph under About the role? But the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep company description if it's substantive. However, we have limited headings; we could add a paragraph under About the role that includes company description. Or we could add a separate section like "About the Company" but not allowed headings. So we incorporate.
Similarly, "H&M Fashion USA, Inc. – Maki Assessment Tool:" etc is about assessment; that's substantive info about selection process. Could be included maybe under About the role or Responsibilities? It's about application process, which we are told to remove application instructions. Indeed: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Maki assessment details are application instructions. So we should remove that entire block.
Also remove "During this process, we may collect information from you through cookies..." etc. That's privacy/cookie boilerplate; remove.
Thus final HTML will have sections:
About the role
... (including company description maybe)
Responsibilities
- ... list items
Qualifications
... (personal attributes, experience)
Skills
Maybe we can list skills like fashion & trend awareness, customer service, sales, visual merchandising, garment care, etc. But we need to see if there is explicit skills list. The "General Information" sections could be considered skills/responsibilities. Could treat them as skills. But we already have Responsibilities covering duties. Skills could be things like "Fashion & trend awareness", "Product knowledge", "Communication", "Team collaboration", "Visual merchandising", "Garment care", "Stock replenishment", "OMNI services". We'll extract from the text.
But we must not invent details. We can pull phrases: "Keep up-to-date with fashion scene, trends, tendencies, styles, brands, products, competitors, and relevant influencers". That's a skill. "Use your product & fashion knowledge to share relevant information to customers". That's skill. "Retain and share your service, fashion and store operations knowledge and skills with colleagues". That's skill. "Follow all procedures, routines, and legal requirements". That's more responsibility. "Give & receive feedback with your colleagues to learn, develop & support each other". Skill. "Participate in relevant available Onboarding, introduction processes & trainings and courses relevant for your role & future development". Skill. "Complete full garment cycle from unpacking and refill to steaming and ensure good garment care". Skill. "Operate fitting room and checkout areas according to best practice & processes". Skill. "Contribute to a clean and tidy sales floor and back of house (including stockrooms)". Skill. "Support with garment presentation, execution and maintain attractive merchandise displays, clear trends & stories according to visual & commercial guidelines". Skill. "Ensure good stock levels with replenishment routines on sales floor". Skill. "Upkeep & follow best practice for any in-store OMNI Services & in-store tech services/tools, etc (Instore Care App, Click & Collect, Smart Store etc)". Skill. "Support with opening and closing of the store". Skill. "Following all H&S guidelines and legal requirements applicable to role and responsibilities". Skill/responsibility.
We could put many of these under Skills as bullet list. However, we must avoid too many thin sections; but we have to include sections only if posting has real specific content. It does have many skill-related statements. So we can include Skills section.
But we also have Responsibilities section; we need to decide what goes where. Could put the action-oriented duties under Responsibilities (like providing customer service, welcoming & guiding customers, selling products, promoting loyalty app, supporting commercial actions, etc.) and the skill/knowledge statements under Skills.
Let's extract responsibilities from the "A Day in the Life" bullet points and subpoints:
- 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
- Represent 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
Also from "General Information" sections maybe some are responsibilities: "Fashion & Trend Awareness" is more knowledge/skill. "Team & Development" is skill/sharing. "Retail Operations/ Visual & Commercial Execution" includes many operational tasks: garment cycle, fitting room, checkout, clean floor, garment presentation, stock levels, OMNI services, opening/closing, H&S guidelines. Those could be responsibilities as well.
But to avoid duplication, we could put all operational tasks under Responsibilities, and the knowledge/skill statements under Skills.
Let's decide:
Responsibilities bullet list:
- Provide excellent customer service: welcoming & guiding customers through the store & OMNI experience where
for prose. Do not repeat job title. Do not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive information. Must not invent or summarize away detail. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes compensation: "Compensation: Sales Associates Pay Rate $15.75 per hour". That's pay. Schedule? Not explicit schedule (maybe hourly, non-exempt). It says "Job Status: Hourly, Non-Exempt". That's schedule type (hourly). Could treat as schedule. But we need to check if schedule is present: "Job Status: Hourly, Non-Exempt". That indicates schedule type (hourly). So we can include Schedule section with that info. Benefits: there is a Benefits paragraph describing benefits. So include Benefits. We need sections: About the role (present). Responsibilities (present). Requirements/Qualifications? The posting has "Qualifications Who You Are" and also "Additional Information" includes job status, compensation, etc. There's also "Why You'll Love Working at H&M" which is more about benefits/culture. Also "Additional Information" includes job status, compensation, etc. There's also "General Information" sections like "Fashion & Trend Awareness", "Team & Development", "Retail Operations/ Visual & Commercial Execution". Those could be considered responsibilities or requirements. We need to decide how to structure. We must not repeat job title. Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content accordingly. About the role: The initial paragraph under "About the Role". Use that. Responsibilities: The bullet list under "A Day in the Life" and the subpoints under "Customer Sales & Profit", also the "General Information" sections (Fashion & Trend Awareness, Team & Development, Retail Operations/ Visual & Commercial Execution) could be responsibilities. But we need to avoid duplication. Could treat those as responsibilities. Requirements: Might be minimal; maybe none explicit besides "You should also be communicative, creative and curious, motivated, flexible, decisive, and action-oriented. You should also enjoy working in a collaborative and dynamic environment. You have sales experience working in a dynamic and collaborative environment that you can apply to your role Experience working with customer service in fashion, retail or other service-related industries". That's more qualifications/skills. Could put under Qualifications. Skills: Could list specific skills like fashion & trend awareness, customer service, sales, visual merchandising, garment care, etc. But we need to avoid filler. Might be better to combine Qualifications and Skills? But we need separate headings only if content exists. We have "Qualifications Who You Are" paragraph describing personal attributes and experience. That's qualifications. We have "Why You'll Love Working at H&M" describing benefits and culture; but we already have Benefits section for tangible benefits. The "Why You'll Love Working at H&M" includes things like valuing diverse backgrounds, colleague resource groups, global talent community, wellbeing, benefits, employee discount. Some of that overlaps with Benefits. We'll extract substantive benefit info: staff discount card, H&M Incentive Program (HIP), local market perks, etc. Also mention comprehensive benefits: health insurance, wellness, family support, company match retirement, paid leave, paid time off, community day. That's in the Benefits paragraph. Thus Benefits section will include those details. Pay: compensation $15.75 per hour. Schedule: Job Status: Hourly, Non-Exempt. Now we need to ensure we don't include boilerplate like EEOC, etc. Remove lines about EEOC Code, etc. Also remove "Additional Information Job Status: Hourly, Non-Exempt EEOC Code: SLS Compensation: ..." We'll keep only Job Status and Compensation. Also remove "This position is subject to a 90 day contract." That's substantive? It's a detail about contract length. Should we keep? It's substantive info about the job. It's not boilerplate. Should we include? It's under Additional Information. Could be placed maybe under About the role or Responsibilities? It's a job condition. Could be placed under About the role or maybe a separate section like "Contract". But we only have allowed headings. Could put under About the role as a sentence. Or under Responsibilities? Probably better to add a sentence in About the role or maybe under Qualifications? I'd add a sentence in About the role after the description: "This position is subject to a 90‑day contract." That preserves info. Also remove "*This job posting highlights the most critical responsibilities and requirements of the job and is not all-inclusive..." That's boilerplate-ish but it's a disclaimer. Might be considered boilerplate; we should remove per instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a disclaimer about completeness; maybe considered boilerplate. Safer to remove. Also remove "**H&M, in good faith, has assessed this posted range..." etc. That's also disclaimer about compensation; could be considered boilerplate. Remove. Also remove "We are committed to providing reasonable accommodations..." etc. That's EEO/accommodation statement; remove. Also remove "Benefits: We offer all our employees at H&M Group attractive benefits..." That's substantive benefits; keep. Also remove "In addition to our staff discount, all our employees are included in our H&M Incentive Program – HIP." Keep. Also remove "In addition to our global benefits, all our local markets offer different competitive perks and benefits." Keep. Also remove "Please note that they may differ between employment type and countries." That's maybe boilerplate but it's a qualifier; could keep as part of benefits description. Also remove "Inclusion & Diversity: ..." That's EEO/diversity boilerplate; remove. Also remove "Company Description: H&M is a fashion brand..." That's maybe not boilerplate but could be considered generic; but it's substantive about company. Might keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed to remove, but could be considered boilerplate? It's not legal/EEO. Might keep as part of About the role? But we already have About the role describing role. Company description could be separate but we don't have a heading for company. Could incorporate into About the role as a sentence? Might be okay to keep as a paragraph under About the role? But the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep company description if it's substantive. However, we have limited headings; we could add a paragraph under About the role that includes company description. Or we could add a separate section like "About the Company" but not allowed headings. So we incorporate. Similarly, "H&M Fashion USA, Inc. – Maki Assessment Tool:" etc is about assessment; that's substantive info about selection process. Could be included maybe under About the role or Responsibilities? It's about application process, which we are told to remove application instructions. Indeed: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Maki assessment details are application instructions. So we should remove that entire block. Also remove "During this process, we may collect information from you through cookies..." etc. That's privacy/cookie boilerplate; remove. Thus final HTML will have sections:
About the role
... (including company description maybe)
Responsibilities
- ... list items
Qualifications
... (personal attributes, experience)