Data Center Technician
for sections like 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, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions. Must not create sections with filler like "commensurate with experience". Must only include sections when posting has real specific content.
We need to parse the description.
Key parts:
- Description intro: "Join our dynamic AWS team..." etc. That's prose about role.
- "NOTE: PDX is an AWS GovCloud region..." includes note about US citizenship requirement effective Feb 24 2026. Also note about lump sum stipend for relocation.
- "Key job responsibilities" bullet list.
- "Physical Requirements" bullet list.
- "Essential Requirements" bullet list.
- "A day in the life" prose.
- "About The Team" with subsections: Why AWS, Diverse Experiences, Inclusive Team Culture, Mentorship and Career Growth.
- "Basic Qualifications" bullet list.
- "Preferred Qualifications" bullet list.
- "Amazon is an equal opportunity employer..." that's EEO boilerplate, should be removed.
- "If you have a disability..." accommodation link - also boilerplate, remove.
- "If the country/region you’re applying in isn’t listed..." remove.
- "The starting pay for this position is listed below. Final starting pay will be based on factors including experience, qualifications, and location. Starting Day 1 of employment, Amazon offers EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Learn more about our benefits at https://hiring.amazon.com/why-amazon/benefits." This includes pay and benefits info.
- "USA, WA, MOSES LAKE - 27.98 - 48.99 USD hourly" pay range.
- "Company - Amazon Data Services, Inc." maybe minor metadata.
- "Job ID: A10538991" drop.
We need to decide sections.
Potential sections:
- About the role (intro description). Could be "About the role" heading.
- Responsibilities (Key job responsibilities).
- Requirements (maybe combine Essential Requirements and Basic Qualifications? But we have separate sections: Requirements and Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Responsibilities: Key job responsibilities list.
- Requirements: maybe Essential Requirements + Physical Requirements? Or maybe Requirements for eligibility (travel, etc). We'll include travel/commute etc.
- Qualifications: Basic Qualifications and Preferred Qualifications.
- Skills: maybe not explicitly listed; we could omit if no specific skills section. Could combine network knowledge etc under Qualifications.
- Benefits: Starting Day 1 benefits (EAP, Mental Health Support, Medical Advice Line, 401(k) matching) plus maybe lump sum stipend for relocation.
- Pay: The hourly range.
- Schedule: mention shift work, weekends, nights, holidays, flexible schedule, 24/7 operations, on-call duties, etc.
We must not create sections with filler. Ensure each section has substantive content.
We must not repeat job title.
We must not include boilerplate like EEO, accommodation, etc.
We must preserve all substantive info: that includes notes about GovCloud citizenship requirement, lump sum stipend, travel requirements, physical requirements, etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft.
Structure:
About the role
Join our dynamic AWS team and become a critical guardian of global cloud infrastructure! You'll play a pivotal role in maintaining the heartbeat of the world's most innovative technology platform, ensuring seamless data center operations that power millions of businesses and services worldwide. Data Center Technicians should be willing to work both independently and with a team. Work prioritization, organizational skills, effective communication, and the ability to react quickly are critical to success. In addition to hardware and network repair, candidates will install equipment, create documentation, innovate solutions, and fix problems within the data center space. This team works in an environment that operates 24/7. Traveling within and outside of the regional work area is required. 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 of 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.
But note: The "NOTE: PDX is an AWS GovCloud region..." and "NOTE: Lump sum stipend will be provided to eligible candidates who relocate for this position." Should we include in About the role or maybe a separate section? Could be part of About the role or maybe a separate "Important Notes". But we only have allowed headings; we could incorporate into About the role paragraph. We need to preserve that info. So add after the intro: "NOTE: PDX is an AWS GovCloud region. As required by our contracts with the federal government, effective February 24, 2026, logical access to the AWS GovCloud region will be restricted to Amazon employees who are U.S. Citizens. (GovCloud may NOT be accessed from outside of the United States). NOTE: Lump sum stipend will be provided to eligible candidates who relocate for this position." We'll include that as a separatemaybe. Now Responsibilities:
Responsibilities
- Performing server rack installations, hardware break-fix on various components, troubleshooting network issues, and responding to operational incidents that impact service availability, escalating to senior technicians and management as needed/required
- Serving as a primary contact point for both internal and external stakeholders, including engineers, software developers, vendors, and contractors
- Performing on-call duties and participating in scheduled maintenance and change management activities
- Contributing to documentation and process improvement initiatives based on your analysis of operational issues
- Helping to train and onboard new team members
Requirements
- Ability to travel to or commute between data center locations as needed
- Willingness to temporarily work at alternative sites during training periods or until assigned facility is operational
- Travel frequency will vary based on business needs and operational status of assigned facility
- Candidates must be able to travel (over 50 miles) or commute (less than 50 miles) to active data center sites as required by business needs
- Regularly lift and/or move up to 40 pounds; and participate in group lifts for 41+ pounds
- Working in cramped and/or elevated locations
- Bending, lifting, stretching, and reaching
- Standing and walking for up to 8+ hours a day
- Ascending and descending ladders, stairs, and gangways safely and without limitation
- Work in a noisy environment
- Work shifts longer than 8 hours to support 24/7 operations (covering both night and day shifts)
Qualifications
- High school or equivalent diploma
- 1+ years of computer/server hardware troubleshooting or related IT experience
- Work a flexible schedule including weekends, nights, and holidays
Preferred Qualifications:
- Knowledge of network design, protocols and Layer 1/2 troubleshooting
- Associate's degree in a relevant field (e.g., Computer Science, Networking Engineering), or experience in a relevant field (e.g., Computer Science, Networking Engineering)
- Experience in a data center or other critical environment
- Experience managing work and priorities through a ticketing system
for section headings; we could have separate headings for Basic Qualifications and Preferred Qualifications but those are not in the allowed list. However we could still use for them if they are substantive; but the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we could still use other headings if they are substantive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Safer to stick to those. So we will have only one Qualifications section, containing both basic and preferred qualifications. We can separate with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive; we could still use other headings if they are substantive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Safer to stick to those. So we will have only one Qualifications section, containing both basic and preferred qualifications. We can separate with
or but not headings.
We'll do:
Basic Qualifications: Preferred Qualifications:Qualifications
Now Benefits: we have lump sum stipend, Day 1 benefits (EAP, Mental Health Support, Medical Advice Line, 401(k) matching). Also maybe mention "Learn more about our benefits at https://hiring.amazon.com/why-amazon/benefits." but that's a link; we can keep as part of benefits.
We'll create:
Benefits