Seasonal: 4am Inbound (Stocking) (T2130)

We need to output HTML fragment with sections: Pay (since we have starting hourly rate and pay range). Possibly also Benefits? There's a link to benefits but no specific benefits listed; we should not create Benefits section unless posting actually states them. It says "Find competitive benefits from financial and education to well-being and beyond at ..." That's a generic statement, not specific benefits. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state Pay (starting hourly rate and pay range). So we include Pay section. Benefits: they mention a URL but not specific benefits; we should not create Benefits section. Schedule: they mention flexible work schedule (e.g., nights, weekends and holidays) and regular attendance necessary. That is schedule info. Should we create Schedule section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state flexible work schedule, so we can include Schedule section. However we need to see if we should include it as a separate section or fold into other sections? The instruction: Prefer a few substantive sections over many thin ones. We have Pay and Schedule both substantive. Could also have Responsibilities? The posting includes description of roles, what we are looking for, skills, etc. Those could go under Responsibilities or Requirements. We need to decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content. We have: - Pay: Starting hourly rate $18.00, Pay range $18.00 - $27.00 per hour. - Schedule: Flexible work schedule (e.g., nights, weekends and holidays) and regular attendance necessary. - Responsibilities: Could be the description of roles: Seasonal Specialty Sales Roles, Seasonal Service & Engagement, Seasonal General Merchandise & Food Sales, plus list of roles (Seasonal Guest Advocate, etc.) and tasks like stocking, setting, selling, etc. Also "We work efficiently and as a team to deliver for our guests", "Providing service to our guests that makes them say I LOVE TARGET! excites you", etc. Those are more like responsibilities/what you'll do. - Requirements/Skills: The list of skills: Welcoming and helpful attitude, learn and adapt to current technology needs, work both independently and with a team, resolve guest questions quickly, attention to detail and follow multi-step processes, accurately handle cash register operations, climb ladders, scan/handle/move merchandise efficiently and safely including lifting up to 40 pounds, flexible work schedule (already schedule). Also "You aren’t looking for Monday thru Friday job where you are at a computer all day…" maybe not a requirement. - Qualifications: Not explicitly listed; maybe "Experience in retail business fundamentals..." etc. That could be qualifications. We need to avoid boilerplate like EEO, ADA, application deadline, etc. Remove those. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: list of roles, the description of each role type, the skills list, etc. We need to format using

