The posting, in Nebius Group's own words
archived Oct 20, 2026About Nebius:
Nebius is leading a new era in cloud infrastructure for the global AI economy. We are building a full-stack AI cloud platform that supports developers and enterprises from data and model training through to production deployment, without the cost and complexity of building large in-house AI/ML infrastructure. Built by engineers, for engineers. From large-scale GPU orchestration to inference optimization, we own the hard problems across compute, storage, networking and applied AI. Listed on Nasdaq (NBIS) and headquartered in Amsterdam, we have a global footprint with R&D hubs across Europe, the UK, North America and Israel. Our team of 1,500+ includes hundreds of engineers with deep expertise across hardware, software and AI R&D.
The Role
We're looking for a Lead Technical Project Manager for Network Infrastructure. This is not a "make slides, chase tickets, and ask engineers for status" job. It is a role for someone with an engineering skeleton: a person who has built, operated, broken and recovered things, and can earn trust in a room full of SREs, SWEs, network engineers, security and platform teams. We are at the early stage of our APAC expansion, so you will work with a high degree of independence, set up the project management practices for the region from scratch, and stay close to the technical details yourself. The "T" matters. You don't need to be the deepest expert in every area, but you should be technical enough to understand real trade-offs: why rollback is not optional, why "just automate it" can create a bigger blast radius, why a provisioning flow must survive real-world constraints, why SLOs without ownership are decoration, and why network device CI/CD is very different from deploying a stateless service. You can read a design doc, challenge missing assumptions, notice unclear failure modes, ask sharp questions, and turn a vague but important problem into an executable plan. The "P" is project delivery with a product mindset, even if the product is internal infrastructure. Your product may be a site bootstrap kit, secrets and robot-user management, an SLO framework, a firmware rollout process, a network observability platform, CI/CD for network devices, or automation that makes day-0 and day-N operations safe. The job is not done when the technical pieces exist. It is done when engineers trust the tool, the NOC actually uses the workflow, alerts are actionable, runbooks are real, and the new way becomes the default way. That means adoption, communication, documentation, feedback loops, and sometimes a bit of internal "marketing": the ability to convince smart technical people that the thing is worth using. The "M" is management of execution, not people management. You will not be responsible for engineers' careers, performance reviews or promotions. You will be responsible for making important cross-team initiatives land: defining scope, aligning owners, exposing risks, driving decisions, tracking dependencies, creating clarity where things are unclear, and making sure we ship useful outcomes instead of collecting half-finished initiatives. This is a high-leverage role in a early-stage and fast-scaling network infrastructure organisation. Many important systems are being built now: automation, observability, reliability standards, provisioning flows, operational safety, and cross-site consistency. You won't be maintaining a mature machine from the sidelines. You'll help shape how the machine works.