Staff Cloud Networking Engineer

About the Role

We're hiring a Staff Cloud Networking Engineer to own cloud networking across our engineering organization. This is a hands-on, high-autonomy role with broad scope: you'll architect, build, and operate the network foundation that our platform and product teams depend on, and you'll set the technical direction for how we do cloud networking as we scale.

Our footprint today is on AWS, so deep AWS expertise is essential — but we expect to span multiple providers over time, and we're looking for someone who thinks about networking at the level of principles and architecture rather than a single vendor's console. The immediate priority is designing and deploying IPv6-native VPC architecture and bringing up IPv6 networking for our EKS workloads. Beyond that, you'll define the long-term strategy for how we address, connect, and scale our network — including how we connect across cloud providers as our footprint expands.

This is the first dedicated networking role in the organization. Our DevOps engineers have carried networking alongside their other responsibilities, and you'll be the first person to own it as a specialty — establishing the standards other teams build against, becoming the authority on cloud networking decisions, and raising the networking competency of the engineers around you. This role is for someone who wants both depth — the hard networking problems — and the ownership to build the function from the ground up rather than execute someone else's design.

Why This Role Matters

• This is a rare chance to define a discipline, not just maintain one. You'll take over an existing network that's served us so far, and your mandate is to design its successor — a deliberate, modern architecture to replace what grew organically. You get the context of a real running system and the freedom to decide what comes next, and the architecture you build will shape how every team here ships for years.

• You'll start with genuinely interesting problems, not maintenance. IPv6 from the ground up, IPv6-native EKS, IPAM stood up clean — these are the kinds of greenfield challenges most network engineers rarely get to do once, let alone all at once. And as we grow into multiple providers, you'll architect how we connect across clouds before the complexity calcifies, while it's still a design problem rather than a cleanup job.

• You'll have real ownership and real reach. As the org's first and most senior networking engineer, you set the direction, you establish the standards, and you're the person the rest of engineering looks to on networking. Your work won't sit in a corner — it's the foundation everyone else builds on, and you'll level up the engineers around you as you go.

If you want depth on the hard networking problems and the autonomy to build a function the right way from day one, this is that role.

What Makes You a Great Fit

• Deep, hands-on AWS networking expertise — you've designed and operated AWS networking in production at scale and can serve as the authority on it

• Strong, vendor-agnostic networking fundamentals: IP addressing and subnetting (IPv4 and IPv6), routing, DNS, TCP/IP, BGP, and NAT — the kind of foundation that transfers cleanly to any cloud provider

• A demonstrated history of setting technical direction across an organization — influencing without authority, establishing standards, and leveling up the teams around you

• Comfort being the first specialist in a domain: defining the practice, making the foundational decisions, and bringing others along rather than inheriting an established playbook

• Demonstrated experience with IPv6 in a cloud or large network environment — not just familiarity, but having actually deployed and troubleshot it

• Production experience with core cloud networking primitives — VPCs, transit/peering, IPAM, and private connectivity — on AWS, and ideally on at least one other provider

• Experience with private DNS in Route 53; familiarity with public DNS management (Cloudflare or similar) a plus

• Kubernetes networking experience, ideally with EKS, including CNI behavior and how addressing works at the pod, service, and ingress levels

• Infrastructure-as-code proficiency (Terraform or equivalent) and comfort working in a code-reviewed, GitOps-style workflow

• Ability to operate independently, drive architectural decisions, and communicate tradeoffs clearly to both engineers and senior stakeholders

How to Stand Out

• Hands-on networking experience with multi-cloud connectivity tooling

• Experience with multi-account/multi-project cloud environments (AWS Organizations, Control Tower, landing zones, or equivalents)

• Ne