Stock Associate, PT (6am-10am)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". So we need to parse the posting. Content: - Values & Innovation At Under Armour... (some intro about values). This is like "About the role"? Actually it's about company values, maybe "About the role" or "Company Overview". We can treat as "About the role" or "Company". The instruction: 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 values paragraph. - Purpose of Role: "Ready to move fast..." This is like a description. Could be part of "About the role" or separate "Purpose". But we can include under "About the role" as prose. - Your Impact We Count On Our Stock Associates To ... list of duties. That's responsibilities. So we need a Responsibilities section with

  • items. - Requirements: list of requirements. So Requirements section with
    • . - Benefits & Perks: list of benefits. So Benefits section with
      • . Also includes pay "$15.00 - $16.90". That's Pay section. Also schedule? Not explicitly given besides flexible schedule. There's mention "Ability to work a flexible schedule to meet the needs of the business, including holidays, nights, and weekends". That's schedule info. So we can have Schedule section with that statement. - Also "Our Commitment to Equal Opportunity" is boilerplate EEO, should be removed. - Also "If you are a current Under Armour teammate, apply to this position on the Internal Career Site Here." That's application instruction, remove. - Also "Other tasks as assigned by management" is part of responsibilities. - Also "Priority consideration to return for future seasonal hiring periods" is a benefit? Could be under Benefits. - Also "Opportunities for regular part-time and full-time roles" benefit. - Also "High-energy environment, working alongside people who appreciate the power of a team" benefit. - Also "Opportunities for professional development and advancement" benefit. - Also "Generous employee discount" benefit. - Also "Ability to participate in special contests with the opportunity to win merchandise and other exclusive prizes" benefit. Thus we need sections: About the role (values + purpose), Responsibilities, Requirements, Benefits, Pay, Schedule. Check if any Qualifications or Skills separate? Requirements already includes skills like communication, ability to lift, etc. Could also have Skills but we can combine into Requirements. The instruction says prefer few substantive sections over many thin ones. So we can keep Requirements as is, not separate Skills. Now we need to output HTML fragment only, no /, no markdown fences. We must ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive info. Let's extract exact text. Values paragraph: "Values & Innovation At Under Armour, we are committed to empowering those who strive for more, and the company's values - Act Sustainably, Celebrate the Wins, Fight on Together, Love Athletes and Stand for Equality - serve as both a roadmap for our teams and the qualities expected of every teammate. Our Values define and unite us, the beliefs that are the red thread that connects everyone at Under Armour. Our values are rallying cries, reminding us why we're here, and fueling everything we do. Our pursuit of better begins with innovation and with our team's mission of being the best. With us, you get the freedom to go further - no matter your role. That means developing, delivering, and selling the state-of-the-art products and digital tools that make top performers even better." We can keep that as prose under About the role. Purpose of Role: "Purpose of Role Ready to move fast and make an impact? As a Stock Associate, you're the engine behind our store's energy - keeping shelves stocked, products flowing, and customers happy. If you're all about staying organized, working with a great team, and making things happen behind the scenes, this is your moment. Let's grow together!" We can include that as prose after values. Now Responsibilities list: From "Your Impact We Count On Our Stock Associates To Process merchandise shipmentsReplenish the sales floor Manage markdowns and re-ticketing, stock transfers and damaged goodsEnsure the store, the sales floor, and stockrooms are cleaned and organizedDeliver omni-channel requests in line with UA process and policy through digital experienceModel the UA service culture and customer expectationsSupport, understand and adhere to Under Armour's visual standards to maximize merchandise presentations when flowing product from the stockroom to the sales floorEngage in, maintain and support safety standards on the sales floor and in the stockroom; communicate safety concerns to store leadershipAware of and follows Loss Prevention policies; advise management of any unusual internal or external activityCollaborate with teammates to achieve store goalsAccountable for self-development, while seizing growth opportunities to increase performance Other tasks as assigned by management" We need to split into sensible items. The original text seems concatenated without punctuation. We need to parse into separate duties. Let's manually split: - Process merchandise shipments - Replenish the sales floor - Manage markdowns and re-ticketing, stock transfers and damaged goods - Ensure the store, the sales floor, and stockrooms are cleaned and organized - Deliver omni-channel requests in line with UA process and policy through digital experience - Model the UA service culture and customer expectations - Support, understand and adhere to Under Armour's visual standards to maximize merchandise presentations when flowing product from the stockroom to the sales floor - Engage in, maintain and support safety standards on the sales floor and in the stockroom; communicate safety concerns to store leadership - Aware of and follows Loss Prevention policies; advise management of any unusual internal or external activity - Collaborate with teammates to achieve store goals - Accountable for self-development, while seizing growth opportunities to increase performance - Other tasks as assigned by management We'll output each as
      • . Now Requirements list: "To be considered for this role, you must meet these minimum requirements: At least 18 years old, or 16 years old in the EMEA Region Ability to work a flexible schedule to meet the needs of the business, including holidays, nights, and weekendsLocal language fluency required; basic English is a plusStrong communication skillsAbility to perform essential functions of the roleCan stand, lift, walk, bend and lift cartons weighing up to 25 lbs./12 kgs during each work shift with or without accommodation Comfortable with or willing to learn technology (such as computers, hand-held and mobile devices)" We need to split: - At least 18 years old, or 16 years old in the EMEA Region - Ability to work a flexible schedule to meet the needs of the business, including holidays, nights, and weekends - Local language fluency required; basic English is a plus - Strong communication skills - Ability to perform essential functions of the role - Can stand, lift, walk, bend and lift cartons weighing up to 25 lbs./12 kgs during each work shift with or without accommodation - Comfortable with or willing to learn technology (such as computers, hand-held and mobile devices) Now Benefits & Perks list: "Benefits & Perks Generous employee discount Ability to participate in special contests with the opportunity to win merchandise and other exclusive prizes High-energy environment, working alongside people who appreciate the power of a team Opportunities for professional development and advancementPriority consideration to return for future seasonal hiring periods Opportunities for regular part-time and full-time roles $15.00 - $16.90" We need to separate benefits and pay. Pay is "$15.00 - $16.90". Benefits list: - Generous employee discount - Ability to participate in special contests with the opportunity to win merchandise and other exclusive prizes - High-energy environment, working alongside people who appreciate the power of a team - Opportunities for professional development and advancement - Priority consideration to return for future seasonal hiring periods - Opportunities for regular part-time and full-time roles Pay: $15.00 - $16.90 (likely hourly wage). We'll make a Pay section with that. Schedule: from requirement "Ability to work a flexible schedule to meet the needs of the business, including holidays, nights, and weekends". That's schedule info. We'll put in Schedule section. Now we need to ensure we don't duplicate schedule info also in Requirements. It's okay to have it in both? The instruction says preserve ALL substantive information; we can keep it in Requirements and also have Schedule section. But maybe better to keep it only in Schedule and remove from Requirements to avoid duplication? However the requirement list includes that as a requirement; we should preserve it. The instruction says do not repeat job title as heading, but doesn't forbid repeating content. It says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it in Requirements as well. Having it also in Schedule is okay but might be considered duplication. However it's not prohibited. But we could move it to Schedule and remove from Requirements to avoid duplication while still preserving info. But the requirement list originally includes it; if we remove it, we lose that requirement from the Requirements section. But we could keep it in Requirements and also have Schedule section with same info; that duplicates but preserves. The instruction didn't forbid duplication. It says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not inventing or summarizing away, it's just repeating. Might be acceptable. However they might prefer not to have redundant sections. But they said "Prefer a few substantive sections over many thin ones." Duplication could be considered thin? Not sure. I think it's safer to keep the schedule info only in Requirements and not create a separate Schedule section unless there is additional schedule info beyond that. But the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The posting does have specific schedule content: "Ability to work a flexible schedule to meet the needs of the business, including holidays, nights, and weekends". That's specific. So we could create a Schedule section with that sentence. However then we would have that content also in Requirements. That's okay. Alternatively we could move it to Schedule and remove from Requirements to avoid duplication, but then we would lose that requirement from Requirements section. However the requirement is about schedule flexibility; it's still a requirement. If we move it, we still preserve it (just in Schedule). The requirement list would lose that item, but we could keep it as part of Requirements but maybe rephrase? The instruction says preserve ALL substantive information; moving it to another section still preserves it. So we could keep it only in Schedule and not duplicate. But then the Requirements section would be missing that item. However the requirement is still present in the document (just in Schedule). So overall preserved. I'd lean to keep it only in Schedule to avoid duplication and keep sections thin? But they said prefer few substantive sections over many thin ones. Having a Schedule section with just one sentence might be thin. Better to keep it within Requirements and not create a separate Schedule section. However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must create a Schedule section if schedule info exists; it's optional. So we can choose not to create Schedule section if we think it's thin. But they also list Schedule as an example heading.