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.

Your responsibilities will include:

• Own end-to-end delivery of cross-team network infrastructure initiatives in APAC, from a vague problem statement to an executable plan to adoption
• Define scope and success criteria, align owners across SRE, SWE, network, security, platform and data center teams, and drive decisions to closure
• Review designs and technical proposals, challenge missing assumptions, and surface failure modes, dependencies and risks early
• Track dependencies and risks across teams and time zones, and keep stakeholders, including the European teams, informed with clear, honest status
• Drive adoption: make sure tools and workflows become the default way of working, with real documentation, runbooks and feedback loops
• Establish and run lightweight, effective project management practices for the region: planning, prioritization, reviews, and post-launch follow-up
• Work with regional teams and external partners (vendors, carriers) on the rollout of new network capabilities
• Turn operational pain and engineering input into a clear, prioritized backlog

We expect you to have:

• 7+ years of experience in technical project management, engineering management or a hands-on engineering role (SRE, SWE, network or infrastructure), with a track record of delivering complex cross-team infrastructure projects
• A real engineering background: you have built and operated production systems and can earn the trust of deeply technical teams
• Ability to read design docs and technical proposals, understand trade-offs, and ask sharp questions about reliability, rollback, blast radius and failure modes
• Strong understanding of infrastructure fundamentals (Linux, networking, automation, CI/CD) at the level needed to hold your own in technical discussions
• Proven ability to drive decisions and create clarity in ambiguous, fast-changing environments without formal authority
• Excellent written and verbal communication, including documenting plans and decisions and influencing smart technical people
• Ability to work independently in an early-stage environment and to build processes from scratch
• Professional working proficiency in English (spoken and written) and comfort working across time zones

It will be an added bonus if you have:

• Experience with network infrastructure: network automation, observability, or network device lifecycle management
• Experience with SLO/SLI frameworks, incident management, or production readiness processes
• Experience with CI/CD or change management for network or other high-blast-radius infrastructure
• Experience delivering projects with distributed teams across APAC time zones
• Experience with secrets and access management, firmware rollout or fleet-wide operational initiatives
• Hands-on engineering contributions (scripts, tooling, automation) alongside project work

Examples of initiatives you may own:

• A user and secrets management system for network infrastructure, including robot-user lifecycle, safe key/password rotation, revocation, break-glass access, mixed agent/push-based device support, and integration with existing secrets backends
• An SLO framework for network services and components, including SLIs, SLOs, dashboards, alerts, ownership, tiering, and a clear link between reliability targets and engineering investment
• CI/CD for network devices, where configuration changes, validation, staged rollout, rollback, and blast-radius control become disciplined and repeatable instead of manual and risky
• Fleet-wide operational initiatives such as firmware consistency, device lifecycle hygiene, observability coverage, monitoring quality, alert ownership, or production readiness for new network capabilities