DCO Tech

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the description. Key sections: - Description (intro) maybe "About the role"? The description includes overview: "Join our dynamic AWS team...". Could be "About the role". We'll put that as

About the role

with

containing the overview paragraphs. - Responsibilities: "Key job responsibilities" list: bullet points. We'll create

Responsibilities

with

• each. - Physical Requirements: list of physical demands. Could be under "Physical Requirements". Might be considered "Requirements" or "Physical Requirements". We have a section "Physical Requirements". We'll treat as

  Physical Requirements

  with
  . - Essential Requirements: travel etc. Could be under "Requirements". We'll combine maybe "Requirements" includes essential requirements and basic qualifications? But we have separate "Basic Qualifications" and "Preferred Qualifications". So we can have sections: "Basic Qualifications", "Preferred Qualifications". Also "Skills" maybe not separate; but we could include "Skills" if there is content. There's mention of skills like troubleshooting, etc. But we have "Preferred Qualifications" covering many skill items. We'll follow the instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They want us to use those headings if content exists. We have content for About the role, Responsibilities, Requirements (maybe essential requirements + physical?), Qualifications (basic and preferred), Benefits, Pay (salary range), Schedule (shift work). We'll need to decide. We must not create sections with filler like "commensurate with experience". We have actual pay range: "USA, MD, FREDERICK - 30.00 - 54.00 USD hourly" repeated for many locations. So we can include Pay section with that range. Schedule: mention "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 we have schedule info. Benefits: mention "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also link. So we can include Benefits. Qualifications: we have Basic Qualifications and Preferred Qualifications. Could combine under Qualifications heading with sub-sections? But instruction: use

  for section headings. Could have

  Qualifications

  and then inside maybe

  for basic and

  for preferred? Or we could separate Basic Qualifications and Preferred Qualifications as separate headings if they exist. The instruction list includes Qualifications as a possible heading. It didn't list Basic Qualifications or Preferred Qualifications separately. So we should use Qualifications heading and include both basic and preferred content. Skills: maybe not needed if covered under Qualifications. But we could still include Skills if there is specific skill list not covered. However we have many skill items in Preferred Qualifications. Might be okay to not have separate Skills. Requirements: we have Essential Requirements (travel) and Physical Requirements. Could combine under Requirements heading. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information, not invent or summarize away detail. Must include all details. We need to be careful to not omit any substantive info. Let's extract all substantive paragraphs. Intro 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 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 NOTE about immigration and lump sum stipend: "NOTE: Amazon does not sponsor for immigration, including for H-1B, TN, and other non-immigrant visas, for this role. NOTE: Lump sum stipend will be provided to eligible candidates who relocate for this position." These are substantive; we should keep them. Where to place? Could be under About the role or maybe a separate note. We'll include them in About the role paragraph. Then "Key job responsibilities" list: - Performing server rack installations, hardware break-fix on various components, troubleshooting network issues, responding to operational incidents that impact service availability, and 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'll put each as
  • . Then "Physical Requirements" list: - Lifting and moving material up to 40 pounds each - 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 an industrial environment - Work shifts longer than 8 hours to support 24/7 operations (covering both night and day shifts). Then note: "This role supports data centers in various operational stages. The position may be assigned to a facility still under development, which could require travel to established locations for training until your designated site becomes fully operational." Then "Essential 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. Then "A day in the life" bullet list (maybe not required but substantive). It includes: - Take ownership of technical issues brought by their customer base, engaging other teams when needed to drive resolution - Show a strong aptitude for troubleshooting and problem solving - Solve problems at their root and step back to understand the broader context - Maintain service level agreements through the implementation of proactive issue detection and reporting - Are biased to act in the absence of direction or support - Improve effectiveness through process innovation Then "You will be required to work shift work that will include days/nights/weekends/holidays." Then "About The Team" subsections: Diverse Experiences, Why AWS?, Inclusive Team Culture, Mentorship & Career Growth, Work/Life Balance. These are substantive but maybe could be considered part of About the role or separate? The instruction says to include sections only when posting has real specific content. We could include a section "About the Team" but not in the list of allowed headings. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not include About the Team. So we should not create a heading for About the Team; we could incorporate its content into About the role or maybe omit? But we must preserve ALL substantive information. If we omit About The Team content, we lose substantive info. So we need to include it somewhere. Perhaps we can put it under About the role as additional paragraphs. That's allowed: we can expand About the role to include team description. So we will incorporate those paragraphs into About the role. Then "Basic Qualifications": - Experience in computer networking - Experience with computer hardware troubleshooting and repair "Preferred Qualifications": - Can work in cramped spaces or in 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) Then EEO boilerplate etc to remove. Then compensation: "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. 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. Learn more about our benefits at https://amazon.jobs/en/benefits." Then list of locations with pay ranges: many lines each "USA, MD, FREDERICK - 30.00 - 54.00 USD hourly" etc. We need to preserve all substantive info; we could summarize as "Pay range: $30.00 - $54.00 USD hourly (various locations)". But that might be summarizing away detail (the specific locations). The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep each location line? That seems excessive but maybe required. However we could keep them as a list under Pay section. That would preserve detail. The instruction says "Prefer a few substantive sections over many thin ones." But we must not lose detail. We could combine location lines into a
    with each location as
    • . That preserves detail while not being many thin sections (still one Pay section). That seems acceptable. Thus Pay section:

      Pay

      • USA, MD, FREDERICK - 30.00 - 54.00 USD hourly
      ... etc for each location. We need to list all location lines from the text. Let's extract them: From the text: USA, MD, FREDERICK - 30.00 - 54.00 USD hourly USA, MD, Frederick - 30.00 - 54.00 USD hourly USA, OH, COLUMBUS - 30.00 - 54.00 USD hourly USA, OH, Columbus - 30.00 - 54.00 USD hourly USA, VA, Ashburn - 30.00 - 54.00 USD hourly USA, VA, Dulles - 30.00 - 54.00 USD hourly USA, VA, FREDERICKSBURG - 30.00 - 54.00 USD hourly USA, VA, Fredericksburg