Warehouse Specialist

We need to output HTML fragment with sections: About the role (maybe heading "About the role")? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. First paragraph: "Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in across the U.S. Additional information about Kinetic is available at www.GoKinetic.com". This is company description. Could be part of "About the role"? Actually "About The Role" heading appears later. The company description is not about the role; maybe we can include as a short

  before sections? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include a short

  for company overview. That's fine. Then we have "About The Role" heading. Under that: "The Warehouse Specialist will support day-to-day warehouse operations including receiving, picking, packing, staging, and shipping. This role requires attention to detail, a safety-first mindset, and the ability to work independently and as part of a team." Then "What You’ll Do" list: bullet points. Then "Do You Have" list: requirements. Then "Even Better" list: preferred qualifications. Then "Physical Tasks – Standing Continuously: ..." etc. This is a detailed physical demands list. Should we include as a section? Possibly under "Requirements" or "Physical Requirements". The instruction says we can have sections like Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have responsibilities (What You’ll Do). We have requirements (Do You Have). We have preferred qualifications (Even Better). We have physical demands (Physical Tasks). We have equipment used. We have minimum requirements (High School diploma or equivalent. This is a safety sensitive position.) Also we have pay info: "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That's vague; not a specific number. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits later: "Our Benefits Medical, Dental, Vision Insurance Plans 401K Plan Health & Flexible Savings Account Life and AD&D, Spousal Life, Child Life Insurance Plans Educational Assistance Plan". That's specific benefits. So we should include a Benefits section. Pay: they say actual base pay will depend... not a specific figure. That's not a concrete pay statement; it's vague. According to instruction: never create Pay section unless posting actually states them. It does state that pay depends on location etc. That's still a statement about pay, but not a specific amount. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (that it depends). I'd argue that is stating something about pay, albeit not a number. However they also say "Prefer a few substantive sections over many thin ones." Might be better to omit Pay section because it's not substantive (no range). The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, but it's not a concrete figure. I'd lean to include a Pay section with that statement? But they said avoid filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The statement "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." is similar to "varies" or "commensurate with experience". It's vague. So better to omit Pay section. Schedule: not mentioned. Benefits: they list specific benefits: Medical, Dental, Vision Insurance Plans, 401K Plan, Health & Flexible Savings Account, Life and AD&D, Spousal Life, Child Life Insurance Plans, Educational Assistance Plan. That's substantive. So include Benefits section. Now we need to decide headings: About the role (maybe we already have company overview separate). Could combine company overview into About the role? The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe includes company description and role summary), Responsibilities (What You’ll Do), Requirements (Do You Have), Qualifications (Even Better?), Benefits. Could also have a section for Physical Requirements? Not in the list but could be under Requirements. However we have a lot of physical demands details; we could include them under Requirements as a list. We need to preserve ALL substantive information. So we must include the physical demands list, equipment used, etc. If we put them under Requirements, we need to include them. We also have "Minimum Requirements: High School diploma or equivalent. This is a safety sensitive position." That's also a requirement. We need to avoid duplication. Let's extract sections: Company overview: maybe a short

  before headings. About the role: Could include the role summary sentence: "The Warehouse Specialist will support day-to-day warehouse operations including receiving, picking, packing, staging, and shipping. This role requires attention to detail, a safety-first mindset, and the ability to work independently and as part of a team." Responsibilities: The bullet list under "What You’ll Do". Let's list each: - Pick, pack, and prepare orders for shipment (accuracy and speed required) - Receive incoming shipments; verify counts and inspect for damage - Label, sort, and stage inventory in designated locations - Load/unload trucks using pallet jacks, carts, and/or forklifts (if certified) - Operate basic warehouse equipment and tools safely (e.g., pallet jack, tape dispenser, scanners) - Perform inventory counts and assist with cycle counting as needed - Maintain a clean, organized, and safe work area (5S/housekeeping) - Follow company procedures for safety, quality, and shipping/receiving documentation - Other duties assigned to support warehouse operations Requirements: The bullet list under "Do You Have". Let's list: - Previous warehouse, shipping/receiving, or logistics experience preferred (not required) - Basic math and reading skills; ability to follow written and verbal instructions - Operate basic computer systems (training provided) - Ability to work in a fast-paced environment and meet productivity/quality goals - Ability to lift, up to 50 lbs. regularly. - Ability to stand/walk for extended periods; frequent bending, reaching, and twisting - Ability to work in varying warehouse conditions (temperature/noise) Even Better (preferred qualifications): - Forklift certification or experience (sit-down/stand-up/reach truck) - Shipping carrier systems experience (USPS/UPS/FedEx/LTL) Physical Tasks: a long list of percentages. We need to preserve all that info. Could be formatted as a list. Equipment Used in Job Performance/Working Environment: Ladders, Hand and Power Tools, van, Forklift and Pallet Jack Minimum Requirements: High School diploma or equivalent. This is a safety sensitive position. Benefits: list. We need to avoid duplication: The "Ability to lift, up to 50 lbs. regularly." is similar to physical tasks list which includes lifting categories. We'll keep both as they are distinct but we can combine? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep both. We need to decide how to structure: maybe have sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Physical Demands, Equipment, Minimum Requirements, Benefits. But the instruction only gave examples of headings; we can use others if needed? It says "use

  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. Safer to stick to those headings. However we have a lot of info that may not fit neatly into those categories. We could map: - About the role: company overview + role summary. - Responsibilities: What You’ll Do. - Requirements: Do You Have + Minimum Requirements (HS diploma, safety sensitive). - Qualifications: Even Better (preferred) + maybe Physical Tasks? Could be under Qualifications? But physical tasks are more like demands. - Skills: maybe not present. - Benefits: Benefits. We could also add a section for "Physical Demands" but not in examples; maybe we can incorporate into Requirements or Qualifications. However the instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So we should combine physical demands into Requirements or Qualifications. Let's think: Requirements section could include both the "Do You Have" list and the physical demands list and equipment used and minimum requirements. That might be a bit long but still substantive. Qualifications section could include Even Better (preferred). That's fine. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. Now we need to output HTML with

  headings and

  • for lists,

    for prose. We need to ensure we don't include boilerplate like EEO etc. Remove those. Now let's craft. First, a short

    for company overview: "Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in the U.S. Additional information about Kinetic is available at www.GoKinetic.com." Note: original text had "insurgent provider" maybe a typo; we should preserve as is? It says "premier insurgent provider". That seems odd but we must preserve substantive information; we should not correct typos unless it's obviously a mistake? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the exact wording: "premier insurgent provider". Keep as is. Thus: "Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in across the U.S. Additional information about Kinetic is available at www.GoKinetic.com". There's a duplicate "in across". We should preserve exactly? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It didn't say we must