Supervisor - DC Operations 1-Monday-Thursday
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove "About Us" maybe? The instruction: "Prefer a few substantive sections over many thin ones." We need to decide which sections to include based on content. The posting includes: - "Your Role JOB DESCRIPTION As a Supervisor in DC operations, you will have the opportunity to lead and develop your own team of AE Associates. You will be responsible for engaging your team to maintain the highest levels of safety, quality, attendance, performance, and engagement. Daily responsibilities will include priority setting, maintaining work standards, and implementing methods to enhance workflow by identifying issues and expediting solutions." That's about the role. - "Your Responsibilities" bullet list: many items. - "Physical Requirements" list. - "Qualifications" list: Bachelor's Degree, Two years supervisory experience, Excellent interpersonal skills..., Intermediate computer skills..., Schedule flexibility..., Ability to step in..., Bonus: Bilingual in Spanish. - "Pay/Benefits Information": paragraph about pay determined by factors, benefits list, PTO varies, discretionary bonuses. - "About Us": description of AEO. - "Inclusion, Diversity, Equity and Access at AEO": description. - EEO boilerplate: remove. - "Applications will be accepted until the Apply Before date...": remove (application instructions). - "JOB INFO Job Identification 33289 Job Category : Supply Chain Posting Date : 2026-09-23T14:42:48+00:00 Job Schedule : Full time Locations : Ottawa, KS, United States": This is metadata; we should not put as headings; we can fold minor metadata into a short
or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph with location, schedule, maybe posting date? But they said drop minor metadata. Probably we can include a short
with location and schedule (full time) as they are substantive? The location and schedule are relevant. The posting date maybe minor. We'll include a short paragraph: "Location: Ottawa, KS, United States. Schedule: Full time." Or we could drop it. But they said preserve ALL substantive information; location and schedule are substantive. So include them in a
. Now sections: We have content for About the role (Your Role), Responsibilities, Qualifications (includes education, experience, skills, schedule flexibility, bonus), Physical Requirements (maybe could be part of Requirements? But we have a section for Requirements; we could put Physical Requirements under Requirements. However we have a separate "Physical Requirements" list. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could map: - About the role: from "Your Role JOB DESCRIPTION ..." - Responsibilities: from "Your Responsibilities" list. - Requirements: could include Physical Requirements? Or maybe we treat Physical Requirements as part of Requirements. But we also have Qualifications separate. The list of headings includes Requirements and Qualifications separate. So we need to decide what goes where. Typically, Requirements might be things like physical requirements, schedule flexibility, ability to step in, etc. Qualifications might be education, experience, skills. Skills could be separate but we may not have a distinct skills section beyond what's in qualifications. Since we have both Qualifications and Skills headings available, we could put education/experience under Qualifications, and interpersonal/computer skills under Skills. But the posting lumps them together. We need to preserve all info; we can split. Let's extract: Qualifications (education/experience): - Bachelor's Degree in Business Management, Logistics or equivalent work experience - Two years supervisory experience, preferably in a warehouse or distribution center environment Skills: - Excellent interpersonal skills, oral and written communication skills, and strong attention to detail - Intermediate computer skills including Google suite and Kronos Time-keeping Software Solutions - Schedule flexibility, including nights and weekends - Ability to step in and support other departments as needed - Bonus: Bilingual in Spanish Physical Requirements could be under Requirements (maybe a separate heading "Requirements" for physical). Or we could put Physical Requirements under Requirements. The heading list includes Requirements, so we can use that for physical requirements. Benefits: we have benefits list in Pay/Benefits Information. Pay: we have pay determination statement. Schedule: we have schedule flexibility mentioned under skills, but also job schedule full time from metadata. Could create a Schedule section with info about full time and flexibility. But we must not create sections with filler like "commensurate with experience". We have actual content. Thus sections: - About the role (h3) - Responsibilities (h3) - Requirements (h3) for Physical Requirements - Qualifications (h3) for education/experience - Skills (h3) for interpersonal, computer, schedule flexibility, ability to step in, bilingual bonus - Benefits (h3) for benefits list - Pay (h3) for pay determination - Schedule (h3) for job schedule full time (maybe also mention flexibility? but we already have schedule flexibility in Skills; but we could keep schedule section just for full time). However we might avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. Having many sections may be thin. Perhaps we combine some. We could combine Qualifications and Skills into one "Qualifications" section, but we have separate headings allowed. However we could still use only Qualifications and skip Skills if we put all under Qualifications. But we have a heading for Skills; we could omit it if we think it's thin. But we have specific skill items; we could put them under Qualifications as sub-bullets. That would reduce number of sections. Similarly, we could combine Pay and Benefits into one "Compensation and Benefits" but headings are separate; we could still use both if they have content. Schedule: we have full time from metadata; we could include that in a short paragraph maybe not need a separate heading. But we have schedule flexibility already in Skills/Qualifications. So maybe we don't need a Schedule section. Thus we could have sections: About the role, Responsibilities, Requirements (physical), Qualifications (education/experience/skills), Benefits, Pay. That's 6 sections. Check if we have content for each: - About the role: yes. - Responsibilities: yes list. - Requirements: physical requirements list. - Qualifications: education, experience, interpersonal skills, computer skills, schedule flexibility, ability to step in, bilingual bonus. - Benefits: list of health care, wellness, 401k, life/disability, stock purchase, paid time off, sick leave, parental leave, discretionary bonuses. - Pay: statement about actual starting pay determined by factors. We should not include boilerplate like "Subject to eligibility requirements, associates may receive..." that's part of benefits; we keep. We need to format lists with
- . For prose, use
. We must not repeat job title as heading. We must not include Job ID etc. We'll drop metadata. We must not include EEO etc. We must not include "About Us" etc? That's substantive but not in headings list; we could maybe include under About the role? But we already have About the role section for role description. The "About Us" is company description; could be considered extra but not required headings. The instruction: "Prefer a few substantive sections over many thin ones." Including About Us would add another section; maybe we can drop it as it's not required by headings list and could be considered boilerplate? It's descriptive but not about the role. The instruction says preserve ALL substantive information; but we can maybe incorporate into About the role? However About the role is about the role, not company. But we could add a short paragraph after About the role? But we must not create new headings not in list unless we think it's needed. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings; we can use others if needed but better to follow examples. So we likely should not add About Us heading. Thus we drop About Us and Inclusion etc. Now produce HTML:
About the role
As a Supervisor in DC operations, you will have the opportunity to lead and develop your own team of AE Associates. You will be responsible for engaging your team to maintain the highest levels of safety, quality, attendance, performance, and engagement. Daily responsibilities will include priority setting, maintaining work standards, and implementing methods to enhance workflow by identifying issues and expediting solutions.
Responsibilities
- Lead the day-to-day operations in a fast paced, E-Commerce distribution environment
- Maintain a motivating and positive leadership presence through active associate engagement
- Promote a culture of safety among associates by prioritizing safety protocols
- Drive success by motivating, teaching, and holding team members accountable
- Conduct daily shift briefings
- Ensure adequate staffing for each shift based on resources and associate skill-sets
- Provide associates with meaningful developmental opportunities
- Proactively identify and lead process improvement initiatives
- Regularly evaluate associate performance, including annual review
- Maintain documentation on associate attendance, productivity, behavior, and safety
- Ensure fiscal responsibility through labor and supply cost control
- Promote positive team relationships through effective communication and recognition
Requirements
- Stand for long periods of time and walk continuously
- Pull merchandise from multiple levels of shelving or move merchandise as needed
- Climb stairs and perform work at platform heights up to 60 feet
- Lift up to 50lbs. Specific weight requirements may vary within each department
Qualifications
- Bachelor's Degree in Business Management, Logistics or equivalent work experience
- Two years supervisory experience, preferably in a warehouse or distribution center environment
- Excellent interpersonal skills, oral and written communication skills, and strong attention to detail
- Intermediate computer skills including Google suite and Kronos Time-keeping Software Solutions
- Schedule flexibility, including nights and weekends
- Ability to step in and support other departments as needed
- Bonus: Bilingual in Spanish
Benefits
- Health care benefits (including medical, vision, and dental)
- Wellness benefits
- 401(k) retirement benefits
- Life and disability insurance
- Employee stock purchase program
- Paid time off
- Paid sick leave
- Parental leave and benefits
- Discretionary bonuses and other incentives
Pay
Actual starting pay is determined by various factors, including but not limited to relevant experience and location.
We should not include schedule section. Check for any leftover boilerplate: we removed EEO, About Us, Inclusion, Application instructions, Job ID etc