Data Center Logistics Specialist

We need to output HTML fragment with sections: About the role? The description includes paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse content: - About the role: The initial description: "Join our dynamic team and become a critical enabler of the world's most advanced cloud computing infrastructure..." etc. That's prose about role. Could be "About the role". We'll put that in

. - Responsibilities: The "Key job responsibilities" bullet list: Ensure that all billing associated with the Inventory supply chain is accurate, validated and ready for processing; Assembling, addressing, stamping and arranging for the shipment of merchandise and materials; Assist in daily scheduling of deliveries and pick-ups to and from production locations; Keep precise records of all commodities going in and out of company; Understand all aspects of production, adhere to strict safety standards, maintain very high quality, and be willing and able to work on powered equipment (i.e forklift or cherry picker). That's a list. - Requirements: Basic Qualifications: High school diploma or equivalent; 2+ years of logistics or other relevant experience; 2+ years of experience in shipping & receiving inventory and warehousing practices. - Qualifications: Preferred Qualifications: Knowledge of computer hardware components and operating systems; Experience in Warehouse Management Software / Inventory Management Software proficiency; Familiar with waybills and shipping procedures with transport companies; Ability to manage work and priorities through a ticketing system and coordination with Manager; Proficient with computers and Microsoft Office (Outlook, Word, Excel). - Skills: Not explicitly separate; maybe combine with qualifications? Could create Skills section for things like "Proficient with computers and Microsoft Office", "Ability to manage work and priorities through a ticketing system". But we already have Preferred Qualifications covering many. Might not need separate Skills if content thin. But we could still create Skills for "Proficient with computers and Microsoft Office (Outlook, Word, Excel)" and "Ability to manage work and priorities through a ticketing system". However we need to avoid thin sections. Probably better to merge skills into Qualifications or Responsibilities. The instruction: Prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements (Basic Qualifications), Preferred Qualifications (maybe as Qualifications). Benefits: The posting mentions benefits: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Also mentions sign-on payments and RSUs. That's substantive. So Benefits section. - Pay: The posting includes "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location." Then later: "USA, NC, HAMLET - 26.87 - 47.06 USD hourly". That's pay range. So we have Pay info: hourly range 26.87-47.06 USD, plus sign-on payments and RSUs. So we should include Pay section. - Schedule: The posting mentions "They must be available to work on weekend shifts." Also maybe schedule not detailed beyond that. Could be considered schedule info. It's specific: must be available to work on weekend shifts. That's schedule info. So we can include Schedule section with that note. We must not include boilerplate like EEO, accommodation links, etc. Also not include Job ID, company name maybe as metadata? Could fold minor metadata into 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 could include a short paragraph at top maybe with location and job ID? But they said drop it if minor. Probably better to drop it entirely, not include. We'll not include Job ID or company name. We must preserve all substantive information. So we need to include location? The location "USA, NC, HAMLET - 26.87 - 47.06 USD hourly" includes location and pay. We already captured pay. Location maybe not needed elsewhere but could be included in About the role? Not necessary. Might be considered metadata; we could include a short

with location. But they said fold minor metadata into a short

or drop it. Location is maybe minor but could be useful. I'd include a short paragraph: "

Location: Hamlet, NC, USA.

" before sections. But we must not repeat job title as heading. No heading for job title. Now produce HTML fragment:

About the role

Join our dynamic team and become a critical enabler of the world's most advanced cloud computing infrastructure. In this role, you'll play a pivotal part in maintaining the heartbeat of our data center operations by ensuring seamless logistics and inventory management that directly support our technology deployment and maintenance efforts. The Logistics Specialist plays a critical role in inventory management, ensuring optimal stock levels are maintained to support data center build and repair operations. This position serves as the primary point of contact for parts management, including receiving, inventory control, and distribution to Data Center Technicians and Engineers. This position involves frequent lifting of materials and products. Logistics Specialists will be required to keep precise records of all commodities going in and out of the company. They must also maintain the cleanliness, organization, and safety of all workspaces. They must be available to work on weekend shifts. AWS Infrastructure Services owns the design, planning, delivery, and operation of all AWS global infrastructure. In other words, we’re the people who keep the cloud running. We support all AWS data centers and all the servers, storage, networking, power, and cooling equipment that ensure our customers have continual access to the innovation they rely on. We work on the most challenging problems, with thousands of variables impacting the supply chain — and we’re looking for talented people who want to help. You’ll join a diverse team of software, hardware, and network engineers, supply chain specialists, security experts, operations managers, and other vital roles. You’ll collaborate with people across AWS to help us deliver the highest standards for safety and security while providing seemingly infinite capacity at the lowest possible cost for our customers. And you’ll experience an inclusive culture that welcomes bold ideas and empowers you to own them to completion.

