Data Center Technician, DCC Communities, DCO Tech

We need to output HTML fragment with sections: About the role? The description includes description 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 the posting. Content: - Description: introductory paragraphs about role, dynamic AWS team, etc. That could be "About the role". So we can have

About the role

with paragraphs. - Key job responsibilities: list of duties. That's Responsibilities. - A day in the life: maybe also responsibilities? Could be part of responsibilities but we can include as part of responsibilities or separate? The instruction: Use headings only when posting has real specific content. We have responsibilities list; we can put them under Responsibilities. - Basic Qualifications: that's Requirements? Could be Requirements or Qualifications. There's also Preferred Qualifications. So we can have Requirements (basic) and Qualifications (preferred) maybe. Or combine? The headings list includes Requirements, Qualifications, Skills. We need to decide. We have Basic Qualifications (1+ years experience, HS diploma, flexible schedule). Preferred Qualifications (knowledge of network design, associate's degree, data center experience, ticketing system). Also Skills maybe implied: hardware troubleshooting, network, etc. Could create Skills section from responsibilities? But we already have responsibilities. We have Pay: The posting includes "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. USA, GA, Atlanta - 27.98 - 48.99 USD hourly". So we have pay range and benefits. So we need Benefits and Pay sections. Schedule: The posting mentions "Work a flexible schedule including weekends, nights, and holidays" under Basic Qualifications. Also "This team works in an environment that operates 24/7." So schedule info exists. So we can have Schedule section. We need to avoid boilerplate: EEO, equal opportunity, accommodation links, etc. Remove those. Also remove Job ID line. We need to preserve all substantive information. Let's extract content. About the role: The initial description paragraphs: "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." We can put that as paragraphs under About the role. Responsibilities: "Key job 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" We need to split into list items. Each sentence maybe separate. Let's list: - 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 Also "A day in the life" could be additional responsibilities but we can incorporate maybe as part of responsibilities or separate? Could be separate but we don't have a heading for "A day in the life". Could add as part of responsibilities or maybe as a separate section like "Typical Day". But not in allowed headings. So we incorporate into responsibilities. Requirements: Basic Qualifications: - 1+ years of computer/server hardware troubleshooting or related IT experience - High school or equivalent diploma - Work a flexible schedule including weekends, nights, and holidays We could also include "Traveling within and outside of the regional work area is required" maybe as requirement? But it's in description; we could keep in About the role. Qualifications: 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) - Experience in a data center or other critical environment - Experience managing work and priorities through a ticketing system Skills: Could extract from responsibilities: hardware troubleshooting, network troubleshooting, documentation, communication, etc. But we may not need a separate Skills section if content is thin. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills and include those details in Responsibilities or Requirements. Benefits: The posting mentions: "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." Also "Lump sum stipend will be provided to eligible candidates who relocate for this position." That's a benefit. Also maybe other benefits not listed. So we can list: - Employee Assistance Program (EAP) - Mental Health Support - Medical Advice Line - 401(k) matching - Lump sum stipend for eligible relocation candidates Pay: The posting includes pay range: "USA, GA, Atlanta - 27.98 - 48.99 USD hourly". Also mention that starting pay based on experience etc. So we can put: - Hourly pay range: $27.98 – $48.99 (USD) for Atlanta, GA location - Final starting pay based on experience, qualifications, and location Schedule: Info: "Work a flexible schedule including weekends, nights, and holidays" (already in Requirements). Also "This team works in an environment that operates 24/7." Also "Traveling within and outside of the regional work area is required." So schedule section could include: - Flexible schedule including weekends, nights, and holidays - 24/7 operations environment - Travel required within and outside regional work area We need to avoid duplication: The flexible schedule already in Requirements; but we can still mention in Schedule. However duplication may be okay but we should avoid repeating same content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication but better to avoid redundancy. We could keep schedule details separate from requirements: maybe move flexible schedule to Schedule and not include in Requirements. But Requirements currently includes flexible schedule; we could keep it there and also mention in Schedule? Might be duplicate. Perhaps better to put flexible schedule under Schedule, and keep Requirements focused on experience and education. Let's adjust. Requirements (Basic Qualifications): - 1+ years of computer/server hardware troubleshooting or related IT experience - High school or equivalent diploma Schedule: - Flexible schedule including weekends, nights, and holidays - 24/7 operations environment - Travel required within and outside regional work area Now Responsibilities as above. Qualifications (Preferred): - Knowledge of network design, protocols and Layer 1/2 troubleshooting - Associate's degree 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 Benefits: - Employee Assistance Program (EAP) - Mental Health Support - Medical Advice Line - 401(k) matching - Lump sum stipend for eligible relocation candidates Pay: - Hourly pay range: $27.98 – $48.99 (USD) for Atlanta, GA location - Final starting pay based on experience, qualifications, and location About the role: the introductory paragraphs. We need to output HTML fragment only, no /. Use

for headings,

for prose,

• for lists. We need to ensure we don't include any boilerplate like EEO, accommodation links, etc. Let's craft. About the role: Could be multiple paragraphs. We'll split into maybe two paragraphs for readability but not required. We'll include the description text as is, but ensure we don't include the NOTE about immigration sponsorship and lump sum stipend? Actually lump sum stipend is a benefit, we already captured. The NOTE about immigration sponsorship: "NOTE: Amazon does not sponsor for immigration, including for H-1B, TN, and other non-immigrant visas, for this role." That's likely boilerplate/legal? It's a note about immigration sponsorship; might be considered boilerplate? It's not EEO but it's a note about visa sponsorship. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This note about immigration sponsorship could be considered legal boilerplate. Safer to remove it. Also the NOTE about lump sum stipend we already captured as benefit; we can keep that benefit but remove the NOTE line. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "If you have a disability..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Learn more about our benefits at https://hiring.amazon.com/why-amazon/benefits." but we already captured benefits; we can keep the benefit list but not the link. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The link is not substantive? It's a reference; maybe we can drop it as it's just a link. The benefit details are substantive; we can keep them without the link. Also remove "The starting pay for this position is listed below. Final starting pay will be based on factors including experience, qualifications, and location." That's substantive about pay; we already have pay section. Now construct HTML. Let's write:

  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,