Data Center Engineering Operations Technician , DCEO Engr 3
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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. Prefer few substantive sections over many thin ones.
We need to parse the description.
Key sections:
- Description (intro) – maybe "About the role" or just a paragraph.
- Key job responsibilities – list.
- 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. => This is schedule info.
- Physical Requirements – list.
- A day in the life – paragraph.
- About The Team – paragraph.
- Why AWS? – paragraph.
- Diverse Experiences – paragraph.
- Inclusive Team Culture – paragraph.
- Mentorship & Career Growth – paragraph.
- Work/Life Balance – paragraph.
- Basic Qualifications – list.
- Preferred Qualifications – list.
- Pay: "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, OH, HILLIARD - 32.88 - 57.50 USD hourly"
Thus we have pay range and benefits mention.
We need to include Benefits section if posting actually states them. It mentions benefits: EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Also says "Learn more about our benefits at ...". So we can include Benefits section with those items.
Schedule: we have schedule info: "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." So we can include Schedule section.
Pay: we have pay range: "USA, OH, HILLIARD - 32.88 - 57.50 USD hourly". Also mention that final starting pay based on factors. So we can include Pay section with that range.
We must not create sections with filler like "commensurate with experience". We have actual pay range, so okay.
We need to avoid duplication. Also remove boilerplate like EEO statement, accommodation link, etc. 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, please contact your Recruiting Partner." Also remove "Company - Amazon Data Services, Inc. Job ID: A10552696". Might fold minor metadata into short
or drop it. Probably drop it.
We need to preserve all substantive information. So we need to keep the description paragraphs, responsibilities list, physical requirements, day in the life, about the team, why AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance, basic qualifications, preferred qualifications, benefits, schedule, pay.
We need to decide which sections to combine to avoid many thin ones. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some similar sections: e.g., "About The Team", "Why AWS?", "Diverse Experiences", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance" could be combined into a single "About AWS" section? But they are distinct headings; but we could combine them under a heading like "About AWS" with subpoints? However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are typical headings, but we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings when appropriate, but we can also have other headings? Probably we should stick to those headings where applicable. For the many paragraphs about AWS culture, we could put them under "About the role" or "About AWS"? The example list includes "About the role". So we could use "About the role" heading for the introductory description and maybe the team/AWS culture paragraphs. But we also have "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have no explicit "Skills" section; we could treat "Preferred Qualifications" as skills? But we have "Preferred Qualifications" list; maybe we can put under "Qualifications". Basic Qualifications could be under "Requirements". Preferred Qualifications could be under "Qualifications". Skills maybe not present; we could omit.
We need to avoid creating sections with filler. So we need to decide which headings to actually output.
We have substantive content for:
- About the role (intro description, day in the life, about the team, why AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance). That's a lot; we could combine into About the role.
- Responsibilities (key job responsibilities list).
- Requirements (basic qualifications list).
- Qualifications (preferred qualifications list).
- Benefits (benefits list: EAP, Mental Health Support, Medical Advice Line, 401(k) matching).
- Pay (pay range).
- Schedule (schedule info).
- Physical Requirements maybe could be under Requirements? But we have a separate Physical Requirements list; we could incorporate into Requirements or maybe a separate "Requirements" heading includes both basic qualifications and physical requirements. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements include both basic qualifications and physical requirements. Or we could have a separate "Physical Requirements" but that's not in the example list; but we could still use for any heading; the example list is not exhaustive. However to keep few sections, we could merge physical requirements into Requirements.
Thus we could have sections:
About the role
(contains intro paragraphs, day in the life, about the team, why AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance)
Responsibilities
(list)
Requirements
(basic qualifications + physical requirements)
Qualifications
(preferred qualifications)
Benefits
(list)
Pay
(pay range)
Schedule
(schedule info)
We need to ensure we don't repeat job title as heading. Not using.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus for each section we need to decide if content is prose or list.
About the role: multiple paragraphs; we can wrap each paragraph in
. Could combine into multiple
elements.
Responsibilities: list of duties; we can use
- each.
Requirements: we have basic qualifications list (1+ years of Microsoft Office..., work flexible schedule..., 1+ years of electrical facilities maintenance, or 1+ years of mechanical facilities). Also physical requirements list (regularly lift..., participate in group lifts..., maintain balance..., etc). We could combine into one list? But they are different types; but we can still make a single
with all items. Or we could separate into two under same heading? Probably one list is fine.
Qualifications: preferred qualifications list (2+ years of data center engineering experience, Experience reading and writing procedures..., Associate's degree in related field, or technical degree in related field). Use .
Benefits: list of benefits (EAP, Mental Health Support, Medical Advice Line, 401(k) matching). Use .
Pay: we have pay range and note about final starting pay based on factors. That's prose; we can put in .
Schedule: schedule info prose;
.
We also need to include location? The posting includes "USA, OH, HILLIARD - 32.88 - 57.50 USD hourly". That's location and pay. We could include location in Pay section or maybe separate? Not required. We'll include location in Pay
.
We must preserve all substantive information. So we need to ensure we don't drop any details.
Let's extract all substantive content:
Intro paragraphs:
"How would you like to be a part of Earth’s most customer-centric company? You would work with teams of front-line responders who support the operations of some of the world’s most powerful data centers. Our Data Center Engineering Operations team maintain and operate our critical infrastructure systems so that they are prepared to stand up against any situation. AWS has the world’s largest cloud computing portfolio. As an Amazonian you will work in some of the most sophisticated, safe, and secure data centers in the world. Our Engineering Operations Technicians (EOT’s) help keep them that way by working with the brightest minds from around the globe to help test and implement the newest technology and work practices to meet the demands of a changing market. We have a passion for learning and evolving, it’s how we have helped define ourselves as leaders in the industry. Let’s work hard, have fun, and make history!"
That's a paragraph.
Key job responsibilities list:
- 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
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:
- Willingness and demonstrated ability to work in the following physical conditions with reasonable accommodations:
Actually the list includes:
- 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
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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. Prefer few substantive sections over many thin ones. We need to parse the description. Key sections: - Description (intro) – maybe "About the role" or just a paragraph. - Key job responsibilities – list. - 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. => This is schedule info. - Physical Requirements – list. - A day in the life – paragraph. - About The Team – paragraph. - Why AWS? – paragraph. - Diverse Experiences – paragraph. - Inclusive Team Culture – paragraph. - Mentorship & Career Growth – paragraph. - Work/Life Balance – paragraph. - Basic Qualifications – list. - Preferred Qualifications – list. - Pay: "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, OH, HILLIARD - 32.88 - 57.50 USD hourly" Thus we have pay range and benefits mention. We need to include Benefits section if posting actually states them. It mentions benefits: EAP, Mental Health Support, Medical Advice Line, 401(k) matching. Also says "Learn more about our benefits at ...". So we can include Benefits section with those items. Schedule: we have schedule info: "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." So we can include Schedule section. Pay: we have pay range: "USA, OH, HILLIARD - 32.88 - 57.50 USD hourly". Also mention that final starting pay based on factors. So we can include Pay section with that range. We must not create sections with filler like "commensurate with experience". We have actual pay range, so okay. We need to avoid duplication. Also remove boilerplate like EEO statement, accommodation link, etc. 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, please contact your Recruiting Partner." Also remove "Company - Amazon Data Services, Inc. Job ID: A10552696". Might fold minor metadata into short
or drop it. Probably drop it. We need to preserve all substantive information. So we need to keep the description paragraphs, responsibilities list, physical requirements, day in the life, about the team, why AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance, basic qualifications, preferred qualifications, benefits, schedule, pay. We need to decide which sections to combine to avoid many thin ones. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine some similar sections: e.g., "About The Team", "Why AWS?", "Diverse Experiences", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance" could be combined into a single "About AWS" section? But they are distinct headings; but we could combine them under a heading like "About AWS" with subpoints? However the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are typical headings, but we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings when appropriate, but we can also have other headings? Probably we should stick to those headings where applicable. For the many paragraphs about AWS culture, we could put them under "About the role" or "About AWS"? The example list includes "About the role". So we could use "About the role" heading for the introductory description and maybe the team/AWS culture paragraphs. But we also have "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We have no explicit "Skills" section; we could treat "Preferred Qualifications" as skills? But we have "Preferred Qualifications" list; maybe we can put under "Qualifications". Basic Qualifications could be under "Requirements". Preferred Qualifications could be under "Qualifications". Skills maybe not present; we could omit.
We need to avoid creating sections with filler. So we need to decide which headings to actually output.
We have substantive content for:
- About the role (intro description, day in the life, about the team, why AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance). That's a lot; we could combine into About the role.
- Responsibilities (key job responsibilities list).
- Requirements (basic qualifications list).
- Qualifications (preferred qualifications list).
- Benefits (benefits list: EAP, Mental Health Support, Medical Advice Line, 401(k) matching).
- Pay (pay range).
- Schedule (schedule info).
- Physical Requirements maybe could be under Requirements? But we have a separate Physical Requirements list; we could incorporate into Requirements or maybe a separate "Requirements" heading includes both basic qualifications and physical requirements. The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements include both basic qualifications and physical requirements. Or we could have a separate "Physical Requirements" but that's not in the example list; but we could still use for any heading; the example list is not exhaustive. However to keep few sections, we could merge physical requirements into Requirements.
Thus we could have sections:
About the role
(contains intro paragraphs, day in the life, about the team, why AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance)
Responsibilities
(list)
Requirements
(basic qualifications + physical requirements)
Qualifications
(preferred qualifications)
Benefits
(list)
Pay
(pay range)
Schedule
(schedule info)
We need to ensure we don't repeat job title as heading. Not using.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus for each section we need to decide if content is prose or list.
About the role: multiple paragraphs; we can wrap each paragraph in
. Could combine into multiple
elements.
Responsibilities: list of duties; we can use
- each.
Requirements: we have basic qualifications list (1+ years of Microsoft Office..., work flexible schedule..., 1+ years of electrical facilities maintenance, or 1+ years of mechanical facilities). Also physical requirements list (regularly lift..., participate in group lifts..., maintain balance..., etc). We could combine into one list? But they are different types; but we can still make a single
with all items. Or we could separate into two under same heading? Probably one list is fine.
Qualifications: preferred qualifications list (2+ years of data center engineering experience, Experience reading and writing procedures..., Associate's degree in related field, or technical degree in related field). Use .
Benefits: list of benefits (EAP, Mental Health Support, Medical Advice Line, 401(k) matching). Use .
Pay: we have pay range and note about final starting pay based on factors. That's prose; we can put in .
Schedule: schedule info prose;
.
We also need to include location? The posting includes "USA, OH, HILLIARD - 32.88 - 57.50 USD hourly". That's location and pay. We could include location in Pay section or maybe separate? Not required. We'll include location in Pay
.
We must preserve all substantive information. So we need to ensure we don't drop any details.
Let's extract all substantive content:
Intro paragraphs:
"How would you like to be a part of Earth’s most customer-centric company? You would work with teams of front-line responders who support the operations of some of the world’s most powerful data centers. Our Data Center Engineering Operations team maintain and operate our critical infrastructure systems so that they are prepared to stand up against any situation. AWS has the world’s largest cloud computing portfolio. As an Amazonian you will work in some of the most sophisticated, safe, and secure data centers in the world. Our Engineering Operations Technicians (EOT’s) help keep them that way by working with the brightest minds from around the globe to help test and implement the newest technology and work practices to meet the demands of a changing market. We have a passion for learning and evolving, it’s how we have helped define ourselves as leaders in the industry. Let’s work hard, have fun, and make history!"
That's a paragraph.
Key job responsibilities list:
- 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
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:
- Willingness and demonstrated ability to work in the following physical conditions with reasonable accommodations:
Actually the list includes:
- 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
for any heading; the example list is not exhaustive. However to keep few sections, we could merge physical requirements into Requirements.
Thus we could have sections:
About the role
(contains intro paragraphs, day in the life, about the team, why AWS, diverse experiences, inclusive team culture, mentorship & career growth, work/life balance)
Responsibilities
(list)
Requirements
(basic qualifications + physical requirements)
Qualifications
(preferred qualifications)
Benefits
(list)
Pay
(pay range)
Schedule
(schedule info)
We need to ensure we don't repeat job title as heading. Not using.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus for each section we need to decide if content is prose or list.
About the role: multiple paragraphs; we can wrap each paragraph in
. Could combine into multiple
elements.
Responsibilities: list of duties; we can use
- each.
Requirements: we have basic qualifications list (1+ years of Microsoft Office..., work flexible schedule..., 1+ years of electrical facilities maintenance, or 1+ years of mechanical facilities). Also physical requirements list (regularly lift..., participate in group lifts..., maintain balance..., etc). We could combine into one list? But they are different types; but we can still make a single
with all items. Or we could separate into two under same heading? Probably one list is fine.
Qualifications: preferred qualifications list (2+ years of data center engineering experience, Experience reading and writing procedures..., Associate's degree in related field, or technical degree in related field). Use .
Benefits: list of benefits (EAP, Mental Health Support, Medical Advice Line, 401(k) matching). Use .
Pay: we have pay range and note about final starting pay based on factors. That's prose; we can put in .
Schedule: schedule info prose;
.
We also need to include location? The posting includes "USA, OH, HILLIARD - 32.88 - 57.50 USD hourly". That's location and pay. We could include location in Pay section or maybe separate? Not required. We'll include location in Pay
.
We must preserve all substantive information. So we need to ensure we don't drop any details.
Let's extract all substantive content:
Intro paragraphs:
"How would you like to be a part of Earth’s most customer-centric company? You would work with teams of front-line responders who support the operations of some of the world’s most powerful data centers. Our Data Center Engineering Operations team maintain and operate our critical infrastructure systems so that they are prepared to stand up against any situation. AWS has the world’s largest cloud computing portfolio. As an Amazonian you will work in some of the most sophisticated, safe, and secure data centers in the world. Our Engineering Operations Technicians (EOT’s) help keep them that way by working with the brightest minds from around the globe to help test and implement the newest technology and work practices to meet the demands of a changing market. We have a passion for learning and evolving, it’s how we have helped define ourselves as leaders in the industry. Let’s work hard, have fun, and make history!"
That's a paragraph.
Key job responsibilities list:
- 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
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:
- Willingness and demonstrated ability to work in the following physical conditions with reasonable accommodations:
Actually the list includes:
- 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
for prose. Thus for each section we need to decide if content is prose or list. About the role: multiple paragraphs; we can wrap each paragraph in
. Could combine into multiple
elements. Responsibilities: list of duties; we can use
- each.
Requirements: we have basic qualifications list (1+ years of Microsoft Office..., work flexible schedule..., 1+ years of electrical facilities maintenance, or 1+ years of mechanical facilities). Also physical requirements list (regularly lift..., participate in group lifts..., maintain balance..., etc). We could combine into one list? But they are different types; but we can still make a single
- with all items. Or we could separate into two
- under same heading? Probably one list is fine.
Qualifications: preferred qualifications list (2+ years of data center engineering experience, Experience reading and writing procedures..., Associate's degree in related field, or technical degree in related field). Use
- .
Benefits: list of benefits (EAP, Mental Health Support, Medical Advice Line, 401(k) matching). Use
- .
Pay: we have pay range and note about final starting pay based on factors. That's prose; we can put in
. Schedule: schedule info prose;
. We also need to include location? The posting includes "USA, OH, HILLIARD - 32.88 - 57.50 USD hourly". That's location and pay. We could include location in Pay section or maybe separate? Not required. We'll include location in Pay
. We must preserve all substantive information. So we need to ensure we don't drop any details. Let's extract all substantive content: Intro paragraphs: "How would you like to be a part of Earth’s most customer-centric company? You would work with teams of front-line responders who support the operations of some of the world’s most powerful data centers. Our Data Center Engineering Operations team maintain and operate our critical infrastructure systems so that they are prepared to stand up against any situation. AWS has the world’s largest cloud computing portfolio. As an Amazonian you will work in some of the most sophisticated, safe, and secure data centers in the world. Our Engineering Operations Technicians (EOT’s) help keep them that way by working with the brightest minds from around the globe to help test and implement the newest technology and work practices to meet the demands of a changing market. We have a passion for learning and evolving, it’s how we have helped define ourselves as leaders in the industry. Let’s work hard, have fun, and make history!" That's a paragraph. Key job responsibilities list: - 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 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: - Willingness and demonstrated ability to work in the following physical conditions with reasonable accommodations: Actually the list includes: - 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