DCO Tech

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must parse the description. First, we need to remove boilerplate: EEO, immigration note, etc. Keep substantive info. We need to produce headings

for each section. We need to use

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

  for prose. We must preserve all substantive info, not invent or summarize away detail. We must not repeat job title as heading (the page already shows it). So no heading for job title. We must not put Job ID/requisition numbers as headings; fold minor metadata into short

  or drop it. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We must include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. We need to see if posting includes Pay: Yes, there is salary range: "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 there are many lines with location and hourly rates: "USA, MD, FREDERICK - 30.00 - 54.00 USD hourly" repeated many times. So Pay section exists with specific numbers. So we can include Pay section. Schedule: The posting mentions shift work: "You will be required to work shift work that will include days/nights/weekends/holidays." Also earlier: "Work shifts longer than 8 hours to support 24/7 operations (covering both night and day shifts)." So schedule info exists. So we can include Schedule section. Benefits: The posting mentions: "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 earlier: "Your Amazon package will include sign-on payments and restricted stock units (RSUs)." So benefits exist. So we can include Benefits section. Now we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. We have description paragraphs: "Join our dynamic AWS team..." That's about the role. Could be About the role. Responsibilities: "Key job responsibilities" list: performing server rack installations, hardware break-fix, troubleshooting network issues, responding to operational incidents, routine network/server hardware/OS repairs, serving as primary contact point, performing on-call duties, participating in scheduled maintenance and change management, contributing to documentation and process improvement, helping to interview, train and onboard new team members. Also earlier: "Data Center Technician position involves in-depth hardware and network diagnostics followed by physical repair as well as participating in an on-call rotation." That's also responsibilities. Requirements: There's "Physical Requirements" list: lifting up to 40 pounds, working in cramped/elevated locations, bending, lifting, stretching, reaching, standing/walking up to 8+ hours, ascending/descending ladders, stairs, gangways, work in industrial environment, work shifts longer than 8 hours to support 24/7 operations (covering both night and day shifts). Also "Essential Requirements": ability to travel/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 varies, candidates must be able to travel (over 50 miles) or commute (less than 50 miles) to active data center sites as required. Also "Basic Qualifications": Experience in computer networking, Experience with computer hardware troubleshooting and repair. "Preferred Qualifications": list of many items: can work in cramped spaces or elevated locations while adhering to health & safety guidelines, experience dealing effectively with customers during problem resolution and operating efficiently under pressure, experience managing work and priorities through a ticketing system, experience with cabling infrastructure best practices and methodologies, experience working in a data center environment (racking and stacking gear, cable management, hot/cold aisle containment). Also "A day in the life" bullet list: Take ownership of technical issues, show strong aptitude for troubleshooting and problem solving, solve problems at root, maintain SLAs through proactive issue detection, biased to act, improve effectiveness through process innovation. That could be Skills or Qualifications? Might be considered Skills. We need to map to sections: About the role (overview), Responsibilities (duties), Requirements (maybe essential requirements like travel, physical), Qualifications (basic and preferred), Skills (maybe the day-in-life abilities), Benefits, Pay, Schedule. We must not create sections with filler. Ensure each section has substantive content. We need to avoid duplication. Use

  • for lists. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all details from the posting, but we can group them. We must not include boilerplate like EEO, immigration note, etc. Also remove duplicated lines (the salary lines repeated for many locations). We need to keep the pay info but we can summarize? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not summarize away detail; we need to keep the specific pay ranges and locations? However, the pay lines are duplicated many times for each location. If we keep all, it's a huge list but still substantive. However, we might consider that preserving all substantive info means we should not drop the location-specific pay rates. But we could combine them into a list? That's still preserving detail. The instruction says "do NOT invent or summarize away detail." Summarizing away detail would be like saying "pay range $30-54/hour across multiple locations" which loses the location detail. So we should keep each location line. But there are many duplicates: e.g., "USA, MD, FREDERICK - 30.00 - 54.00 USD hourly" appears twice (once with uppercase Frederick, once with lowercase). Also many VA locations repeated with uppercase/lowercase. We could keep them as is; it's okay. But we also have location lines repeated for each location; we could keep them. We also have "Company - Amazon Data Services, Inc. - A19 Job ID: A10425916". This is minor metadata; we can fold into a short

    or drop it. The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include a

    with that info. Now we need to avoid including EEO etc. Also remove "NOTE: Amazon does not sponsor for immigration..." and "NOTE: Lump sum stipend will be provided to eligible candidates who relocate for this position." That's substantive? It's a note about relocation stipend. That could be part of Benefits or maybe a separate note. It's substantive; we should keep it. It mentions lump sum stipend for relocation. That's a benefit. So we can include under Benefits. Also "If you have a disability and need a workplace accommodation..." is EEO/accommodation; that's boilerplate? It's about accommodations; could be considered EEO but it's about disability accommodation. Might be considered legal boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove that accommodation paragraph. Also "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." That's application instruction; remove. Also "Learn more about our benefits at https://amazon.jobs/en/benefits." That's application instruction; remove. Also "Our inclusive culture empowers Amazonians..." that's maybe okay but could be considered boilerplate? It's about culture; maybe keep? It's not EEO. It's about inclusive culture; could be part of About the role or Benefits? Might be okay to keep but we need to avoid duplication. It appears earlier in "Why AWS?" section. That's substantive about AWS. Might be okay to keep under About the role. But we need to be careful not to include too much fluff. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the descriptive paragraphs about AWS, team, culture, mentorship, work-life balance, etc. Those are substantive. Thus About the role could include the initial paragraph about joining AWS team, plus the "Why AWS?" paragraph, plus "About The Team" subsections (Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance). That seems like a lot but it's substantive. But we need to avoid duplication: The "About The Team" section includes headings like Diverse Experiences, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. Those are subheadings within the posting. We could treat them as part of About the role, maybe as

    paragraphs. We need to output only HTML fragment, no markdown. We'll 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 Technician position involves in-depth hardware and network diagnostics followed by physical repair as well as participating in an on-call rotation. 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.

    Then maybe a paragraph about Why AWS? Could be included in About the role as well. But we might also create a separate section "About AWS"? Not in list. So we keep under About the role. Now Responsibilities:

    Responsibilities

    • Performing server rack installations
    • Hardware break-fix on various components
    • Troubleshooting network issues
    • Responding to operational incidents that impact service availability
    • Carrying out routine network, server hardware, and operating system repairs to contribute to the overall availability of AWS services
    • 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 interview, train and onboard new team members
    We could also include the earlier line about in-depth hardware and network diagnostics followed by physical repair and on-call rotation, but that's covered. Now Requirements: We need to capture