Head of Global Customer Engineering - Internal EDA Infrastructure
NVIDIA · California, United States · 1 mo ago
RemoteRemoteEngineeringFull-time
We need to produce HTML fragment with sections: headings using for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse the job posting.
First, we need to extract sections:
- About the role: description of role: first paragraph(s) describing the team, role, etc.
- Responsibilities: bullet list of "What You’ll Be Doing" items.
- Requirements: bullet list of "What We Need To See" items.
- Qualifications: maybe education requirement? Could be part of requirements. But we can treat "Ways To Stand Out From The Crowd" as Skills or maybe "Preferred Qualifications". However we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
We have:
- About the role: The initial description: "Every NVIDIA GPU starts as a job on our internal EDA infrastructure...". That's about the role.
- Responsibilities: "What You’ll Be Doing" list: Build the leaders..., Develop the Kubernetes platform..., Ship the L0 AI support layer..., Set the bar..., Stay close to the metal...
- Requirements: "What We Need To See" list: 12+ overall years..., 5+ years..., Proven ability..., Deep technical familiarity..., Track record..., Exceptional communication skills..., A Bachelor’s degree...
- Qualifications: Could be the education requirement (Bachelor's degree) but that's already in requirements. Could treat "Ways To Stand Out From The Crowd" as Skills or Preferred Qualifications. The heading "Skills" could capture those standout ways.
- Benefits: The posting mentions "You will also be eligible for equity and benefits." Also earlier: "NVIDIA is considered one of the technology world’s most desirable employers..." but not specific benefits. There's mention of equity and benefits generically. Also "Your base salary will be determined..." and salary range. So we have Pay section.
- Schedule: Not mentioned. No schedule info. So we should not include Schedule.
- Benefits: We have mention of equity and benefits, but not detailed. However we can include a Benefits section with that statement? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting says "You will also be eligible for equity and benefits." That's specific enough? It states eligibility for equity and benefits. That's real content. So we can include Benefits section with that sentence.
- Pay: The posting includes base salary range: "Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 272,000 USD - 431,250 USD for Level 4, and 320,000 USD - 488,750 USD for Level 5." That's specific. So include Pay section.
- Schedule: none, omit.
- Skills: The "Ways To Stand Out From The Crowd" list: Led a platform team and a customer facing team simultaneously..., You’ve architected “self-healing” support ecosystems..., You’ve led the full lifecycle of generative AI / LLM-based support assistants..., Run LSF, Slurm, or Kubernetes at a scale where manual intervention was the bottleneck... These are skills/experience that stand out. So we can put them under Skills.
- Qualifications: Could be the Bachelor's degree requirement. But we already have that in Requirements. However we could separate Qualifications as education: "A Bachelor’s degree in a relevant engineering field or equivalent experience." That is a qualification. We'll include Qualifications section with that.
But we need to avoid duplication. The Requirements list includes that as last item. If we put it also in Qualifications, it's duplication. Better to keep Requirements as the list of requirements (including years, experience, etc.) and Qualifications as education only. However the requirement list includes education; we could move education to Qualifications and keep other items in Requirements. That seems reasonable.
Thus:
- About the role: paragraph(s) from start up to "What You’ll Be Doing". Let's capture the descriptive paragraphs before that heading.
The text:
"Every NVIDIA GPU starts as a job on our internal EDA infrastructure. Thousands of hardware engineers designing next-generation silicon depend on it being fast, available, and frictionless and when it isn’t, tapeout schedules feel it. This team is the difference. We’re hiring a hands-on engineering leader to develop our Global Customer Engineering for Internal EDA Infrastructure - the organization sitting directly between our chip designers and the platforms they run on. This is a multi-team leadership role spanning managers and tech leads across a globally distributed organization, and it comes with two co-equal mandates: A world-class customer engineering organization for EDA infrastructure - reactive when it must be, proactive by design. The Kubernetes platform team that delivers one of our customer services end to end. You will design software solutions, and automation pipelines to eliminate operational overhead. When encountering recurring toil for customer engineering, your immediate impulse is to engineer permanent automated remedies. Staying directly connected to live production environments is essential hence the end-to-end Kubernetes platform responsibility."
That's the About the role.
Then "What You’ll Be Doing" list.
Then "What We Need To See" list.
Then "Ways To Stand Out From The Crowd" list.
Then later paragraphs about NVIDIA, salary, equity, benefits, application deadline, etc. We need to remove boilerplate like EEO, etc. Also remove "Applications for this job will be accepted at least until September 19, 2026." That's application instruction, should be removed per rule: remove application instructions. Also remove "NVIDIA uses AI tools in its recruiting processes." etc. Also remove equal opportunity boilerplate. Also remove the trailing ", , JR2025101". So we keep only substantive content: About the role, Responsibilities, Requirements, Qualifications (education), Skills (standout ways), Benefits (equity and benefits), Pay (salary range). Possibly also a short paragraph about NVIDIA's mission? That's more fluff but could be considered part of About the role? It's generic marketing. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The NVIDIA mission statements might be considered boilerplate but not explicitly listed. However they are generic fluff; but they are not legal/EEO. Might be okay to keep? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. The mission statements are substantive? They are more like marketing fluff but still part of posting. I'd keep them maybe as part of About the role? But they appear after the "Ways To Stand Out..." section: "NVIDIA is leading the way in groundbreaking developments in Artificial Intelligence, High-Performance Computing, and Visualization. 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 seeking exceptional individuals like you to help us drive the next wave of artificial intelligence. NVIDIA is considered one of the technology world’s most desirable employers. We have some of the most forward-thinking and hardworking people on the planet working for us. If you are creative and autonomous, we want to hear from you!" This is generic but could be considered part of the company description. It's not strictly required but could be kept. However the instruction to prefer a few substantive sections over many thin ones. Might be okay to include as part of About the role or maybe a separate section "About NVIDIA"? Not in allowed headings. So we could append to About the role.
But we must not include application instructions or EEO etc. So we will cut after salary/benefits.
Thus final HTML:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content.
We need to parse the job posting.
First, we need to extract sections:
- About the role: description of role: first paragraph(s) describing the team, role, etc.
- Responsibilities: bullet list of "What You’ll Be Doing" items.
- Requirements: bullet list of "What We Need To See" items.
- Qualifications: maybe education requirement? Could be part of requirements. But we can treat "Ways To Stand Out From The Crowd" as Skills or maybe "Preferred Qualifications". However we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
We have:
- About the role: The initial description: "Every NVIDIA GPU starts as a job on our internal EDA infrastructure...". That's about the role.
- Responsibilities: "What You’ll Be Doing" list: Build the leaders..., Develop the Kubernetes platform..., Ship the L0 AI support layer..., Set the bar..., Stay close to the metal...
- Requirements: "What We Need To See" list: 12+ overall years..., 5+ years..., Proven ability..., Deep technical familiarity..., Track record..., Exceptional communication skills..., A Bachelor’s degree...
- Qualifications: Could be the education requirement (Bachelor's degree) but that's already in requirements. Could treat "Ways To Stand Out From The Crowd" as Skills or Preferred Qualifications. The heading "Skills" could capture those standout ways.
- Benefits: The posting mentions "You will also be eligible for equity and benefits." Also earlier: "NVIDIA is considered one of the technology world’s most desirable employers..." but not specific benefits. There's mention of equity and benefits generically. Also "Your base salary will be determined..." and salary range. So we have Pay section.
- Schedule: Not mentioned. No schedule info. So we should not include Schedule.
- Benefits: We have mention of equity and benefits, but not detailed. However we can include a Benefits section with that statement? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting says "You will also be eligible for equity and benefits." That's specific enough? It states eligibility for equity and benefits. That's real content. So we can include Benefits section with that sentence.
- Pay: The posting includes base salary range: "Your base salary will be determined based on your location, experience, and the pay of employees in similar positions. The base salary range is 272,000 USD - 431,250 USD for Level 4, and 320,000 USD - 488,750 USD for Level 5." That's specific. So include Pay section.
- Schedule: none, omit.
- Skills: The "Ways To Stand Out From The Crowd" list: Led a platform team and a customer facing team simultaneously..., You’ve architected “self-healing” support ecosystems..., You’ve led the full lifecycle of generative AI / LLM-based support assistants..., Run LSF, Slurm, or Kubernetes at a scale where manual intervention was the bottleneck... These are skills/experience that stand out. So we can put them under Skills.
- Qualifications: Could be the Bachelor's degree requirement. But we already have that in Requirements. However we could separate Qualifications as education: "A Bachelor’s degree in a relevant engineering field or equivalent experience." That is a qualification. We'll include Qualifications section with that.
But we need to avoid duplication. The Requirements list includes that as last item. If we put it also in Qualifications, it's duplication. Better to keep Requirements as the list of requirements (including years, experience, etc.) and Qualifications as education only. However the requirement list includes education; we could move education to Qualifications and keep other items in Requirements. That seems reasonable.
Thus:
- About the role: paragraph(s) from start up to "What You’ll Be Doing". Let's capture the descriptive paragraphs before that heading.
The text:
"Every NVIDIA GPU starts as a job on our internal EDA infrastructure. Thousands of hardware engineers designing next-generation silicon depend on it being fast, available, and frictionless and when it isn’t, tapeout schedules feel it. This team is the difference. We’re hiring a hands-on engineering leader to develop our Global Customer Engineering for Internal EDA Infrastructure - the organization sitting directly between our chip designers and the platforms they run on. This is a multi-team leadership role spanning managers and tech leads across a globally distributed organization, and it comes with two co-equal mandates: A world-class customer engineering organization for EDA infrastructure - reactive when it must be, proactive by design. The Kubernetes platform team that delivers one of our customer services end to end. You will design software solutions, and automation pipelines to eliminate operational overhead. When encountering recurring toil for customer engineering, your immediate impulse is to engineer permanent automated remedies. Staying directly connected to live production environments is essential hence the end-to-end Kubernetes platform responsibility."
That's the About the role.
Then "What You’ll Be Doing" list.
Then "What We Need To See" list.
Then "Ways To Stand Out From The Crowd" list.
Then later paragraphs about NVIDIA, salary, equity, benefits, application deadline, etc. We need to remove boilerplate like EEO, etc. Also remove "Applications for this job will be accepted at least until September 19, 2026." That's application instruction, should be removed per rule: remove application instructions. Also remove "NVIDIA uses AI tools in its recruiting processes." etc. Also remove equal opportunity boilerplate. Also remove the trailing ", , JR2025101". So we keep only substantive content: About the role, Responsibilities, Requirements, Qualifications (education), Skills (standout ways), Benefits (equity and benefits), Pay (salary range). Possibly also a short paragraph about NVIDIA's mission? That's more fluff but could be considered part of About the role? It's generic marketing. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The NVIDIA mission statements might be considered boilerplate but not explicitly listed. However they are generic fluff; but they are not legal/EEO. Might be okay to keep? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. The mission statements are substantive? They are more like marketing fluff but still part of posting. I'd keep them maybe as part of About the role? But they appear after the "Ways To Stand Out..." section: "NVIDIA is leading the way in groundbreaking developments in Artificial Intelligence, High-Performance Computing, and Visualization. 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 seeking exceptional individuals like you to help us drive the next wave of artificial intelligence. NVIDIA is considered one of the technology world’s most desirable employers. We have some of the most forward-thinking and hardworking people on the planet working for us. If you are creative and autonomous, we want to hear from you!" This is generic but could be considered part of the company description. It's not strictly required but could be kept. However the instruction to prefer a few substantive sections over many thin ones. Might be okay to include as part of About the role or maybe a separate section "About NVIDIA"? Not in allowed headings. So we could append to About the role.
But we must not include application instructions or EEO etc. So we will cut after salary/benefits.
Thus final HTML:
About the role
Every NVIDIA GPU starts as a job on our internal EDA infrastructure. Thousands of hardware engineers designing next-generation silicon depend on it being fast, available, and frictionless and when it isn’t, tapeout schedules feel it. This team is the difference. We’re hiring a hands-on engineering leader to develop our Global Customer Engineering for Internal EDA Infrastructure - the organization sitting directly between our chip designers and the platforms they run on. This is a multi-team leadership role spanning managers and tech leads across a globally distributed organization, and it comes with two co-equal mandates: A world-class customer engineering organization for EDA infrastructure - reactive when it must be, proactive by design. The Kubernetes platform team that delivers one of our customer services end to end. You will design software solutions, and automation pipelines to eliminate operational overhead. When encountering recurring toil for customer engineering, your immediate impulse is to engineer permanent automated remedies. Staying directly connected to live production environments is essential hence the end-to-end Kubernetes platform responsibility.
Responsibilities
- Build the leaders. Grow and develop the leaders running a globally distributed team of customer-facing engineers who own the reactive support queue for EDA infrastructure - escalating into service engineering with clean, high-quality signal.
- Develop the Kubernetes platform. Run the K8s platform team as a first-class customer engineering service: availability, roadmap, developer experience, and the operational excellence behind it.
- Ship the L0 AI support layer. Own the evolution of our AI support agent from FAQ bot to a system that safely resolves real issues against real internal systems - and measurably removes volume from human queues.
- Set the bar. Define and defend SLOs for operational performance, and win genuine stakeholder buy-in.
- Stay close to the metal. Drive deep support and continuous improvement across EDA job schedulers (LSF/Slurm), Kubernetes platforms, and the internal LLM harnesses our chip designers depend on.
Requirements
- 12+ overall years building and leading engineering support organizations, spanning reactive and proactive customer engineering.
- 5+ years of experience leading a globally distributed organization, including developing managers and leaders.
- Proven ability to influence technical roadmaps by turning support trends into engineering requirements that actually ship.
- Deep technical familiarity with Kubernetes, EDA workloads, job schedulers, and AI/LLM infrastructure foundations.
- Track record of leveraging automation and AI/ML to improve support efficiency and drive ticket volume down.
- Exceptional communication skills - credible with individual engineers and executive leadership in the same day.
Qualifications
A Bachelor’s degree in a relevant engineering field or equivalent experience.
Skills
- Led a platform team and a customer facing team simultaneously, and made each one better because of the other.
- You’ve architected “self-healing” support ecosystems where a customer engineering team builds and owns the tools it runs on including “shift-left” tooling that resolved issues before a ticket ever existed.
- You’ve led the full lifecycle of generative AI / LLM-based support assistants, well beyond basic chatbots, into systems that integrate deeply and safely with internal infrastructure.
- Run LSF, Slurm, or Kubernetes at a scale where manual intervention was the bottleneck and you personally led the automation that removed it.
Benefits
You will also be eligible for equity and benefits.
Pay
Your base salary will be determined based on your location, experience, and the pay