Senior AI Infrastructure Software Engineer - DGX Cloud

We need to output HTML fragment with sections for headings: About the role, Responsibilities? Actually headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. We must not repeat job title. Remove boilerplate like EEO, legal, application instructions, etc. Keep substantive info. Let's parse the posting: - Intro paragraph: "Joining NVIDIA's DGX Cloud Lepton Team means contributing to the leading cloud product that powers innovative AI research and developers. We focus on building the AI/ML platform for improving productivity, optimizing efficiency and resiliency of AI workloads, as well as developing scalable AI infrastructure services globally. We are seeking an AI infrastructure software engineer to join our team. You'll be instrumental in designing, building, and maintaining AI platforms that enable large-scale AI training, inferencing, fine-tuning, and Agentic AI in production. As a senior DGX Cloud AI Infrastructure software engineer at NVIDIA, you will have the opportunity to work on innovative technologies that power the future of AI and be part of a dynamic and supportive team that values learning and growth. The role provides the autonomy to work on meaningful projects with the support and mentorship needed to succeed, and contributes to a culture of blameless postmortems, iterative improvement, and risk-taking. If you are seeking an exciting and rewarding career that makes a difference, we invite you to apply now!" That's about the role. Could be "About the role". We'll put that in

About the role

then

with that paragraph. - Then "What You’ll Be Doing" list: bullet points: Develop platform and tools for large-scale AI, LLM, and GenAI infrastructure. Develop and optimize tools to improve AI/ML workload efficiency and resiliency. Root cause and analyze and triage failures from the application level to the hardware level Enhance infrastructure and products underpinning NVIDIA's AI platforms. Co-design and implement APIs for integration with NVIDIA's resiliency stacks on the platform. Define meaningful and actionable reliability metrics to track and improve system and service reliability. Skilled in problem-solving, root cause analysis, and optimization. These are responsibilities. So

Responsibilities