for section headings,

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

  for prose. We should not repeat job title as heading. No Job ID. We need to output only HTML fragment. Let's structure:

  Pay

  The starting hourly rate is $18.00 USD per hour. The pay range is $18.00 USD – $27.00 USD per hour.

  Schedule

  A flexible work schedule is required, including nights, weekends, and holidays, with regular attendance expected.

  Responsibilities

  • Provide tailored suggestions and solutions through active selling and compelling visual merchandising presentations (Seasonal Specialty Sales Roles).
  • Welcome, thank, and exceed guest service expectations by focusing on guest interaction and recovery (Seasonal Service & Engagement).
  • Ensure product is set, in-stock, accurately priced and signed on the sales floor to enable a consistent guest experience (Seasonal General Merchandise & Food Sales).
  • Stock, set, and sell Target products.
  • Work efficiently as a team to deliver for guests.
  • Provide service that makes guests say “I LOVE TARGET!”.
  But we also have list of specific roles: Seasonal Guest Advocate, Seasonal General Merchandise Expert, Seasonal Fulfillment Expert, Seasonal Style Consultant, Seasonal Inbound Expert, Seasonal Food & Beverage Expert, Seasonal Tech Consultant. Could be included under Responsibilities as bullet list. Better to have a bullet list of roles and maybe separate duties. We need to preserve all substantive information; we can combine. Let's create a
  with each role as a bullet, and maybe also include duties. But we must not invent; we can list them as given. Also include "We work efficiently and as a team to deliver for our guests" etc. Now Requirements/Skills:

  Requirements

  • Welcoming and helpful attitude toward guests and other team members.
  • Ability to learn and adapt to current technology needs.
  • Capable of working both independently and with a team.
  • Resolve guest questions quickly on the spot.
  • Attention to detail and ability to follow multi‑step processes.
  • Accurately handle cash register operations.
  • Climb up and down ladders.
  • Scan, handle, and move merchandise efficiently and safely, including frequently lifting or moving merchandise up to 40 pounds.
  • Flexible work schedule (e.g., nights, weekends and holidays) and regular attendance necessary.
  But schedule already covered; we could avoid duplication. However schedule is also a requirement. Might be okay to keep schedule section separate and not duplicate in requirements. But the instruction says preserve ALL substantive information; we can keep schedule in its own section and not repeat in requirements. However the schedule bullet is also a requirement; but we can keep it only under Schedule section to avoid duplication. However the requirement list includes schedule; if we omit it, we might be losing that detail. But we already have schedule section covering it. So we can omit from requirements to avoid duplication. Now Qualifications: The posting includes "At Target We Believe Our Team Members Have Meaningful Experiences That Help Them Build And Develop Skills For a Career. These Roles Can Provide You With The: Knowledge of guest service fundamentals and experience supporting a guest first culture across the store Experience in retail business fundamentals: department sales trends, inventory management, and process efficiency and improvement Experience executing daily/weekly workload to support business priorities and deliver on sales goals". That seems like qualifications/experience you will gain. Could be under Qualifications or maybe under About the role. But we have no "About the role" section yet. Could create "About the role" with that paragraph. Let's see: The posting includes "ALL ABOUT TARGET Working at Target means helping all families discover the joy of everyday life. We bring that vision to life through our values and culture. Learn more about Target here." That's generic fluff; maybe we can include as About the role? But it's not specific to the role; it's about Target. Might be considered boilerplate? It's not EEO/legal but it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's generic fluff. Might be okay to keep as part of About the role? However we should prefer few substantive sections over many thin ones. This paragraph is not specific to the role; maybe we can omit it as it's not substantive for the role. The instruction says preserve ALL substantive information; this is not substantive about the job. So we can drop it. Similarly "ALL ABOUT SEASONAL JOBS" includes descriptions of role types; that is substantive. We already captured that in Responsibilities. Now "Find competitive benefits from financial and education to well-being and beyond at https://corporate.target.com/careers/benefits." That's generic; we already decided not to create Benefits section. Now "Benefits Eligibility Please paste this url into your preferred browser to learn about benefits eligibility for this role: https://tgt.biz/BenefitsForYou_G | Pegue esta URL en su navegador preferido para obtener información sobre la elegibilidad de este puesto para recibir beneficios: https://tgt.biz/BenefitsForYou_G". That's a link; we could include as a link in Benefits? But we shouldn't create Benefits section unless posting actually states them. It does state benefits eligibility URL, but not specific benefits. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a benefits eligibility URL, which is about benefits. However the rule says "unless the posting actually states them" meaning actual benefits details? The example: "commensurate with experience", "not specified", "N/A", "varies", "TBD" are not to be used. The URL is a pointer to benefits; but we don't have actual benefits listed. I'd argue we should not create a Benefits section because we don't have specific benefits details. The URL is just a reference; we could include it as a link in a paragraph maybe under a generic "More info" but we shouldn't create a section. Safer to omit. Now "Americans With Disabilities Act (ADA) In compliance with state and federal laws, Target will make reasonable accommodations for applicants with disabilities. If a reasonable accommodation is needed to participate in the job application or interview process, please reach out to candidate.accommodations@HRHelp.Target.com. Non-accommodation-related requests, such as application follow-ups or technical issues, will not be addressed through this channel." That's EEO/legal boilerplate; remove. "Application deadline is : 12/10/2026" - application instruction; remove. Now we have sections: Pay, Schedule, Responsibilities, Requirements (skills). Possibly also Qualifications (the "These Roles Can Provide You With The:" list). That is about what you will gain; could be considered Qualifications or maybe "What you'll gain". But we have no heading for that; we could use "Qualifications". However the posting says "These Roles Can Provide You With The:" then list of knowledge/experience. That's more like what you will gain, not qualifications required. Could be under "What you'll learn" but not a standard heading. We could treat as "Qualifications" but that might be misleading. Better to use "What you'll gain" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put that under Qualifications (though it's about what you'll gain). Or we could put under About the role. But we already omitted About the role due to generic fluff. However we could use About the role for the specific description of what the role offers (the "These Roles Can Provide You With The:" list). That seems appropriate: About the role describes the role and what you'll experience. Let's do that. Thus:

  About the role

  These roles provide you with knowledge of guest service fundamentals and experience supporting a guest‑first culture across the store, experience in retail business fundamentals (department sales trends, inventory management, and process efficiency and improvement), and experience executing daily/weekly workloads to support business priorities and deliver on sales goals.

  Now Responsibilities: we can include the role type descriptions and the list of specific roles. Let's craft Responsibilities section with bullet points: - Seasonal Specialty Sales Roles: provide tailored suggestions and solutions through active selling and