Staff Software Engineer (Network Development)

Overview

• CoreWeave runs one of the largest GPU clouds in the world, and the network underneath it has to be fast, reliable, and almost entirely self-operating. Our Network Development team builds the software that makes that possible
• We design, build, and run the platforms and services that provision, configure, automate, monitor, and heal the network, so that the people relying on it rarely have to think about it
• We are looking for a Staff Software Engineer to take ownership of these systems
• This is a software engineering role at its core
• You will spend most of your time designing and writing production software, setting technical direction, and raising the quality bar for the team
• A solid understanding of networking fundamentals is required, but deep network engineering expertise is not
• This role is about building the software that operates the network
• Own the design, development, and long‑term health of the platforms and services that automate the network, including config generation, device provisioning, workflow automation, observability tooling, and internal CLIs and APIs
• Plan and map out complex projects months in advance, sequencing the work, anticipating dependencies, and keeping several efforts moving in parallel
• Lead technical direction through RFCs, design reviews, and architecture decisions, and break ambiguous problems down into shippable work
• Write well‑tested, well‑documented software in Python and Go, and set the standard for quality across the team through strong test cases, clear error handling, and solid CI/CD practices
• Improve the reliability and operability of what we run by defining service‑level indicators and objectives and relentlessly reducing manual toil through automation
• Partner closely with Network Engineering, Observability, Fleet Engineering, and HPC teams so our automation fits cleanly into the wider system
• Join the on‑call rotation once you are ramped, and help drive calm, blameless follow‑up when things break
• Mentor other engineers, review code and designs, and help grow the technical skills of the team
• Contribute to a positive, collaborative team and organizational culture

Qualifications

• Strong understanding of managing runtime health for services and applications at an enterprise level
• A love of process automation and toil elimination, with hands‑on experience building workflow automation or orchestration systems and automated device provisioning at scale such as Zero Touch Provisioning
• 8 or more years of professional software engineering experience, ideally building and operating production infrastructure, platform, or backend systems at scale
• Strong planning skills, including the ability to lay out and drive projects across a multi‑month horizon while keeping several concurrent efforts moving as part of a team
• Strong, well‑reasoned technical opinions, paired with genuine openness to better ideas and other people’s input
• Strong proficiency in Python and Go
• Excellent written communication, a habit of writing documentation other people can actually use, and experience mentoring engineers and collaborating across teams
• Solid understanding and experience in CI/CD (testing, code review, maintaining continuous builds and deployments)
• A solid understanding of core networking fundamentals, including IP addressing and subnetting, routing/switching, NTP, and DNS
• Comfort with Linux and Kubernetes, and experience with infrastructure automation tooling such as Ansible and Jinja, a source‑of‑truth or IPAM and DCIM system such as NetBox, and observability tooling such as Prometheus and Grafana

Additional Qualities

• We believe in investing in our people, and value candidates who can bring their own diversified experiences to our teams – even if you aren’t a 100% skill or experience match.
• Here are a few qualities we’ve found compatible with our team. If some of this describes you, we’d love to talk
• A degree in Computer Science or a related field is a plus
• You explain the reasoning behind your technical choices, stay open to being convinced otherwise, and pick the right tool for the job rather than defending a favorite
• You see a problem and solve it without waiting to be asked, and you always look for ways to make things easier, faster, and more secure
• You treat problems as shared problems, keep incident culture blameless, and give credit generously