Principal Technical Program Manager, AI Physical Deployment
About the role
then paragraph). Responsibilities: useResponsibilities
then- for each bullet under "What You'll be Doing". Requirements: maybe combine required experience and qualifications? The instruction: Use sections for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where.
We have required experience (Experience: 5+ years...). That could be under Requirements. Qualifications could be Preferred Qualifications. Skills could be technical domain knowledge etc. But we need to avoid duplication.
Better: Requirements = mandatory experience and qualifications (the "Experience:" block). Qualifications = Preferred Qualifications. Skills = maybe technical domain knowledge etc? But that is already in Requirements. However we can put technical domain knowledge under Skills. Let's think.
The posting includes:
- Experience: 5+ years of experience in a Technical Program Management role, successfully driving large-scale, complex infrastructure or physical deployment projects.
- Technical Domain Knowledge: Strong foundational understanding of data center infrastructure, distributed systems, and networking concepts.
- Program Management Rigor: Proven expertise in modern program management methodologies (Agile, Scrum, PMP certification preferred). Exceptional organizational, communication, and presentation skills.
- Metrics-Driven Approach: Demonstrable experience in defining, tracking, and improving system performance based on operational metrics (e.g., Uptime, Availability, MTTR, SLOs/SLIs).
- Execution in Ambiguity: Ability to thrive in a fast-paced, high-growth environment, managing multiple priorities and adapting to evolving technical requirements.
These could be considered Requirements (mandatory). Then Preferred Qualifications bullet list. Then Nice to Have bullet list could be considered Skills? Or we could put Skills as a separate section combining technical domain knowledge etc. But we already used them.
We need to avoid thin sections. Perhaps combine Requirements and Qualifications into one? But we need separate headings only if content exists.
We have content for About the role, Responsibilities, Requirements (the Experience block), Qualifications (Preferred Qualifications), Skills (maybe Nice to Have or Technical Domain Knowledge?), Benefits (What We Can Offer You includes benefits), Pay (salary range), Schedule (maybe not present). There's no explicit schedule info (like full-time, remote). The posting mentions flexible workplace, but not schedule specifics. Should we include Schedule? Only if posting actually states them. It mentions "Human-First Flexibility: We treat you as humans first. 🫶🏽 Our flexible workplace trusts Nscalers to deliver, giving you the autonomy to shape your day around life's moments." That's about flexibility but not explicit schedule. Might be considered schedule info? It's vague. Probably better not to include Schedule section because not explicit.
Pay: we have salary range: $250,000 USD - $303,000 USD. Also mentions bonus, equity, commission. So we can include Pay section.
Benefits: mention medical, dental, vision, flexible paid time off, parental leave, retirement plan participation. Also "Highly competitive package (base + equity) with reviews every 12 months." and "Human-First Flexibility". So we can include Benefits.
Now we need to ensure we don't repeat job title as heading. Not include Job ID etc.
We must output only HTML fragment, no markdown fences.
Let's craft:
About the role
...
Responsibilities
- ... ...
Requirements
- 5+ years of experience in a Technical Program Management role, successfully driving large-scale, complex infrastructure or physical deployment projects.
- Strong foundational understanding of data center infrastructure, distributed systems, and networking concepts.
- Proven expertise in modern program management methodologies (Agile, Scrum, PMP certification preferred); exceptional organizational, communication, and presentation skills.
- Demonstrable experience in defining, tracking, and improving system performance based on operational metrics (e.g., Uptime, Availability, MTTR, SLOs/SLIs).
- Ability to thrive in a fast-paced, high-growth environment, managing multiple priorities and adapting to evolving technical requirements.
Qualifications
- Direct experience managing programs related to data center infrastructure build-outs and hardware commissioning processes.
- Specific domain knowledge of AI/HPC infrastructure, including NVIDIA GPUs, InfiniBand/RDMA networks, and the challenges of tightly-coupled systems.
- Experience in a hyperscale or public cloud environment supporting 24/7 mission-critical services.
- Familiarity with SRE principles, automation tooling, and continuous integration/continuous deployment (CI/CD) pipelines for infrastructure.
- A Bachelor's or Master's degree in a technical field (Computer Science, Engineering, etc.) or equivalent practical experience.
- Willingness to travel occasionally to project sites as needed.
Skills
Maybe we can put Nice to Have as Skills? Or we could combine Nice to Have into Skills. Let's do Skills = Nice to Have bullet list.Skills
- Experience in hyperscale data center delivery, AI infrastructure, GPU clusters, cloud regions, or high-density compute environments.
- Experience with end-to-end data center lifecycle management, including site development, power, utilities, design, procurement, construction, commissioning, network, security, and operations handoff.
- Familiarity with data center power infrastructure, utility interconnection, substations, generators, switchgear, cooling systems, and MEP dependencies.
- Experience implementing or operating within program delivery tooling such as Smartsheet, Jira, Asana, Monday.com, MS Project, Primavera P6, Power BI, Tableau, or similar systems.
- Experience standing up or scaling a program delivery operating model in a high-growth infrastructure organization.
- PMP, PgMP, Agile, Lean Six Sigma, or similar certification preferred but not required.
Benefits
- Highly competitive package (base + equity) with reviews every 12 months.
- Human‑First Flexibility: flexible workplace trusts Nscalers to deliver, giving you autonomy to shape your day around life's moments.
- Medical, dental, vision coverage.
- Flexible paid time off.
- Parental leave.
- Retirement plan participation.
Pay
Salary range: $250,000 USD – $303,000 USD (base). Eligible for bonus, equity, and/or commission programs.
We should not include Schedule. Check that we didn't include any boilerplate like EEO, legal, etc. We removed. We need to ensure we preserve all substantive information. Did we miss any? Let's review original. Original includes: - Nscale description at start: "Nscale is the GPU cloud engineered for AI..." That's company overview; not required to include? The instruction: preserve ALL substantive information; but we can omit company overview? It's substantive but not part of sections? The instruction says we should reformat a job posting into clean HTML. Likely we should include that as part of About the role? But they said "About the role" heading for section headings. The company overview could be placed before About the role as a paragraph? There's no heading for company overview. The instruction: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Probably we should include a brief intro paragraph before the first heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we cannot have extra paragraphs outside headings. However they said "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; we can have other content like a brief intro paragraph before first heading. The company overview is substantive; we should preserve it. Let's add a
before the first heading containing the company overview. Also there is a line: "As an Nscaler, you'll build trust through openness and transparency, where everyone is inspired to do their best work. If you join our team, you'll be contributing to building the technology that powers the future." That's also part of About the role? Actually it's after company overview, before "About The Role". Could be included in About the role paragraph. Thus About the role section should include the description of the role: "The Principal Technical Program Manager, AI Physical Deployment, is a senior individual contributor ..." plus maybe the earlier motivational sentences. We'll combine. Let's extract About the role content: From posting: "About The Role The Principal Technical Program Manager, AI Physical Deployment, is a senior individual contributor responsible for driving project delivery and execution with our data center and physical deployment partners. In this hands-on leadership role, you will own key RFx processes, partner with internal cross-functional teams on contracts, drive cost efficiency initiatives, and serve as a primary escalation point for complex technical and business challenges. Acting as a strategic bridge between internal stakeholders and external partners, you will navigate vendor relationships and ensure seamless alignment to achieve core business objectives. You will partner closely with Data Center Development, Design & Construction, Engineering, Power & Utilities, Procurement, Supply Chain, Finance, Legal, Commercial, Security, Network, Operations, Project Controls, and Executive Leadership to create a single operating rhythm across complex infrastructure programs. You will be accountable for driving internal alignment, facilitating decision-making, removing blockers, and ensuring teams are coordinated from planning through operational readiness. The ideal candidate has deep, hands-on experience running strategic programs in data center infrastructure, networking, AI, construction, or mission-critical environments, and has chosen depth of craft over people management. You should be highly effective at influencing without authority, aligning senior stakeholders, translating complexity into clear decisions, and setting the delivery, governance, and controls standards others follow." That's the role description. Also preceding sentences: "As an Nscaler, you'll build trust through openness and transparency, where everyone is inspired to do their best work. If you join our team, you'll be contributing to building the technology that powers the future." Could be included. Thus About the role paragraph(s) can include both. We'll output a
containing that. Now ensure we didn't miss any responsibilities bullet list: Under "What You'll be Doing" there are two subheadings: "Internal Stakeholder Engagement & Alignment" and "Technical Leadership & Mentorship". Each has bullet-like sentences (some are long). We need to extract each bullet as
- . Let's list them: Internal Stakeholder Engagement & Alignment: - Act as the central coordination and alignment point across internal and external teams involved in data center infrastructure delivery. - Build programs