DirectJobHub
Jobs · Consulting · Nevada

Engineering Operations Technician, RNO101

Amazon Web Services (AWS) · Sparks, NV · 1 mo ago
ConsultingFull-time
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 not repeat job title. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. Let's parse the description. Key sections: - Description: intro paragraph about role. - Key job responsibilities: list of duties. - Work schedule changes depending on specific site needs. Shifts can be up to 12 hours and may rotate on a predefined schedule. Some locations have on-call rotations. Role may support more than one location/site. - Physical Requirements: list. - This role supports data centers in various operational stages... (travel etc.) - Essential Requirements: travel etc. - A day in the life: more description. - About The Team: description. - Basic Qualifications: list. - Preferred Qualifications: list. - Benefits: mention comprehensive benefits list. - Pay: 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. Also mention hourly range: USA, NV, Sparks - 37.64 - 65.91 USD hourly. Thus we have Pay info. - Schedule: Work schedule changes depending on specific site needs. Shifts can be up to 12 hours and may rotate on a predefined schedule. Some locations have on-call rotations. Role may support more than one location/site. Thus schedule. - Benefits: comprehensive benefits list. - Skills? Not explicitly listed but maybe we can infer from qualifications: Microsoft Office, etc. But we should only include sections if posting has real specific content. There's no explicit "Skills" heading; we could create Skills section from qualifications? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we may include Skills if we have content. The posting includes qualifications (basic and preferred) which could be considered Requirements and Qualifications. Skills maybe not explicit; we could omit Skills if no explicit skill list. However we have Microsoft Office experience, reading/writing procedures, technical documents, engineering drawings, etc. Those could be skills. But safer to include Skills only if there is explicit skill content. The posting does not have a dedicated "Skills" bullet list; but we could treat qualifications as skills. However the instruction says "include a section ONLY when the posting has real, specific content for it". Since we have qualifications, we can put them under Qualifications. Skills maybe not needed. Thus sections: About the role (intro), Responsibilities, Requirements (maybe combine Essential Requirements and Physical Requirements?), Qualifications (Basic and Preferred), Benefits, Pay, Schedule. We need to decide what goes into Requirements. The posting has "Essential Requirements" (travel etc.) and "Physical Requirements". Could combine under Requirements. We must not invent or summarize away detail. Must preserve all substantive info. We need to output HTML fragment only, no markdown fences. Let's craft. Structure:

About the role

... intro paragraph(s) ...

Then Responsibilities:

Responsibilities

  • ... each duty ...
We need to capture all duties from "Key job responsibilities" list. List them: - Daily building rounds to monitor and record information from electrical, mechanical, and fire/life safety equipment to ensure 24/7 reliability and availability - Monitor Building Management Systems (BMS) and Electrical Power Management System (EPMS) - Assist in troubleshooting of facility and rack-level events within internal Service Level Agreements (SLA) - Perform rack installs and rack decommissioning within internal SLA - Perform PM, troubleshooting, root cause analysis, and repair of electrical and mechanical equipment - Technical writing to support change management program - Monitor daily work requests and manage to resolution, and execute projects from conception to completion - On-site support of contractors, sub-contractors and vendors, ensuring that all work performed is in accordance with established practices, procedures & local legislation Also maybe "Work schedule changes depending on specific site needs..." but that's schedule. Now Requirements: combine Essential Requirements and Physical Requirements. Essential Requirements bullet points: - 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. Physical Requirements bullet points: - Willingness and demonstrated ability to work in the following physical conditions with reasonable accommodations: - Regularly lift and/or move up to 39 pounds independently - Participate in group lifts for 40+ pounds - Maintain balance and perform construction tasks while on a ladder - Regularly walk, use hands and fingers, handle or feel, reach with hands and arms, stoop, kneel, crouch or crawl, climb stairs, twist, bend, work above shoulders, grasp, carry, push and pull objects into position - Work in an environment requiring provided ear protection Also 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." That's similar to essential requirements; we can include. We'll put all as
  • . Now Qualifications: Basic Qualifications and Preferred Qualifications. Basic: - 2+ years of electrical and mechanical facilities maintenance, or 2+ years of electrical facilities maintenance and 1+ years of mechanical facilities maintenance experience - 2+ years of Microsoft Office products and applications experience - Work flexible schedule including weekends, nights, and holidays Preferred: - 2+ years of data center engineering experience - Experience reading and writing procedures, technical documents, and engineering drawings - vocational/technical training or an associate degree or above, or 4+ years of military experience We'll list each as
  • under appropriate subheadings? The instruction only says use
    • for any list of duties/requirements/benefits. So we can have a single list for Qualifications combining basic and preferred? Might be better to separate but still list. Could do two lists under same heading? Probably fine to have one list with all qualifications, but we need to preserve distinction? Not required. We'll just list all. Now Benefits: The posting mentions comprehensive benefits list: 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 link to learn more. We'll create a list. Pay: The base salary range: USA, NV, Sparks - 37.64 - 65.91 USD hourly. Also mention sign-on payments and RSUs, final compensation based on experience, qualifications, location. We'll include that as

      maybe. Schedule: Work schedule changes depending on specific site needs. Shifts can be up to 12 hours and may rotate on a predefined schedule. Some locations have on-call rotations. Role may support more than one location/site. We'll put as

      . Now About The Team: we have a paragraph about team supporting new machine learning cluster etc. That could be part of About the role or separate section? The instruction includes About the role as a heading. We could put the initial description plus About The Team under About the role. Or we could make a separate section "About the team" but not in allowed headings list. The allowed headings include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should incorporate team description into About the role. Thus About the role paragraph(s) will include the initial description and the team description. Let's craft About the role: Paragraph 1: "Join our dynamic team and become a critical guardian of technological infrastructure! As a Data Center Engineering Technician, you'll play a pivotal role in maintaining the heartbeat of mission-critical technology infrastructure, ensuring seamless operations that power global digital experiences. Your expertise will directly contribute to maintaining an extraordinary 99.999% uptime, keeping the digital world running smoothly and efficiently. Engineering Technicians are Amazon’s front line when it comes to hands-on electrical and mechanical equipment troubleshooting. They will maintain, operate, and troubleshoot, Data Center Operation’s Mission Critical Facilities, which includes stand-by diesel generators and related fuel systems, as well as three phase electrical systems such as: switch gear, UPSs, PDUs, wet cell batteries and associated systems, CRAC, centrifugal chillers, cooling towers/water chemical system, air handlers and associated systems, pumps, & motors. 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." Paragraph 2 (About The Team): "Our team supports a new machine learning cluster at Amazon, providing the power and cooling that keep thousands of accelerator hosts online around the clock. We are hands-on engineers and technicians who work across electrical, mechanical, and controls disciplines to fix problems and improve how we operate. You will work closely with your peers and site leadership to maintain the systems that enable uninterrupted model training and inference workloads. Because this cluster is new, you will help build operational processes from the start and grow with the facility over the coming years. There is room to deepen your technical skills, take on process improvement work, and move into more senior roles in critical facility engineering." We'll combine into About the role section with two

      elements. Now ensure we don't include boilerplate like EEO, accommodation link, etc. We must remove those. 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." Those are substantive? They are notes about immigration and relocation stipend. Should we keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The notes about immigration and relocation stipend are not boilerplate; they are specific to the role. Should we keep? Probably yes, as they are substantive. However they are preceded by "NOTE:" which might be considered a note. The instruction says to preserve ALL substantive information. So we should keep them. Where to place? Could be under Requirements or maybe a separate section? Not in allowed headings. Could incorporate into Requirements (maybe as a note). But we need to preserve. Let's include them under Requirements as additional bullet points? Or as a

      under Requirements. Since they are not a list, we can put a

      . Similarly, the lump sum stipend for relocation is substantive. Thus under Requirements we can have a paragraph after the list: "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." Now also there is a line: "If

    • Similar jobs