Technical Program Manager, Cloud Infrastructure

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. First, job title: Technical Program Manager (TPM) but we must not repeat job title as heading. We need to include sections: - About the role: likely the introductory paragraph(s) describing role, mission, etc. The posting includes: "NVIDIA's deep learning platforms are at the forefront of innovation... We're seeking an accomplished and highly skilled Technical Program Manager (TPM) to join our NVIDIA DGX Cloud team. This is an exciting opportunity for a passionate, focused, and creative individual to provide outstanding value to our DGX Cloud customers. We are specifically looking for a TPM with extensive background in cloud infrastructure bring-up with external partners. You will play a key role in collaborating with CSPs, emerging cloud providers and engineering teams internally to help build AI capacity and infrastructure across the globe!" That's about the role. - Responsibilities: The "What You'll Be Doing" and "Your Responsibilities Will Include" sections. We need to list bullet points. - Requirements: The "What We Need To See" section: list of requirements. - Qualifications: Possibly the "BS or MS in Electrical Engineering or Computer Science, or equivalent experience." Could be part of requirements but we can separate. - Skills: Possibly the "Ways To Stand Out From The Crowd" includes additional skills/knowledge. - Benefits: The posting mentions "We offer attractive compensation and an extensive benefits package. While planning your future, explore what we provide for you and your loved ones at www.nvidiabenefits.com/". Also mentions equity and benefits. No specific benefits listed, but we have mention of benefits package. However rule: do NOT create Benefits section unless posting actually states them. It states "attractive compensation and an extensive benefits package" and link. That's somewhat generic but still states benefits. Might be considered content. However we need to avoid filler like "commensurate with experience". This is not filler; it's a statement about benefits. We could include a Benefits section with a paragraph describing that they offer attractive compensation and extensive benefits package, and link. - Pay: The posting includes base salary range: "The base salary range is 168,000 USD - 258,750 USD for Level 4, and 200,000 USD - 322,000 USD for Level 5. You will also be eligible for equity and benefits." That's specific pay info. So include Pay section. - Schedule: The posting mentions "Time Type Full time". That's schedule info. So include Schedule section with "Full time". Also maybe location? Not needed. We must not include boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Also remove duplicated lines. We need to preserve all substantive information; do not invent or summarize away detail. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which content goes into lists vs prose. For About the role: likely prose paragraph(s). Could be multiple paragraphs but we can combine into one

  . For Responsibilities: list of duties. Use

  • . For Requirements: list of requirements. Use
    • . For Qualifications: maybe list? It's just degree requirement. Could be

      or

      . Since it's a single item, could be

      . But rule: use

      • for any list of duties/requirements/benefits. If it's not a list, we can use

        . We'll decide. For Skills: list of ways to stand out. Use

        • . For Benefits: maybe a paragraph describing benefits and link. For Pay: paragraph with salary ranges. For Schedule: paragraph with "Full time". We must not repeat job title as heading. Also do not put Job ID/requisition numbers as headings. We need to output only HTML fragment, no /, no markdown fences. Let's extract content precisely. About the role: Paragraph: "NVIDIA's deep learning platforms are at the forefront of innovation, profoundly impacting various fields and widely adopted by leading academic institutions, startups, and major Internet companies globally. We're seeking an accomplished and highly skilled Technical Program Manager (TPM) to join our NVIDIA DGX Cloud team. This is an exciting opportunity for a passionate, focused, and creative individual to provide outstanding value to our DGX Cloud customers. We are specifically looking for a TPM with extensive background in cloud infrastructure bring-up with external partners. You will play a key role in collaborating with CSPs, emerging cloud providers and engineering teams internally to help build AI capacity and infrastructure across the globe!" We can keep as one

          . Responsibilities: From "What You'll Be Doing" and "Your Responsibilities Will Include". Let's extract bullet points. What You'll Be Doing: - As a DGX Cloud Technical Program Manager, you'll be a key partner to our Engineering, Infrastructure, Software teams and their leadership, driving critical programs related to AI capacity enablement and management. - You'll play a pivotal role in developing and maturing foundational capabilities and processes for DGX Cloud, spanning critical areas such as cluster/capacity bring-up including CPU, storage, networking and compute requirements to support GPUs. - This is a dynamic, fast-paced environment where TPMs are encouraged to apply fungible abilities to a range of high-impact programs within the DGX Cloud ecosystem. Your Responsibilities Will Include: - Working in close coordination with storage engineering and network engineering teams to define and communicate requirements to CSP (Cloud Service Providers) and NCP’s (NVIDIA Cloud Providers). - Drive alignment and a POR for capacity blocks based on workload needs. - Drive early engagement with CSP (Cloud Service Providers) and NCP’s (NVIDIA Cloud Providers) to understand their managed storage, network solutions and influence alignment with NVIDIA Cloud roadmap - Gathering technical requirements, developing comprehensive roadmaps, establishing clear turning points, and ensuring adherence to our Product Lifecycle (PLC) process. - Managing ongoing capacity operations and the engineering engagement with CSP (Cloud Service Providers) and NCP’s (NVIDIA Cloud Provider) partners, collaborating closely with engineering leads. Focus on availability, maintenance and other critical performance indicators. - Partner closely within NVIDIA to understand workload requirements and related hardware and infrastructure needs. This includes speeds and feeds to optimize infrastructure readiness with cloud vendors and NVIDIA Cloud Providers. - Demonstrating Jira and other program management platforms to instill rigor and structure in the management of engineering deliverables. - Identifying and driving opportunities to onboard the adoption of third-party and in-house cloud infrastructure solutions for deployments, support, security, compliance and observability across DGX Cloud - Establishing key performance indicators (KPIs) and quantitatively demonstrating the value and impact delivered by your programs. - Proactively identifying, resolving, and mitigating risks and issues that could affect scope, schedule, and quality across all program aspects. - Encouraging a culture of continuous improvement, consistently seeing opportunities for process improvements within our cloud infrastructure operations. We need to ensure we preserve all details. Some bullet points have minor typos (NCP’s). We'll keep as is. We'll combine both sets into one list. Requirements: From "What We Need To See": - 10+ years of technical program management experience. - You have driven the planning and execution of large-scale cloud infrastructure programs with outside organizations. - You focus strongly on software engineering projects within a matrixed organization. - Extensive hands-on experience in cloud infrastructure, preferably gained from working at a major Cloud Service Provider (CSP). - Domain knowledge in the bring-up and end to end operations of compute, storage and GPU (including common failure points at the HW and SW levels). - Expert-level proficiency with Jira, Smartsheet, or similar program management tools, with the ability to expertly guide engineering teams on their use of the tools. - Outstanding strategic and tactical thinking abilities, coupled with a strong capacity to build consensus and drive program success - Comfort and efficiency in growing within ambiguous environments. - Possess excellent communication and technical presentation skills, particularly for executive audiences. - BS or MS in Electrical Engineering or Computer Science, or equivalent experience. Note that the last bullet about degree could be considered qualification but we can keep in Requirements or separate Qualifications. The instruction says we can have Qualifications section. Let's separate: Requirements: the experience/skills; Qualifications: education. Thus Requirements list excludes the degree bullet. Qualifications: - BS or MS in Electrical Engineering or Computer Science, or equivalent experience. Skills: From "Ways To Stand Out From The Crowd": - In depth knowledge of NVIDIA GPU products, including deployment and bring-up - Working knowledge of various cloud technologies (Kubernetes, API integration, Terraform, etc) - A highly enthusiastic, lively, responsive, and passionate individual who actively notices and addresses process improvement opportunities. - Significant experience with productivity tools and process automation is a major plus. - Deep familiarity with cloud-native product / services environments and familiarity with AI, ML infrastructure, and cloud/services We'll keep as list. Benefits: From posting: "We offer attractive compensation and an extensive benefits package. While planning your future, explore what we provide for you and your loved ones at www.nvidiabenefits.com/ We have some of the most forward-thinking and hardworking people in the world working for us. If you're creative and autonomous, we want to hear from you! Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 168,000 USD - 258,750 USD for Level 4, and 200,000 USD - 322,000 USD for Level 5. You will also be eligible for equity and benefits." But we already extracted Pay. Benefits: "We offer attractive compensation and an extensive benefits package. While planning your future, explore what we provide for you and your loved ones at www.nvidiabenefits.com/". Also "You will also be eligible for equity and benefits." That's somewhat overlapping with pay. But we can keep Benefits section with that sentence. We should not include the salary details in Benefits; they go to Pay. Thus Benefits paragraph: "We offer attractive compensation and an extensive benefits package. While planning your future, explore what we provide for you and your loved ones at www.nvidiabenefits.com/ You will also be eligible for equity and benefits." But note "You will also be eligible for equity and benefits." is also in Pay section? We'll keep it in Benefits maybe. However Pay section already mentions equity. To avoid duplication, we could keep equity in Pay and benefits in Benefits. But the sentence "You will also be eligible for equity and benefits." mentions both. We could split: Pay includes base salary range and equity eligibility; Benefits includes attractive compensation and extensive benefits package and link. However the instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's in original? But we should avoid repeating same info unnecessarily? Not explicitly forbidden. But better to keep each piece once. Let's parse: The paragraph: "Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 168,000 USD - 258,750 USD for Level 4, and 200,000 USD - 322,000 USD for Level 5. You will also be eligible for equity and benefits." Thus equity and benefits mentioned together with base salary. So we could put equity in Pay section, and benefits in Benefits section. The phrase "You will also be eligible for equity and benefits." could be split: we could mention equity in Pay, and benefits in Benefits. But we need to preserve the detail that they are eligible for equity and benefits. If we separate, we still preserve both details