• each. - Then "What We Need To See" list: Minimum of 8+ years of experience in developing software infrastructure for large scale AI systems. Bachelor's degree or higher in Computer Science or a related technical field (or equivalent experience). Strong debugging skills and experience in analyzing and triaging AI applications from the application level to the hardware level. Proven track record in building and scaling large-scale distributed systems. Experience with AI training and inferencing and data infrastructure services. Familiar in Kubernetes and operating large-scale observability platforms for monitoring and logging (e.g., ELK, Prometheus, Loki). Proficiency in programming languages such as Golang, Python, C/C++, script languages Excellent communication and collaboration skills, and a culture of diversity, intellectual curiosity, problem solving, and openness are essential. These are requirements/qualifications. Could split into Requirements and Qualifications? The instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide based on content. The list includes experience, education, debugging, track record, experience with AI training/inferencing, Kubernetes, observability, proficiency in languages, communication skills. Could treat as Requirements (minimum qualifications) and maybe Skills (technical skills). But we can also put all under Requirements. However we should avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But we have separate headings allowed. We need to include a section only when posting has real specific content for it. We have content for Requirements (experience, education) and Qualifications (maybe same). Could split: Requirements: Minimum of 8+ years experience, Bachelor's degree, Strong debugging skills, Proven track record, Experience with AI training/inferencing, Familiar with Kubernetes/observability, Proficiency in programming languages. Qualifications: Excellent communication and collaboration skills, and a culture of diversity, intellectual curiosity, problem solving, and openness are essential. That seems a bit forced but okay. Alternatively, we could have Requirements (experience/education) and Skills (technical skills). Let's see: The list includes technical skills: debugging, distributed systems, AI training/inferencing, Kubernetes, observability, languages. Also communication skills could be under Skills as well. But we have separate Skills heading. Could put technical skills under Skills, and maybe Requirements for experience/education. Let's decide: - Requirements: Minimum of 8+ years experience, Bachelor's degree or higher. - Qualifications: Strong debugging skills, proven track record, experience with AI training/inferencing, familiarity with Kubernetes/observability, proficiency in languages. - Skills: Excellent communication and collaboration skills, and a culture of diversity, intellectual curiosity, problem solving, and openness are essential. But the instruction says "Prefer a few substantive sections over many thin ones." Having three sections may be okay if each has substantive content. Let's see each: Requirements: two items (experience, education) - maybe thin but still substantive. Qualifications: many items (debugging, track record, AI training/inferencing, Kubernetes/observability, languages) - substantive. Skills: communication etc - maybe thin but still substantive. Alternatively combine Requirements and Qualifications into one "Requirements" section and put communication under Skills. That yields two sections: Responsibilities, Requirements (including experience, education, technical skills), Skills (soft skills). That seems better. Let's do:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...
  (include experience, education, debugging, track record, AI training/inferencing, Kubernetes/observability, languages)

  Skills

  ...
  (communication, collaboration, diversity, intellectual curiosity, problem solving, openness) We should not include Benefits, Pay, Schedule unless posting actually states them. The posting mentions base salary range and equity and benefits. It says: "Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 184,000 USD - 287,500 USD for Level 4, and 224,000 USD - 356,500 USD for Level 5. You will also be eligible for equity and benefits." That is specific pay info. So we should include a Pay section with that info. Also benefits mentioned: equity and benefits (generic). Could include Benefits section? It mentions equity and benefits but not details. Might be considered not specific enough? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay range and equity and benefits. So we can include Pay section with the salary ranges. Benefits: "You will also be eligible for equity and benefits." That's vague but still states eligibility for equity and benefits. Could include Benefits section with that line. However we should avoid filler like "not specified". This is specific enough: equity and benefits. We'll include Benefits. Schedule: not mentioned, so omit. Now we need to remove boilerplate: EEO, legal, application instructions, etc. Also remove duplicated lines, cookie/navigation. Also remove the job ID/requisition numbers (JR2018042) and the line about applications accepted until Sep 20 2026? That's application instruction? It's a date; maybe considered application instruction? The instruction says remove application instructions. The line "Applications for this job will be accepted at least until September 20, 2026." is an application instruction (deadline). Remove. Also "This posting is for an existing vacancy." maybe metadata; could drop. Also "NVIDIA uses AI tools in its recruiting processes." maybe boilerplate; drop. Also EEO statement drop. Also remove the repeated lines like "NVIDIA leads the way..." paragraph about GPU etc. That's generic company description; could be considered boilerplate? It's not about the role specifically but about NVIDIA. Might be considered boilerplate; but it's substantive about company? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description may not be boilerplate but it's generic. However it's not about the role; but it's still substantive info about NVIDIA. Might be okay to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive about NVIDIA. It's not boilerplate per se. However it's not directly about the role but could be considered "About the company". There's no heading for that. We could incorporate into About the role paragraph? But we already have About the role paragraph; we could add that as additional paragraph. However the instruction says prefer a few substantive sections over many thin ones. Adding another paragraph under About the role is fine. But we need to decide if we keep that paragraph. It says: "NVIDIA leads the way in groundbreaking developments in Artificial Intelligence, High-Performance Computing, and Visualization. The GPU, our invention, serves as the visual cortex of modern computers and is at the heart of our products and services. Our work opens up new universes to explore, enables amazing creativity and discovery, and powers what were once science fiction inventions, from artificial intelligence to autonomous cars. NVIDIA is looking for exceptional people like you to help us accelerate the next wave of artificial intelligence." This is generic marketing but still substantive about NVIDIA. I'd keep it as part of About the role. Now we need to ensure we don't repeat job title as heading. We didn't. Now produce HTML fragment. Let's craft About the role paragraph: combine the intro paragraph and the NVIDIA description. Intro: "Joining NVIDIA's DGX Cloud Lepton Team means contributing to the leading cloud product that powers innovative AI research and developers. We focus on building the AI/ML platform for improving productivity, optimizing efficiency and resiliency of AI workloads, as well as developing scalable AI infrastructure services globally. We are seeking an AI infrastructure software engineer to join our team. You'll be instrumental in designing, building, and maintaining AI platforms that enable large-scale AI training, inferencing, fine-tuning, and Agentic AI in production. As a senior DGX Cloud AI Infrastructure software engineer at NVIDIA, you will have the opportunity to work on innovative technologies that power the future of AI and be part of a dynamic and supportive team that values learning and growth. The role provides the autonomy to work on meaningful projects with the support and mentorship needed to succeed, and contributes to a culture of blameless postmortems, iterative improvement, and risk-taking. If you are seeking an exciting and rewarding career that makes a difference, we invite you to apply now!" Then NVIDIA description: "NVIDIA leads the way in groundbreaking developments in Artificial Intelligence, High-Performance Computing, and Visualization. The GPU, our invention, serves as the visual cortex of modern computers and is at the heart of our products and services. Our work opens up new universes to explore, enables amazing creativity and discovery, and powers what were once science fiction inventions, from artificial intelligence to autonomous cars. NVIDIA is looking for exceptional people like you to help us accelerate the next wave of artificial intelligence." Combine into one

  maybe two paragraphs but we can put both in same

  separated by space. Now Responsibilities list items as given. Now Requirements list: Let's decide items: - Minimum of 8+ years of experience in developing software infrastructure for large scale AI systems. - Bachelor's degree or higher in Computer Science or a related technical field (or equivalent experience). - Strong debugging skills and experience in analyzing and triaging AI applications from the application level to the hardware level. - Proven track record in building and scaling large-scale distributed systems. - Experience with AI training and inferencing and data infrastructure services