Responsibilities

• Ensure that all billing associated with the Inventory supply chain is accurate, validated and ready for processing
• Assembling, addressing, stamping and arranging for the shipment of merchandise and materials
• Assist in daily scheduling of deliveries and pick-ups to and from production locations
• Keep precise records of all commodities going in and out of company
• Understand all aspects of production, adhere to strict safety standards, maintain very high quality, and be willing and able to work on powered equipment (i.e forklift or cherry picker)

Requirements

• High school diploma or equivalent
• 2+ years of logistics or other relevant experience
• 2+ years of experience in shipping & receiving inventory and warehousing practices

Qualifications

• Knowledge of computer hardware components and operating systems
• Experience in Warehouse Management Software / Inventory Management Software proficiency
• Familiar with waybills and shipping procedures with transport companies
• Ability to manage work and priorities through a ticketing system and coordination with Manager
• Proficient with computers and Microsoft Office (Outlook, Word, Excel)

Benefits

• Comprehensive health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance, option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage)
• 401(k) matching
• Paid time off
• Parental leave
• Sign-on payments
• Restricted stock units (RSUs)

Pay

Hourly pay range: $26.87 – $47.06 USD (based on location). Total compensation includes sign-on payments and RSUs, with final amount determined by experience, qualifications, and location.

Schedule

Must be available to work weekend shifts.

We might also include a short location paragraph before sections. But we already have location in Pay. Could add a short

Location: Hamlet, NC, USA.

before About the role. That's minor metadata but okay. Let's add:

Location: Hamlet, NC, USA.

Now ensure we didn't include any boilerplate like EEO, accommodation links, etc. We removed those. Check for any repeated content: We included "They must be available to work on weekend shifts." in About the role and also Schedule section. That's duplication but okay? Might be considered duplication but we need to preserve all substantive information; duplication is okay but maybe we could remove from About the role to avoid duplication. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited. But we could keep it only in Schedule and remove from About the role to avoid redundancy. However the About the role paragraph originally includes that sentence; removing it would be summarizing away detail? It's a detail about schedule. If we move it to Schedule section, we still preserve it. It's okay to relocate. I'd remove from About the role to avoid duplication. Let's edit About the role paragraph to exclude that sentence. We'll need to adjust the paragraph accordingly. Original About the role paragraph includes: "They must also maintain the cleanliness, organization, and safety of all workspaces. They must be available to work on weekend shifts." We'll remove the second sentence. Thus About the role paragraph ends with "They must also maintain the cleanliness, organization, and safety of all workspaces." Now Schedule section will have that sentence. Now check for any other boilerplate: "NOTE: Amazon does not sponsor for immigration..." we removed. "NOTE: Lump sum stipend will be provided to eligible candidates who relocate for this position." That's a note about relocation stipend. That's substantive? It's a benefit maybe. Could be included in Benefits or Pay? It's a lump sum stipend for relocation. Could be added to Benefits as "Relocation lump sum stipend for eligible candidates." We should preserve that. So add to Benefits list. Also "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." Already in Benefits/Pay. Now also "The base salary range for this position is listed below." Already in Pay. Now also "Learn more about our benefits at https://amazon.jobs/en/benefits." That's a link, boilerplate? It's a link to benefits page; could be considered boilerplate but it's a reference. Might be considered navigation? Probably drop. Now also "If you have a disability and need a workplace accommodation..." that's EEO accommodation, drop. Now also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." drop. Now also "Amazon is an equal opportunity employer..." drop. Now also "Our inclusive culture empowers Amazonians..." maybe part of About the role? Already covered. Now also "NOTE: Lump sum stipend will be provided to eligible candidates who relocate for this position." We'll add to Benefits. Now also "Your Amazon package will include sign-on payments and restricted