Technical Program Manager, Network
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The posting includes "About Fluidstack" (company description). Could be "About the role"? Actually "About Fluidstack" is company overview, not role. But we can still use "About the role" heading for role description? The instruction says use those headings as examples, but we should include a section only when posting has real specific content for it. We have content for: About Fluidstack (company), How We Operate (culture), Data Center Operations Team (team description), Role Scope (responsibilities), What We're Looking For (requirements/qualifications), Compensation Range (pay). We could map:
- About Fluidstack -> maybe "About the role"? But better to use "About Fluidstack" as heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. So we need to map content to those headings.
We have:
- About the role: could include company overview and team description? Might be okay.
- Responsibilities: Role Scope.
- Requirements/Qualifications/Skills: What We're Looking For.
- Pay: Compensation Range.
- Benefits: none.
- Schedule: none.
We should not repeat job title as heading. No Job ID.
We need to preserve all substantive information. Remove boilerplate: EEO, equal opportunity, scam warning, application instructions, confirmation email etc. Also remove duplicated "How We Operate" repeated lines. Keep content but not duplicate.
We need to include sections only when posting has real specific content. So we will include About the role, Responsibilities, Requirements (or Qualifications), Skills, Pay. Possibly combine Requirements and Qualifications into one? But we can have separate if content fits. The "What We're Looking For" includes both requirements and qualifications and skills. Could split into Requirements and Skills. But we can just put under Requirements (or Qualifications). Safer to have one section "Requirements" containing the list.
We need to use - for any list of duties/requirements/benefits. So for responsibilities list (Role Scope) we need to turn each bullet into
- . The Role Scope paragraph includes multiple sentences each starting with a verb. We can break into list items.
Similarly, What We're Looking For bullet list: each line starting with "You've". We'll make list.
Compensation Range: just a
.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
About Fluidstack paragraph: "We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!"
How We Operate (duplicate) content: "Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.Insane urgency. We drive everything forward as fast as possible.Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world."
We can include this as part of About the role or maybe as a separate section "How We Operate" but not in prescribed headings. Could incorporate into About the role.
The Data Center Operations Team section includes examples of key problems and role scope. Actually the "The Data Center Operations Team Examples of key problems the team is working on" then bullet-like sentences. Then "Role Scope" separate heading with bullet-like sentences. We need to preserve all.
Let's parse:
"The Data Center Operations Team Examples of key problems the team is working on Operate at the scale of a nation, not a building. Accelerating toward 10s to 100s of GWs by the end of the decade, more than the entire electricity consumption of many countries. You won't just run a data center; you'll run infrastructure the size of a G7.Fly the plane while it's being built. Running flawless operations inside a live construction zone, adapting in real time and turning the pace of build-out into our advantage. You will redefine operational excellence.Write the playbook, don't inherit it. Most operators step into someone else's system. Here you build one, leaving your fingerprints on how the whole company runs. As we scale 100x, you'll set the standards, shape the operating model, and grow the team by the thousands"
That's a paragraph with sentences. Could treat as description.
Then "Role Scope Own the network critical path for every site activation, from structured cabling and optics through switch and router delivery, circuit turn-up, and vendor integration, so network is never the reason a site goes live late.Define the network readiness gates, acceptance criteria, and sign-offs that move a site from construction into production, and hold each one across the fleet rather than renegotiating them site by site.Run the operating rhythm across network engineering, network operations, deployment, supply chain, and the colocation or construction partner, surfacing schedule risk weeks before it reaches the go-live date.Drive network change and incident programs to closure, tracking corrective actions, recurrence patterns, and fleet-wide trends into the weekly and monthly reviews that decide what the org does next.Hold OEMs, ODMs, and deployment partners to delivery commitments with measured performance data, including RMA and integration turnaround, so vendor problems surface as evidence rather than escalation.Partner with the Principal Operations Engineer, Network, who sets the technical standard, and own whether that standard actually lands on schedule at every site. Travel 50%."
We need to turn each sentence into list item.
Then "What We're Looking For The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would. You've run network deployment or infrastructure delivery programs at scale, where a missed turn-up date cost capacity rather than a slipped status report.You know networks well enough to hold engineers and vendors to a schedule credibly: structured cabling and optics, carrier circuit timelines, switch and router deployment, and what actually drives integration slip.You've built activation or readiness frameworks from nothing, defining the gates and acceptance criteria yourself rather than running a process someone else designed.You quarterback across engineering, deployment, supply chain, and external partners without owning any of them, and you're the person other teams call when a workstream is stuck.You track corrective actions and vendor performance to closure in live reporting, not to initial assignment.You write clearly enough to turn a tangled delivery problem into a decision and a next action for a site lead, an executive, or a counterparty who was not in the room.Bonus: Hyperscale or large colocation network deployment (100k+ endpoint fabrics). Hardware supply chain and RMA program ownership (OEM, ODM, integrator). Program management credentials (PMP, PgMP). Tooling and scripting for fleet-scale tracking (Python, Jira or Smartsheet automation, custom dashboards)."
We need to turn each bullet into list item. The "Bonus:" line is also a bullet.
Compensation Range: "Compensation Range: $200K - $300K"
Now we need to strip boilerplate: EEO, equal opportunity, scam warning, application instructions, confirmation email etc. Also remove duplicated "How We Operate" lines (we have one copy). Also remove "We are committed to pay equity and transparency. Fluidstack is an Equal Employment Opportunity Employer..." etc. Also remove "You will receive a confirmation email..." etc.
Now construct HTML.
We'll have:
About the role
... (About Fluidstack + How We Operate combined)
Responsibilities
- Own the network critical path for every site activation, from structured cabling and optics through switch and router delivery, circuit turn-up, and vendor integration, so network is never the reason a site goes live late.
- Define the network readiness gates, acceptance criteria, and sign-offs that move a site from construction into production, and hold each one across the fleet rather than renegotiating them site by site.
- Run the operating rhythm across network engineering, network operations, deployment, supply chain, and the colocation or construction partner, surfacing schedule risk weeks before it reaches the go-live date.
- Drive network change and incident programs to closure, tracking corrective actions, recurrence patterns, and fleet-wide trends into the weekly and monthly reviews that decide what the org does next.
- Hold OEMs, ODMs, and deployment partners to delivery commitments with measured performance data, including RMA and integration turnaround, so vendor problems surface as evidence rather than escalation.
- Partner with the Principal Operations Engineer, Network, who sets the technical standard, and own whether that standard actually lands on schedule at every site.
- Travel 50%.
Requirements
- You've run network deployment or infrastructure delivery programs at scale, where a missed turn-up date cost capacity rather than a slipped status report.
- You know networks well enough to hold engineers and vendors to a schedule credibly: structured cabling and optics, carrier circuit timelines, switch and router deployment, and what actually drives integration slip.
- You've built activation or readiness frameworks from nothing, defining the gates and acceptance criteria yourself rather than running a process someone else designed.
- You quarterback across engineering, deployment, supply chain, and external partners without owning any of them, and you're the person other teams call when a workstream is stuck.
- You track corrective actions and vendor performance to closure in live reporting, not to initial assignment.
- You write clearly enough to turn a tangled delivery problem into a decision and a next action for a site lead, an executive, or a counterparty who was not in the room.
- Bonus: Hyperscale or large colocation network deployment (100k+ endpoint fabrics).
- Hardware supply chain and RMA program ownership (OEM, ODM, integrator).
- Program management credentials (PMP, PgMP).
- Tooling and scripting for fleet-scale tracking (Python, Jira or Smartsheet automation, custom dashboards).
Pay
Compensation Range:
- for any list of duties/requirements/benefits. So for responsibilities list (Role Scope) we need to turn each bullet into
- . The Role Scope paragraph includes multiple sentences each starting with a verb. We can break into list items.
Similarly, What We're Looking For bullet list: each line starting with "You've". We'll make list.
Compensation Range: just a
. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Fluidstack paragraph: "We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply!" How We Operate (duplicate) content: "Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role.Insane urgency. We drive everything forward as fast as possible.Reason from first principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins.Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward.Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world." We can include this as part of About the role or maybe as a separate section "How We Operate" but not in prescribed headings. Could incorporate into About the role. The Data Center Operations Team section includes examples of key problems and role scope. Actually the "The Data Center Operations Team Examples of key problems the team is working on" then bullet-like sentences. Then "Role Scope" separate heading with bullet-like sentences. We need to preserve all. Let's parse: "The Data Center Operations Team Examples of key problems the team is working on Operate at the scale of a nation, not a building. Accelerating toward 10s to 100s of GWs by the end of the decade, more than the entire electricity consumption of many countries. You won't just run a data center; you'll run infrastructure the size of a G7.Fly the plane while it's being built. Running flawless operations inside a live construction zone, adapting in real time and turning the pace of build-out into our advantage. You will redefine operational excellence.Write the playbook, don't inherit it. Most operators step into someone else's system. Here you build one, leaving your fingerprints on how the whole company runs. As we scale 100x, you'll set the standards, shape the operating model, and grow the team by the thousands" That's a paragraph with sentences. Could treat as description. Then "Role Scope Own the network critical path for every site activation, from structured cabling and optics through switch and router delivery, circuit turn-up, and vendor integration, so network is never the reason a site goes live late.Define the network readiness gates, acceptance criteria, and sign-offs that move a site from construction into production, and hold each one across the fleet rather than renegotiating them site by site.Run the operating rhythm across network engineering, network operations, deployment, supply chain, and the colocation or construction partner, surfacing schedule risk weeks before it reaches the go-live date.Drive network change and incident programs to closure, tracking corrective actions, recurrence patterns, and fleet-wide trends into the weekly and monthly reviews that decide what the org does next.Hold OEMs, ODMs, and deployment partners to delivery commitments with measured performance data, including RMA and integration turnaround, so vendor problems surface as evidence rather than escalation.Partner with the Principal Operations Engineer, Network, who sets the technical standard, and own whether that standard actually lands on schedule at every site. Travel 50%." We need to turn each sentence into list item. Then "What We're Looking For The below is a starting point. We always make space for exceptional people, so if you don't fit this role exactly, tell us where you would. You've run network deployment or infrastructure delivery programs at scale, where a missed turn-up date cost capacity rather than a slipped status report.You know networks well enough to hold engineers and vendors to a schedule credibly: structured cabling and optics, carrier circuit timelines, switch and router deployment, and what actually drives integration slip.You've built activation or readiness frameworks from nothing, defining the gates and acceptance criteria yourself rather than running a process someone else designed.You quarterback across engineering, deployment, supply chain, and external partners without owning any of them, and you're the person other teams call when a workstream is stuck.You track corrective actions and vendor performance to closure in live reporting, not to initial assignment.You write clearly enough to turn a tangled delivery problem into a decision and a next action for a site lead, an executive, or a counterparty who was not in the room.Bonus: Hyperscale or large colocation network deployment (100k+ endpoint fabrics). Hardware supply chain and RMA program ownership (OEM, ODM, integrator). Program management credentials (PMP, PgMP). Tooling and scripting for fleet-scale tracking (Python, Jira or Smartsheet automation, custom dashboards)." We need to turn each bullet into list item. The "Bonus:" line is also a bullet. Compensation Range: "Compensation Range: $200K - $300K" Now we need to strip boilerplate: EEO, equal opportunity, scam warning, application instructions, confirmation email etc. Also remove duplicated "How We Operate" lines (we have one copy). Also remove "We are committed to pay equity and transparency. Fluidstack is an Equal Employment Opportunity Employer..." etc. Also remove "You will receive a confirmation email..." etc. Now construct HTML. We'll have:
About the role
... (About Fluidstack + How We Operate combined)
Responsibilities
- Own the network critical path for every site activation, from structured cabling and optics through switch and router delivery, circuit turn-up, and vendor integration, so network is never the reason a site goes live late.
- Define the network readiness gates, acceptance criteria, and sign-offs that move a site from construction into production, and hold each one across the fleet rather than renegotiating them site by site.
- Run the operating rhythm across network engineering, network operations, deployment, supply chain, and the colocation or construction partner, surfacing schedule risk weeks before it reaches the go-live date.
- Drive network change and incident programs to closure, tracking corrective actions, recurrence patterns, and fleet-wide trends into the weekly and monthly reviews that decide what the org does next.
- Hold OEMs, ODMs, and deployment partners to delivery commitments with measured performance data, including RMA and integration turnaround, so vendor problems surface as evidence rather than escalation.
- Partner with the Principal Operations Engineer, Network, who sets the technical standard, and own whether that standard actually lands on schedule at every site.
- Travel 50%.
Requirements
- You've run network deployment or infrastructure delivery programs at scale, where a missed turn-up date cost capacity rather than a slipped status report.
- You know networks well enough to hold engineers and vendors to a schedule credibly: structured cabling and optics, carrier circuit timelines, switch and router deployment, and what actually drives integration slip.
- You've built activation or readiness frameworks from nothing, defining the gates and acceptance criteria yourself rather than running a process someone else designed.
- You quarterback across engineering, deployment, supply chain, and external partners without owning any of them, and you're the person other teams call when a workstream is stuck.
- You track corrective actions and vendor performance to closure in live reporting, not to initial assignment.
- You write clearly enough to turn a tangled delivery problem into a decision and a next action for a site lead, an executive, or a counterparty who was not in the room.
- Bonus: Hyperscale or large colocation network deployment (100k+ endpoint fabrics).
- Hardware supply chain and RMA program ownership (OEM, ODM, integrator).
- Program management credentials (PMP, PgMP).
- Tooling and scripting for fleet-scale tracking (Python, Jira or Smartsheet automation, custom dashboards).
Pay
Compensation Range: