Senior Solution Engineer, Networking
About the role
...
Responsibilities
- ... list items from "What You Will Be Doing".
Requirements
maybe combine "What We Need To See" as Requirements. Could also have Qualifications separate. But we can put Requirements for mandatory qualifications, and Qualifications for preferred? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can decide which sections to include based on content. We have: - About the role: intro paragraph. - Responsibilities: bullet list from "What You Will Be Doing". - Requirements: bullet list from "What We Need To See" (minimum BS, 5+ years C/Python, 8+ years experience..., at least 3 years supporting end-customers, strong system software expertise, professional communication, passion for learning). - Qualifications: maybe "Ways To Stand Out From The Crowd" as Qualifications or Skills? Could be Skills. The heading "Skills" could be used for those standout items. But we also have "Qualifications" maybe for education? However we already included BS in Requirements. Could treat "Ways To Stand Out" as Skills or Qualifications. Let's map: Qualifications: maybe the education and experience? But we already used Requirements for those. Could treat Qualifications as the "Ways To Stand Out" (preferred). Or Skills as those standout items. The instruction says we can include sections only when posting has real specific content. We have content for both. We could do: - Requirements: mandatory. - Qualifications: preferred (Ways To Stand Out). - Skills: maybe not needed separately if we treat standout as Skills. But we have both Qualifications and Skills headings available; we could put standout under Skills and maybe not use Qualifications. However we have education already in Requirements; we could keep Qualifications empty? Not allowed. So we need to decide. Better: Use Requirements for mandatory, Skills for standout (preferred). Then we might not need Qualifications section. But we have education and experience in Requirements; that's fine. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We need Benefits: mention equity and benefits. Could also mention "You will also be eligible for equity and benefits." That's benefits. Pay: salary ranges. Schedule: occasional work on weekends or holidays. Now we need to preserve all substantive information. Ensure we don't lose any details. Let's extract each piece. About the role paragraph: Combine sentences: "The NVIDIA Enterprise Experience (NVEX) Solutions Engineering team is looking for a senior Computer or Software Engineer. This person will establish expertise in ground-breaking network technology used in AI clusters. Our software engineers connect customer support teams and R&D. They focus on solving tough problems from the front lines. They provide top support for high-speed interconnect technologies like InfiniBand, NVLink, and Spectrum-X that link GPUs and AI compute infrastructure." We can keep as one. Responsibilities bullet list from "What You Will Be Doing": - Assist various network and AI cluster support teams in reproducing, resolving, and root causing sophisticated customer issues - Work with R&D teams to develop bug fixes, workarounds, and solutions for critical customers using NVIDIA’s network technologies - Become an authority in NVIDIA network technologies used in AI clusters such as Infiniband, NVLink, and Spectrum-X - Analyze network performance metrics and make tuning recommendations for high-performance, lossless networks - Develop support and analysis tools to help analyze and root cause field issues - Daily use of ground breaking AI tools for software development, log and trace analysis, and source code debugging - Occasional work on weekends or holidays to support customers Note: The last bullet about occasional work could also go to Schedule, but it's also a responsibility. We'll keep it in Responsibilities as per original list, but we also need Schedule section maybe separate. However we might duplicate. Better to separate: Keep responsibilities without the occasional work, and put occasional work in Schedule. But the instruction says preserve ALL substantive information; we can place it in either section but not duplicate. Let's split: Responsibilities list excludes occasional work; Schedule includes that. Thus Responsibilities bullets (first six). Schedule bullet: "Occasional work on weekends or holidays to support customers". Now Requirements bullet list from "What We Need To See": - Minimum of a BS in Computer, Electrical, or Software Engineering (or equivalent experience) - 5+ years of experience in C or Python development on Linux platforms - 8+ years of experience developing, testing, and debugging software for one or more of the following: Linux NIC drivers, switch ASICs and SDKs, embedded network device firmware, Linux based network equipment (routers, switches, gateways, etc), network operating systems, virtual routers, SDN stacks, virtual switching, DPDK, SRIOV stacks - At least 3 years of experience directly supporting end-customers, partners, or integrators for network equipment and infrastructures - Strong system software (firmware, BIOS, kernel, driver, operating system) expertise - Professional-level communication skills, including adjusting communication to the technical level of the audience, and staying calm and focused in negative situations. - Passion for learning innovative tech and motivation to work hard on ground-breaking products Now Skills (Ways To Stand Out): - Experience developing drivers or firmware for switch and NIC ASICs - Background with AI infrastructure and HPC networking - Experience with Infiniband or other non-Ethernet network technologies - Experience developing or supporting DPUs or SmartNICs - Knowledge of HPC performance test tools and NVIDIA AI stacks (NCCL, MPI, DOCA, CUDA) Now Benefits: "You will also be eligible for equity and benefits." Could also mention equity. We'll put that. Pay: "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 - 270,250 USD for Level 4, and 200,000 USD - 322,000 USD for Level 5." We could split into two paragraphs but okay. Now Schedule: "Occasional work on weekends or holidays to support customers." Now ensure we didn't include any boilerplate: removed Job ID, Job Category, Time Type, "Join us!", "Applications for this job will be accepted at least until September 15, 2026.", "This posting is for an existing vacancy.", "NVIDIA uses AI tools in its recruiting processes.", EEO statements. Now output HTML fragment. We must not include or . Just the fragment. Let's craft:
About the role
The NVIDIA Enterprise Experience (NVEX) Solutions Engineering team is looking for a senior Computer or Software Engineer. This person will establish expertise in ground-breaking network technology used in AI clusters. Our software engineers connect customer support teams and R&D. They focus on solving tough problems from the front lines. They provide top support for high-speed interconnect technologies like InfiniBand, NVLink, and Spectrum-X that link GPUs and AI compute infrastructure.
Responsibilities
- Assist various network and AI cluster support teams in reproducing, resolving, and root causing sophisticated customer issues
- Work with R&D teams to develop bug fixes, workarounds, and solutions for critical customers using NVIDIA’s network technologies
- Become an authority in NVIDIA network technologies used in AI clusters such as Infiniband, NVLink, and Spectrum-X
- Analyze network performance metrics and make tuning recommendations for high-performance, lossless networks
- Develop support and analysis tools to help analyze and root cause field issues
- Daily use of ground breaking AI tools for software development, log and trace analysis, and source code debugging
Requirements
- Minimum of a BS in Computer, Electrical, or Software Engineering (or equivalent experience)
- 5+ years of experience in C or Python development on Linux platforms
- 8+ years of experience developing, testing, and debugging software for one or more of the following: Linux NIC drivers, switch ASICs and SDKs, embedded network device firmware, Linux based network equipment (routers, switches, gateways, etc), network operating systems, virtual routers, SDN stacks, virtual switching, DPDK, SRIOV stacks
- At least 3 years of experience directly supporting end-customers, partners, or integrators for network equipment and infrastructures
- Strong system software (firmware, BIOS, kernel, driver, operating system) expertise
- Professional-level communication skills, including adjusting communication to the technical level of the audience, and staying calm and focused in negative situations.
- Passion for learning innovative tech and motivation to work hard on ground-breaking products
Skills
- Experience developing drivers