> Markdown version of [/jobs/ext/4771115-software-engineer-collective-communication-and-network-performance](https://www.wearedevelopers.com/jobs/ext/4771115-software-engineer-collective-communication-and-network-performance). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer, Collective Communication and Network Performance - **Company:** NVIDIA Corporation - **Location:** Santa Clara, CA, United States - **Experience:** Expert - **Salary:** $172,500 - $338,000 - **Contract:** Permanent contract - **Skills:** C++ (Programming Language), Code Review, Computer Engineering, Network Congestion, Software Debugging, Programming Tools, InfiniBand, Python (Programming Language), Remote Direct Memory Access, Software Engineering, Graphics Processing Unit (GPU), High Performance Computing, Information Technology - **Published:** November 18, 2026 - **Apply:** https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Software-Engineer--Collective-Communication-and-Network-Performance_JR2030158 ## About the Role * Bachelor's degree in Computer Science, Computer Engineering, or a related field, or equivalent experience. * 8+ years of relevant software engineering experience, including hands-on work on a collective communication library, an RDMA transport, or network performance for GPU or HPC workloads. * Working knowledge of how NCCL or a comparable library operates: algorithms, protocols, channels, transports and topology detection, and how each affects latency and bandwidth. * Working knowledge of RDMA networking in practice: InfiniBand or RoCE, NIC and switch counters, congestion control, and the tools used to measure them. * Demonstrated experience diagnosing a multi-node communication problem from measurements, proving the cause, and turning that diagnosis into software used by others. * Proven history of landing changes in code owned by other teams, from defining requirements to delivery. * Strong debugging skills across component boundaries, with changes validated through code review, tests and independent measurements, including when using automated development tools. * Proficiency in C++ and Python, and clear communication of evidence, uncertainty and next steps to engineers and users. Ways to stand out from the crowd: * Contributions to NCCL, UCX, libfabric, NVSHMEM or a comparable communication library, or to their profiling and tuner plugins. * Experience with point-to-point and expert-parallel communication paths such as NIXL, DeepEP or NVSHMEM, or with fabrics such as EFA. * Experience building detection or root-cause analysis that ran in production, with insight into its precision and recall. * Experience operating or debugging training or inference jobs above a thousand GPUs, including hang localization.