Data Center Operations - Day/Flex
for 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 as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate etc.
We need to parse the posting.
Content:
- Title: Data Center Operations — Day/Flexible On-site in Pittsburgh, Pennsylvania | Monday–Friday, 9:00 a.m.–5:00 p.m. Eastern
- Description: This position normally works Monday through Friday from 9:00 a.m. to 5:00 p.m. Eastern. During another team member’s planned absence or a scheduled operational event, the employee may temporarily work alternate hours, including evening or weekend coverage. Schedule changes will ordinarily be communicated in advance. When alternate coverage is required, the employee’s regular workdays or hours will be adjusted accordingly. This is not a permanently rotating-shift position.
- Who We Are: description of Teraswitch.
- What To Expect: description of role.
- Responsibilities include: list of responsibilities.
- What Our New Team Member Will Need: list of requirements/experience.
- Helpful Experience: list of helpful experience.
- Compensation and Benefits: mentions competitive pay, benefits list.
- Success in This Role: description of success criteria.
We need sections: About the role (maybe "Who We Are" or "What To Expect"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings.
We have:
- About the role: could be "What To Expect" description.
- Responsibilities: the list under "Responsibilities include:".
- Requirements: maybe "What Our New Team Member Will Need" (mandatory experience).
- Qualifications: maybe overlapping with Requirements? Could combine? But we need separate sections only if content exists. Could treat "Helpful Experience" as Qualifications or Skills? Actually Skills could be separate: maybe "Helpful Experience" includes skills like Linux admin, etc. Could put under Skills.
- Benefits: list under Compensation and Benefits.
- Pay: mention "competitive pay". That's specific enough? It says "Along with competitive pay, full-time Teraswitch employees are eligible for the following benefits". So we have pay info: competitive pay (no specifics). According to rule: never create Pay section unless posting actually states them. It does state "competitive pay". That's a statement, albeit vague. Should we include Pay section? It says "competitive pay". That's real content, albeit not a number. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive pay" is not exactly filler? It's vague but still a statement. Might be okay. But we could also incorporate pay into Benefits section? The instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they ask to use headings for Pay and Benefits separately if content exists. Since we have both, we could include both.
- Schedule: we have schedule details: Monday-Friday 9-5, flexible, occasional alternate hours. That's specific. So we can have Schedule section.
Now we need to output HTML fragment only, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So no heading for the title.
We must not include Job ID etc.
We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to preserve all substantive information; do not invent or summarize away detail.
Thus we need to include all details from the posting, but we can format them.
Let's extract sections:
About the role: Could be "What To Expect" paragraph(s). Also maybe "Who We Are" could be About the company, but heading "About the role" maybe includes role description. We'll put the "What To Expect" prose under About the role.
Responsibilities: list under "Responsibilities include:" (multiple lines). We'll put each as
- .
Requirements: "What Our New Team Member Will Need" (mandatory experience). We'll list each bullet as
- .
Qualifications: maybe we could treat "Helpful Experience" as Qualifications? But Qualifications often similar to Requirements. However we have both Requirements and Helpful Experience. Could treat Helpful Experience as Qualifications (preferred but not required). Or we could treat Helpful Experience as Skills. The instruction includes Skills heading. So we can put Helpful Experience under Skills.
Thus:
- Requirements: mandatory experience.
- Skills: helpful experience (Linux admin, etc.)
- Benefits: list of benefits.
- Pay: mention competitive pay.
- Schedule: schedule description.
We also have "Who We Are" description of company. Could we put that under About the role? Or maybe we could add an "About the company" but not in allowed headings. Since only allowed headings are those listed, we should fit it somewhere. Could include in About the role section as a brief intro. The About the role heading could encompass both role description and company overview. That seems okay.
Thus About the role section will contain:
- Who We Are paragraph(s)
- What To Expect paragraph(s)
We need to preserve all substantive info, so we need to include both.
We'll put them in
tags.
Now we need to format lists.
Let's extract the exact text for each piece.
Who We Are:
"Teraswitch is on a mission to provide the highest performance, lowest latency bare metal servers in the world. With 20 data center locations around the world, Teraswitch has served thousands of customers across 185 countries. Founded by Brendan Mannella and headquartered in Pittsburgh, Pennsylvania, Teraswitch is a privately held infrastructure company operating a growing global bare metal platform."
What To Expect:
"As a member of Data Center Operations, you will own infrastructure incidents, customer requests, maintenance activities, deployments, and operational projects from intake through verified completion. This is primarily a remote infrastructure operations role—not a primarily hands-on data-center technician position. Most work is performed through monitoring systems, tickets, server-management interfaces, technical documentation, and coordination with customers, internal engineering teams, colocation facilities, vendors, contractors, and remote-hands providers. Approximately 10% of the role may involve physical work including server assembly, component replacement, cabling, rack-and-stack work, and equipment maintenance. This role requires someone who can investigate problems independently, communicate clearly with technical and nontechnical stakeholders, create precise technical procedures, manage multiple concurrent priorities, and remain accountable until work is completed and validated."
Now Responsibilities list: It's a long paragraph starting with "Responsibilities include:" then a series of sentences each starting with a verb. We need to split into list items. Let's extract each bullet:
- Own infrastructure incidents, customer requests, maintenance activities, deployments, and operational projects from intake through verified completion.
- Monitor infrastructure alerts, support requests, maintenance activities, and active operational issues.
- Investigate reported server, network, power, cooling, connectivity, deployment, and monitoring problems.
- Gather and interpret information from logs, monitoring platforms, tickets, management interfaces, internal systems, customers, and on-site technicians.
- Perform incident triage, take safe and documented corrective actions, and escalate service-affecting issues when appropriate.
- Communicate directly and professionally with customers during incidents, technical investigations, maintenance events, and service requests.
- Write precise Methods of Procedure, implementation plans, validation steps, rollback instructions, runbooks, and remote-hands directions.
- Translate technical requirements into clear, executable instructions for colocation technicians, contractors, vendors, and internal teams.
- Coordinate and direct remote-hands technicians at Teraswitch data center locations around the world.
- Remain accountable for remote work by confirming the correct equipment, reviewing evidence, tracking progress, validating results, and ensuring documentation is complete.
- Coordinate scheduled installations, migrations, maintenance events, hardware replacements, shipments, and other operational projects.
- Work with facility personnel to address power, cooling, cross-connect, cabling, access, and other facility-provided services.
- Coordinate vendor warranty technicians and ensure hardware issues are resolved promptly and correctly.
- Maintain clear ticket updates, incident timelines, project notes, escalation records, and actionable shift handoffs.
- Collaborate with Software, Network, Systems, Facilities, Logistics, and other internal teams.
- Maintain accurate records of infrastructure, hardware changes, completed work, and physical inventory.
- Identify recurring problems and improve documentation, procedures, tooling, and operational workflows.
- Execute documented server-management, recovery, deployment, and maintenance procedures.
- Perform occasional hands-on server assembly, rack-and-stack work, cabling, diagnostics, upgrades, and component replacement.
- Provide temporary coverage on alternate Operations schedules during planned team absences or scheduled operational events.
- Follow established security, change-management, escalation, validation, and access-control procedures.
Now Requirements (What Our New Team Member Will Need):
List:
- Three or more years of experience in data center operations, infrastructure support, systems support, technical operations, or a similar role.
- Demonstrated ability to write detailed technical procedures that another technician can execute without additional interpretation.
- Experience troubleshooting infrastructure remotely using logs, monitoring platforms, tickets, command-line tools, server-management interfaces, or information supplied by on-site personnel.
- Experience independently owning incidents, service requests, maintenance activities, or technical projects through completion.
- Strong written communication and the ability to provide clear updates to customers, vendors, contractors, and internal technical teams.
- Ability to prioritize multiple concurrent customer, infrastructure, and operational issues.
- Sound judgment regarding service impact, change control, escalation, rollback, and validation.
- Working knowledge of server hardware, network equipment, structured cabling, and data center facility services.
- Ability to distinguish between gathering information, taking corrective action, escalating an issue, and transferring ownership.
- Ability to follow technical procedures precisely and verify that completed work produced the intended result.
- Strong troubleshooting, organization, and time-management skills.
- Ability to safely lift, move, rack, and work around data center equipment when physical work is required.
- Ability to temporarily adjust scheduled workdays and hours, with advance notice when practicable, to provide coverage during planned team absences or scheduled operational events.
Now Helpful Experience (Skills):
List:
- Writing MOPs, SOPs, runbooks, implementation plans, rollback procedures, and escalation documentation.
- Coordinating remotehands providers, contractors, vendors, and colocation facility personnel.
- Linux administration and troubleshooting.
- Server management through IPMI, Redfish, iDRAC, iLO, or other BMC platforms.
- Infrastructure monitoring and alert-management platforms.
- Ticketing, documentation, inventory, and infrastructure-management systems.
- Basic networking concepts, including IP addressing, VLANs, interface bonding, and physical connectivity.
- Server diagnostics, component replacement, firmware management, and hardware compatibility.
- Hardware inventory and spare-parts management.
- Experience supporting bare metal, hosting, cloud, network, or large-scale distributed infrastructure.
- Familiarity with APIs or API endpoints used to retrieve and validate operational data.
Now Compensation and Benefits:
"Along with competitive pay, full-time Teraswitch employees are eligible for the following benefits beginning on their first day of employment: Health, dental, and vision insurance. 401(k) with company profit sharing. Flexible paid time off. Company holiday benefits."
Thus Pay: "competitive pay". Benefits list: Health, dental, and vision insurance; 401(k) with company profit sharing; Flexible paid time off; Company holiday benefits.
Now Success in This Role: description of success criteria. Could we put under a section? Not in allowed headings. Could incorporate into About the role or maybe as a separate section like "What Success Looks Like" but not allowed. Since we must only use allowed headings, we could incorporate this info into About the role
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. So no heading for the title. We must not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to preserve all substantive information; do not invent or summarize away detail. Thus we need to include all details from the posting, but we can format them. Let's extract sections: About the role: Could be "What To Expect" paragraph(s). Also maybe "Who We Are" could be About the company, but heading "About the role" maybe includes role description. We'll put the "What To Expect" prose under About the role. Responsibilities: list under "Responsibilities include:" (multiple lines). We'll put each as
- . Requirements: "What Our New Team Member Will Need" (mandatory experience). We'll list each bullet as
- .
Qualifications: maybe we could treat "Helpful Experience" as Qualifications? But Qualifications often similar to Requirements. However we have both Requirements and Helpful Experience. Could treat Helpful Experience as Qualifications (preferred but not required). Or we could treat Helpful Experience as Skills. The instruction includes Skills heading. So we can put Helpful Experience under Skills.
Thus:
- Requirements: mandatory experience.
- Skills: helpful experience (Linux admin, etc.)
- Benefits: list of benefits.
- Pay: mention competitive pay.
- Schedule: schedule description.
We also have "Who We Are" description of company. Could we put that under About the role? Or maybe we could add an "About the company" but not in allowed headings. Since only allowed headings are those listed, we should fit it somewhere. Could include in About the role section as a brief intro. The About the role heading could encompass both role description and company overview. That seems okay.
Thus About the role section will contain:
- Who We Are paragraph(s)
- What To Expect paragraph(s)
We need to preserve all substantive info, so we need to include both.
We'll put them in
tags. Now we need to format lists. Let's extract the exact text for each piece. Who We Are: "Teraswitch is on a mission to provide the highest performance, lowest latency bare metal servers in the world. With 20 data center locations around the world, Teraswitch has served thousands of customers across 185 countries. Founded by Brendan Mannella and headquartered in Pittsburgh, Pennsylvania, Teraswitch is a privately held infrastructure company operating a growing global bare metal platform." What To Expect: "As a member of Data Center Operations, you will own infrastructure incidents, customer requests, maintenance activities, deployments, and operational projects from intake through verified completion. This is primarily a remote infrastructure operations role—not a primarily hands-on data-center technician position. Most work is performed through monitoring systems, tickets, server-management interfaces, technical documentation, and coordination with customers, internal engineering teams, colocation facilities, vendors, contractors, and remote-hands providers. Approximately 10% of the role may involve physical work including server assembly, component replacement, cabling, rack-and-stack work, and equipment maintenance. This role requires someone who can investigate problems independently, communicate clearly with technical and nontechnical stakeholders, create precise technical procedures, manage multiple concurrent priorities, and remain accountable until work is completed and validated." Now Responsibilities list: It's a long paragraph starting with "Responsibilities include:" then a series of sentences each starting with a verb. We need to split into list items. Let's extract each bullet: - Own infrastructure incidents, customer requests, maintenance activities, deployments, and operational projects from intake through verified completion. - Monitor infrastructure alerts, support requests, maintenance activities, and active operational issues. - Investigate reported server, network, power, cooling, connectivity, deployment, and monitoring problems. - Gather and interpret information from logs, monitoring platforms, tickets, management interfaces, internal systems, customers, and on-site technicians. - Perform incident triage, take safe and documented corrective actions, and escalate service-affecting issues when appropriate. - Communicate directly and professionally with customers during incidents, technical investigations, maintenance events, and service requests. - Write precise Methods of Procedure, implementation plans, validation steps, rollback instructions, runbooks, and remote-hands directions. - Translate technical requirements into clear, executable instructions for colocation technicians, contractors, vendors, and internal teams. - Coordinate and direct remote-hands technicians at Teraswitch data center locations around the world. - Remain accountable for remote work by confirming the correct equipment, reviewing evidence, tracking progress, validating results, and ensuring documentation is complete. - Coordinate scheduled installations, migrations, maintenance events, hardware replacements, shipments, and other operational projects. - Work with facility personnel to address power, cooling, cross-connect, cabling, access, and other facility-provided services. - Coordinate vendor warranty technicians and ensure hardware issues are resolved promptly and correctly. - Maintain clear ticket updates, incident timelines, project notes, escalation records, and actionable shift handoffs. - Collaborate with Software, Network, Systems, Facilities, Logistics, and other internal teams. - Maintain accurate records of infrastructure, hardware changes, completed work, and physical inventory. - Identify recurring problems and improve documentation, procedures, tooling, and operational workflows. - Execute documented server-management, recovery, deployment, and maintenance procedures. - Perform occasional hands-on server assembly, rack-and-stack work, cabling, diagnostics, upgrades, and component replacement. - Provide temporary coverage on alternate Operations schedules during planned team absences or scheduled operational events. - Follow established security, change-management, escalation, validation, and access-control procedures. Now Requirements (What Our New Team Member Will Need): List: - Three or more years of experience in data center operations, infrastructure support, systems support, technical operations, or a similar role. - Demonstrated ability to write detailed technical procedures that another technician can execute without additional interpretation. - Experience troubleshooting infrastructure remotely using logs, monitoring platforms, tickets, command-line tools, server-management interfaces, or information supplied by on-site personnel. - Experience independently owning incidents, service requests, maintenance activities, or technical projects through completion. - Strong written communication and the ability to provide clear updates to customers, vendors, contractors, and internal technical teams. - Ability to prioritize multiple concurrent customer, infrastructure, and operational issues. - Sound judgment regarding service impact, change control, escalation, rollback, and validation. - Working knowledge of server hardware, network equipment, structured cabling, and data center facility services. - Ability to distinguish between gathering information, taking corrective action, escalating an issue, and transferring ownership. - Ability to follow technical procedures precisely and verify that completed work produced the intended result. - Strong troubleshooting, organization, and time-management skills. - Ability to safely lift, move, rack, and work around data center equipment when physical work is required. - Ability to temporarily adjust scheduled workdays and hours, with advance notice when practicable, to provide coverage during planned team absences or scheduled operational events. Now Helpful Experience (Skills): List: - Writing MOPs, SOPs, runbooks, implementation plans, rollback procedures, and escalation documentation. - Coordinating remotehands providers, contractors, vendors, and colocation facility personnel. - Linux administration and troubleshooting. - Server management through IPMI, Redfish, iDRAC, iLO, or other BMC platforms. - Infrastructure monitoring and alert-management platforms. - Ticketing, documentation, inventory, and infrastructure-management systems. - Basic networking concepts, including IP addressing, VLANs, interface bonding, and physical connectivity. - Server diagnostics, component replacement, firmware management, and hardware compatibility. - Hardware inventory and spare-parts management. - Experience supporting bare metal, hosting, cloud, network, or large-scale distributed infrastructure. - Familiarity with APIs or API endpoints used to retrieve and validate operational data. Now Compensation and Benefits: "Along with competitive pay, full-time Teraswitch employees are eligible for the following benefits beginning on their first day of employment: Health, dental, and vision insurance. 401(k) with company profit sharing. Flexible paid time off. Company holiday benefits." Thus Pay: "competitive pay". Benefits list: Health, dental, and vision insurance; 401(k) with company profit sharing; Flexible paid time off; Company holiday benefits. Now Success in This Role: description of success criteria. Could we put under a section? Not in allowed headings. Could incorporate into About the role or maybe as a separate section like "What Success Looks Like" but not allowed. Since we must only use allowed headings, we could incorporate this info into About the role