Data Center Infrastructure Project Manager
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/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". So we need to extract content.
Let's parse the posting:
- Location: On-site in Pittsburgh, Pennsylvania | Monday–Friday, 9:00 a.m.–5:00 p.m. Eastern (this is schedule info). So schedule: Monday-Friday 9-5 Eastern, some work outside standard hours.
- Who We Are: description of Teraswitch.
- What To Expect: description of role.
- What You’ll Own: bullet list of responsibilities.
- How You’ll Work With Other Teams: description.
- What We’re Looking For: qualifications/requirements.
- Helpful Experience: maybe skills.
- Schedule: already given.
- Compensation And Benefits: mentions competitive pay, benefits list.
- Success in This Role: maybe not needed.
We need sections: About the role (maybe "About the role" corresponds to Who We Are? Actually "Who We Are" is about company. Could be "About the role" is description of role (What To Expect). But we can decide.
We need to use headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not create sections with filler. So we need to see if we have content for each.
- About the role: Could be "What To Expect" describing role. That's substantive.
- Responsibilities: "What You’ll Own" and maybe "How You’ll Work With Other Teams" are responsibilities. So we can combine.
- Requirements: "What We’re Looking For" (three or more years experience etc.) That's requirements.
- Qualifications: maybe overlapping with Requirements; but we could treat "Helpful Experience" as qualifications or skills. However we need to avoid duplication. Could combine Requirements and Qualifications into one? But spec says we can have multiple sections; but we should not create empty sections. We have content for both Requirements and Qualifications? The posting lists "What We’re Looking For" (requirements) and "Helpful Experience" (helpful but not required). That could be Qualifications. Also "Skills" maybe from "Helpful Experience" includes familiarity with tools etc. Could treat Skills section.
- Benefits: list health, dental, vision, 401(k) with profit sharing, flexible PTO, company holiday benefits.
- Pay: mentions "competitive pay" but no specific numbers. That's vague; we should not create Pay section if only says "competitive pay" with no specifics? 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 vague but maybe acceptable? It's not a specific number. Might be considered filler. Safer to omit Pay section unless we have actual numbers. So we will not include Pay.
- Schedule: we have schedule info.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe Helpful Experience), Skills (maybe from Helpful Experience?), Benefits, Schedule.
But we need to avoid duplication. Let's map:
- About the role: "Who We Are" + "What To Expect" maybe.
- Responsibilities: combine "What You’ll Own" and "How You’ll Work With Other Teams".
- Requirements: "What We’re Looking For".
- Qualifications: maybe "Helpful Experience" (but that's more like preferred experience). Could be Qualifications.
- Skills: maybe from "Helpful Experience" includes familiarity with racks, power circuits, etc., Jira, Confluence, etc. Could be Skills.
But we might combine Qualifications and Skills into one section? However spec says we can have multiple sections but prefer few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Requirements, Benefits, Schedule. And maybe include Skills/Qualifications within Requirements? But we need to capture all substantive info. The "Helpful Experience" is substantive; we could include it under Requirements as "Preferred qualifications". But we need a heading for Requirements; we can include both required and preferred under that heading. That's okay.
Thus we can have sections: About the role, Responsibilities, Requirements, Benefits, Schedule.
Check if we need Qualifications/Skills separate? Not required if we incorporate.
Now we need to format:
- Use
for each section heading.
- Use - for any list of duties/requirements/benefits.
- Use
for prose.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc.
Let's extract content.
**About the role**: Combine Who We Are and What To Expect.
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: "Teraswitch is seeking a Data Center Infrastructure Project Manager to organize and drive infrastructure projects across our global data center footprint. Because Teraswitch operates as a customer within independently owned data center facilities, this role serves as the primary project management bridge between our internal technical teams and the facility providers, contractors, vendors, carriers, and remote-hands technicians responsible for work at each site. This is an individual contributor project management role focused on planning, coordination, documentation, communication, and follow through. You will work with colocation facilities, contractors, vendors, remote hands providers, and internal Teraswitch teams to ensure projects are clearly defined, assigned, tracked, validated, and completed. This is not a building maintenance, skilled trades, engineering design, or hands on installation position. Your responsibility is to understand what must be accomplished, organize the responsible parties, maintain visibility into progress and risks, verify the result, keep documentation current, and drive the project through completion. Projects may include new data center deployments, rack and power additions, capacity expansions, equipment installations, cross connects, cabling, migrations, decommissions, facility remediation, and corrective actions following infrastructure incidents."
We can combine into a few paragraphs.
**Responsibilities**: Combine What You’ll Own and How You’ll Work With Other Teams.
What You’ll Own bullet list? It's a paragraph with many responsibilities separated by periods. We can turn into
- items.
List items:
- Manage data center infrastructure projects from initial requirements through planning, execution, validation, documentation, and closure.
- Manage Teraswitch’s project-level relationship with colocation providers as their customer, ensuring requests are clearly scoped, commitments are documented, deadlines are tracked, and completed work satisfies Teraswitch’s operational requirements.
- Create and maintain project plans containing scope, owners, milestones, dependencies, deadlines, risks, escalation points, and completion criteria.
- Coordinate work among colocation facilities, contractors, vendors, remote-hands providers, and Teraswitch’s Operations, Network, Systems, Software, Purchasing, and Logistics teams.
- Translate internal requirements into clear scopes of work, action plans, vendor requests, implementation steps, and completion criteria.
- Schedule and track rack deployments, power installations, cabling, cross-connects, equipment deliveries, remote installations, migrations, and decommissions.
- Lead communication with facility personnel when power, cooling, environmental, cabling, access, or space issues affect Teraswitch infrastructure.
- Track facility-related issues beyond the initial incident response and ensure corrective actions are assigned, completed, validated, and documented.
- Review vendor proposals, scopes of work, schedules, implementation plans, completion evidence, and invoices for accuracy and alignment with project requirements.
- Track project dependencies such as rack availability, power readiness, cooling considerations, network connectivity, equipment delivery, site access, and contractor scheduling.
- Maintain accurate project records, rack elevations, site documentation, floor plans, photographs, vendor contacts, access procedures, and escalation paths.
- Coordinate recurring site audits and reconcile documented conditions with information reported by facility personnel or on-site technicians.
- Provide clear project updates identifying completed work, upcoming milestones, blockers, risks, ownership, and decisions required.
- Follow up persistently with internal and external owners and escalate when commitments, deadlines, service reliability, or capacity delivery are at risk.
- Develop repeatable templates, checklists, documentation standards, and workflows for deployments, expansions, migrations, audits, and decommissions.
- Identify recurring coordination or documentation failures and improve the process used to prevent them.
- Support infrastructure monitoring and reporting projects by coordinating requirements and ensuring the appropriate teams provide accurate, actionable data.
How You’ll Work With Other Teams: could be turned into list as well, but maybe we can incorporate into responsibilities as additional items.
How You’ll Work With Other Teams paragraph: "You will work especially closely with Teraswitch’s Server Fulfillment & Capacity function. You will ensure the intended destination is prepared to receive that capacity by coordinating the necessary facility, vendor, contractor, documentation, and infrastructure work. You will also partner with: Data Center Operations. Network and Systems teams. Purchasing and Logistics. Software and internal tooling teams. Colocation facility personnel. Contractors, infrastructure vendors, carriers, and remote-hands providers. You will not replace the engineers, facility technicians, or tradespeople responsible for designing or physically performing specialized work. Your role is to connect those parties, maintain the plan, identify missing requirements, track execution, resolve blockers, and verify completion."
We can turn into list items:
- Work especially closely with Teraswitch’s Server Fulfillment & Capacity function, ensuring the intended destination is prepared to receive capacity by coordinating necessary facility, vendor, contractor, documentation, and infrastructure work.
- Partner with Data Center Operations, Network and Systems teams, Purchasing and Logistics, Software and internal tooling teams, colocation facility personnel, contractors, infrastructure vendors, carriers, and remote-hands providers.
- Not replace engineers, facility technicians, or tradespeople responsible for designing or physically performing specialized work; instead connect those parties, maintain the plan, identify missing requirements, track execution, resolve blockers, and verify completion.
We can add these to responsibilities list.
**Requirements**: "What We’re Looking For" paragraph plus maybe "Helpful Experience" as preferred.
What We’re Looking For:
- Three or more years of experience managing or coordinating technical projects.
- Demonstrated ownership of projects involving multiple stakeholders, dependencies, deadlines, and external providers.
- Strong organizational skills and the ability to maintain an accurate picture across several simultaneous projects.
- Excellent written communication, documentation, follow-up, and stakeholder-management skills.
- Ability to turn incomplete or technical requirements into clear plans, responsibilities, timelines, and completion criteria.
- Ability to identify risks, missing information, and blockers before they affect project delivery.
- Experience maintaining project plans, status reports, task tracking, documentation, and decision records.
- Sound judgment regarding priority, escalation, service impact, and when work can be considered complete.
- Comfort working with technical teams and learning unfamiliar infrastructure concepts.
- Ability to verify completed work through documentation, photographs, monitoring data, testing results, or confirmation from the appropriate technical owner.
- Ability to work independently while maintaining communication, visibility, and accountability.
Helpful Experience (preferred):
- Experience in data centers, colocation, hosting, cloud infrastructure, telecommunications, networking, facilities coordination, construction, or technical logistics.
- Familiarity with racks, power circuits, PDUs, cooling, environmental conditions, structured cabling, cross-connects, and physical capacity.
- Experience coordinating colocation personnel, contractors, vendors, carriers, or remote-hands providers.
- Experience with new-site deployments,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". So we need to extract content. Let's parse the posting: - Location: On-site in Pittsburgh, Pennsylvania | Monday–Friday, 9:00 a.m.–5:00 p.m. Eastern (this is schedule info). So schedule: Monday-Friday 9-5 Eastern, some work outside standard hours. - Who We Are: description of Teraswitch. - What To Expect: description of role. - What You’ll Own: bullet list of responsibilities. - How You’ll Work With Other Teams: description. - What We’re Looking For: qualifications/requirements. - Helpful Experience: maybe skills. - Schedule: already given. - Compensation And Benefits: mentions competitive pay, benefits list. - Success in This Role: maybe not needed. We need sections: About the role (maybe "About the role" corresponds to Who We Are? Actually "Who We Are" is about company. Could be "About the role" is description of role (What To Expect). But we can decide. We need to use headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not create sections with filler. So we need to see if we have content for each. - About the role: Could be "What To Expect" describing role. That's substantive. - Responsibilities: "What You’ll Own" and maybe "How You’ll Work With Other Teams" are responsibilities. So we can combine. - Requirements: "What We’re Looking For" (three or more years experience etc.) That's requirements. - Qualifications: maybe overlapping with Requirements; but we could treat "Helpful Experience" as qualifications or skills. However we need to avoid duplication. Could combine Requirements and Qualifications into one? But spec says we can have multiple sections; but we should not create empty sections. We have content for both Requirements and Qualifications? The posting lists "What We’re Looking For" (requirements) and "Helpful Experience" (helpful but not required). That could be Qualifications. Also "Skills" maybe from "Helpful Experience" includes familiarity with tools etc. Could treat Skills section. - Benefits: list health, dental, vision, 401(k) with profit sharing, flexible PTO, company holiday benefits. - Pay: mentions "competitive pay" but no specific numbers. That's vague; we should not create Pay section if only says "competitive pay" with no specifics? 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 vague but maybe acceptable? It's not a specific number. Might be considered filler. Safer to omit Pay section unless we have actual numbers. So we will not include Pay. - Schedule: we have schedule info. Thus sections: About the role, Responsibilities, Requirements, Qualifications (maybe Helpful Experience), Skills (maybe from Helpful Experience?), Benefits, Schedule. But we need to avoid duplication. Let's map: - About the role: "Who We Are" + "What To Expect" maybe. - Responsibilities: combine "What You’ll Own" and "How You’ll Work With Other Teams". - Requirements: "What We’re Looking For". - Qualifications: maybe "Helpful Experience" (but that's more like preferred experience). Could be Qualifications. - Skills: maybe from "Helpful Experience" includes familiarity with racks, power circuits, etc., Jira, Confluence, etc. Could be Skills. But we might combine Qualifications and Skills into one section? However spec says we can have multiple sections but prefer few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Requirements, Benefits, Schedule. And maybe include Skills/Qualifications within Requirements? But we need to capture all substantive info. The "Helpful Experience" is substantive; we could include it under Requirements as "Preferred qualifications". But we need a heading for Requirements; we can include both required and preferred under that heading. That's okay. Thus we can have sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Check if we need Qualifications/Skills separate? Not required if we incorporate. Now we need to format: - Use
for each section heading.
- Use - for any list of duties/requirements/benefits.
- Use
for prose.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc.
Let's extract content.
**About the role**: Combine Who We Are and What To Expect.
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: "Teraswitch is seeking a Data Center Infrastructure Project Manager to organize and drive infrastructure projects across our global data center footprint. Because Teraswitch operates as a customer within independently owned data center facilities, this role serves as the primary project management bridge between our internal technical teams and the facility providers, contractors, vendors, carriers, and remote-hands technicians responsible for work at each site. This is an individual contributor project management role focused on planning, coordination, documentation, communication, and follow through. You will work with colocation facilities, contractors, vendors, remote hands providers, and internal Teraswitch teams to ensure projects are clearly defined, assigned, tracked, validated, and completed. This is not a building maintenance, skilled trades, engineering design, or hands on installation position. Your responsibility is to understand what must be accomplished, organize the responsible parties, maintain visibility into progress and risks, verify the result, keep documentation current, and drive the project through completion. Projects may include new data center deployments, rack and power additions, capacity expansions, equipment installations, cross connects, cabling, migrations, decommissions, facility remediation, and corrective actions following infrastructure incidents."
We can combine into a few paragraphs.
**Responsibilities**: Combine What You’ll Own and How You’ll Work With Other Teams.
What You’ll Own bullet list? It's a paragraph with many responsibilities separated by periods. We can turn into
- items.
List items:
- Manage data center infrastructure projects from initial requirements through planning, execution, validation, documentation, and closure.
- Manage Teraswitch’s project-level relationship with colocation providers as their customer, ensuring requests are clearly scoped, commitments are documented, deadlines are tracked, and completed work satisfies Teraswitch’s operational requirements.
- Create and maintain project plans containing scope, owners, milestones, dependencies, deadlines, risks, escalation points, and completion criteria.
- Coordinate work among colocation facilities, contractors, vendors, remote-hands providers, and Teraswitch’s Operations, Network, Systems, Software, Purchasing, and Logistics teams.
- Translate internal requirements into clear scopes of work, action plans, vendor requests, implementation steps, and completion criteria.
- Schedule and track rack deployments, power installations, cabling, cross-connects, equipment deliveries, remote installations, migrations, and decommissions.
- Lead communication with facility personnel when power, cooling, environmental, cabling, access, or space issues affect Teraswitch infrastructure.
- Track facility-related issues beyond the initial incident response and ensure corrective actions are assigned, completed, validated, and documented.
- Review vendor proposals, scopes of work, schedules, implementation plans, completion evidence, and invoices for accuracy and alignment with project requirements.
- Track project dependencies such as rack availability, power readiness, cooling considerations, network connectivity, equipment delivery, site access, and contractor scheduling.
- Maintain accurate project records, rack elevations, site documentation, floor plans, photographs, vendor contacts, access procedures, and escalation paths.
- Coordinate recurring site audits and reconcile documented conditions with information reported by facility personnel or on-site technicians.
- Provide clear project updates identifying completed work, upcoming milestones, blockers, risks, ownership, and decisions required.
- Follow up persistently with internal and external owners and escalate when commitments, deadlines, service reliability, or capacity delivery are at risk.
- Develop repeatable templates, checklists, documentation standards, and workflows for deployments, expansions, migrations, audits, and decommissions.
- Identify recurring coordination or documentation failures and improve the process used to prevent them.
- Support infrastructure monitoring and reporting projects by coordinating requirements and ensuring the appropriate teams provide accurate, actionable data.
How You’ll Work With Other Teams: could be turned into list as well, but maybe we can incorporate into responsibilities as additional items.
How You’ll Work With Other Teams paragraph: "You will work especially closely with Teraswitch’s Server Fulfillment & Capacity function. You will ensure the intended destination is prepared to receive that capacity by coordinating the necessary facility, vendor, contractor, documentation, and infrastructure work. You will also partner with: Data Center Operations. Network and Systems teams. Purchasing and Logistics. Software and internal tooling teams. Colocation facility personnel. Contractors, infrastructure vendors, carriers, and remote-hands providers. You will not replace the engineers, facility technicians, or tradespeople responsible for designing or physically performing specialized work. Your role is to connect those parties, maintain the plan, identify missing requirements, track execution, resolve blockers, and verify completion."
We can turn into list items:
- Work especially closely with Teraswitch’s Server Fulfillment & Capacity function, ensuring the intended destination is prepared to receive capacity by coordinating necessary facility, vendor, contractor, documentation, and infrastructure work.
- Partner with Data Center Operations, Network and Systems teams, Purchasing and Logistics, Software and internal tooling teams, colocation facility personnel, contractors, infrastructure vendors, carriers, and remote-hands providers.
- Not replace engineers, facility technicians, or tradespeople responsible for designing or physically performing specialized work; instead connect those parties, maintain the plan, identify missing requirements, track execution, resolve blockers, and verify completion.
We can add these to responsibilities list.
**Requirements**: "What We’re Looking For" paragraph plus maybe "Helpful Experience" as preferred.
What We’re Looking For:
- Three or more years of experience managing or coordinating technical projects.
- Demonstrated ownership of projects involving multiple stakeholders, dependencies, deadlines, and external providers.
- Strong organizational skills and the ability to maintain an accurate picture across several simultaneous projects.
- Excellent written communication, documentation, follow-up, and stakeholder-management skills.
- Ability to turn incomplete or technical requirements into clear plans, responsibilities, timelines, and completion criteria.
- Ability to identify risks, missing information, and blockers before they affect project delivery.
- Experience maintaining project plans, status reports, task tracking, documentation, and decision records.
- Sound judgment regarding priority, escalation, service impact, and when work can be considered complete.
- Comfort working with technical teams and learning unfamiliar infrastructure concepts.
- Ability to verify completed work through documentation, photographs, monitoring data, testing results, or confirmation from the appropriate technical owner.
- Ability to work independently while maintaining communication, visibility, and accountability.
Helpful Experience (preferred):
- Experience in data centers, colocation, hosting, cloud infrastructure, telecommunications, networking, facilities coordination, construction, or technical logistics.
- Familiarity with racks, power circuits, PDUs, cooling, environmental conditions, structured cabling, cross-connects, and physical capacity.
- Experience coordinating colocation personnel, contractors, vendors, carriers, or remote-hands providers.
- Experience with new-site deployments,
for prose. We must not repeat job title as heading. We must not include boilerplate like EEO etc. Let's extract content. **About the role**: Combine Who We Are and What To Expect. 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: "Teraswitch is seeking a Data Center Infrastructure Project Manager to organize and drive infrastructure projects across our global data center footprint. Because Teraswitch operates as a customer within independently owned data center facilities, this role serves as the primary project management bridge between our internal technical teams and the facility providers, contractors, vendors, carriers, and remote-hands technicians responsible for work at each site. This is an individual contributor project management role focused on planning, coordination, documentation, communication, and follow through. You will work with colocation facilities, contractors, vendors, remote hands providers, and internal Teraswitch teams to ensure projects are clearly defined, assigned, tracked, validated, and completed. This is not a building maintenance, skilled trades, engineering design, or hands on installation position. Your responsibility is to understand what must be accomplished, organize the responsible parties, maintain visibility into progress and risks, verify the result, keep documentation current, and drive the project through completion. Projects may include new data center deployments, rack and power additions, capacity expansions, equipment installations, cross connects, cabling, migrations, decommissions, facility remediation, and corrective actions following infrastructure incidents." We can combine into a few paragraphs. **Responsibilities**: Combine What You’ll Own and How You’ll Work With Other Teams. What You’ll Own bullet list? It's a paragraph with many responsibilities separated by periods. We can turn into
- items. List items: - Manage data center infrastructure projects from initial requirements through planning, execution, validation, documentation, and closure. - Manage Teraswitch’s project-level relationship with colocation providers as their customer, ensuring requests are clearly scoped, commitments are documented, deadlines are tracked, and completed work satisfies Teraswitch’s operational requirements. - Create and maintain project plans containing scope, owners, milestones, dependencies, deadlines, risks, escalation points, and completion criteria. - Coordinate work among colocation facilities, contractors, vendors, remote-hands providers, and Teraswitch’s Operations, Network, Systems, Software, Purchasing, and Logistics teams. - Translate internal requirements into clear scopes of work, action plans, vendor requests, implementation steps, and completion criteria. - Schedule and track rack deployments, power installations, cabling, cross-connects, equipment deliveries, remote installations, migrations, and decommissions. - Lead communication with facility personnel when power, cooling, environmental, cabling, access, or space issues affect Teraswitch infrastructure. - Track facility-related issues beyond the initial incident response and ensure corrective actions are assigned, completed, validated, and documented. - Review vendor proposals, scopes of work, schedules, implementation plans, completion evidence, and invoices for accuracy and alignment with project requirements. - Track project dependencies such as rack availability, power readiness, cooling considerations, network connectivity, equipment delivery, site access, and contractor scheduling. - Maintain accurate project records, rack elevations, site documentation, floor plans, photographs, vendor contacts, access procedures, and escalation paths. - Coordinate recurring site audits and reconcile documented conditions with information reported by facility personnel or on-site technicians. - Provide clear project updates identifying completed work, upcoming milestones, blockers, risks, ownership, and decisions required. - Follow up persistently with internal and external owners and escalate when commitments, deadlines, service reliability, or capacity delivery are at risk. - Develop repeatable templates, checklists, documentation standards, and workflows for deployments, expansions, migrations, audits, and decommissions. - Identify recurring coordination or documentation failures and improve the process used to prevent them. - Support infrastructure monitoring and reporting projects by coordinating requirements and ensuring the appropriate teams provide accurate, actionable data. How You’ll Work With Other Teams: could be turned into list as well, but maybe we can incorporate into responsibilities as additional items. How You’ll Work With Other Teams paragraph: "You will work especially closely with Teraswitch’s Server Fulfillment & Capacity function. You will ensure the intended destination is prepared to receive that capacity by coordinating the necessary facility, vendor, contractor, documentation, and infrastructure work. You will also partner with: Data Center Operations. Network and Systems teams. Purchasing and Logistics. Software and internal tooling teams. Colocation facility personnel. Contractors, infrastructure vendors, carriers, and remote-hands providers. You will not replace the engineers, facility technicians, or tradespeople responsible for designing or physically performing specialized work. Your role is to connect those parties, maintain the plan, identify missing requirements, track execution, resolve blockers, and verify completion." We can turn into list items: - Work especially closely with Teraswitch’s Server Fulfillment & Capacity function, ensuring the intended destination is prepared to receive capacity by coordinating necessary facility, vendor, contractor, documentation, and infrastructure work. - Partner with Data Center Operations, Network and Systems teams, Purchasing and Logistics, Software and internal tooling teams, colocation facility personnel, contractors, infrastructure vendors, carriers, and remote-hands providers. - Not replace engineers, facility technicians, or tradespeople responsible for designing or physically performing specialized work; instead connect those parties, maintain the plan, identify missing requirements, track execution, resolve blockers, and verify completion. We can add these to responsibilities list. **Requirements**: "What We’re Looking For" paragraph plus maybe "Helpful Experience" as preferred. What We’re Looking For: - Three or more years of experience managing or coordinating technical projects. - Demonstrated ownership of projects involving multiple stakeholders, dependencies, deadlines, and external providers. - Strong organizational skills and the ability to maintain an accurate picture across several simultaneous projects. - Excellent written communication, documentation, follow-up, and stakeholder-management skills. - Ability to turn incomplete or technical requirements into clear plans, responsibilities, timelines, and completion criteria. - Ability to identify risks, missing information, and blockers before they affect project delivery. - Experience maintaining project plans, status reports, task tracking, documentation, and decision records. - Sound judgment regarding priority, escalation, service impact, and when work can be considered complete. - Comfort working with technical teams and learning unfamiliar infrastructure concepts. - Ability to verify completed work through documentation, photographs, monitoring data, testing results, or confirmation from the appropriate technical owner. - Ability to work independently while maintaining communication, visibility, and accountability. Helpful Experience (preferred): - Experience in data centers, colocation, hosting, cloud infrastructure, telecommunications, networking, facilities coordination, construction, or technical logistics. - Familiarity with racks, power circuits, PDUs, cooling, environmental conditions, structured cabling, cross-connects, and physical capacity. - Experience coordinating colocation personnel, contractors, vendors, carriers, or remote-hands providers. - Experience with new-site deployments,