About the Role
Were 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: youll architect, build, and operate the network foundation that our platform and product teams depend on, and youll 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 were looking for someone who thinks about networking at the level of principles and architecture rather than a single vendors console. The immediate priority is designing and deploying IPv6-native VPC architecture and bringing up IPv6 networking for our EKS workloads. Beyond that, youll 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 youll 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 elses design.
Why This Role Matters
This is a rare chance to define a discipline, not just maintain one. Youll take over an existing network thats 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.
Youll 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, youll architect how we connect across clouds before the complexity calcifies, while its still a design problem rather than a cleanup job.
Youll have real ownership and real reach. As the orgs first and most senior networking engineer, you set the direction, you establish the standards, and youre the person the rest of engineering looks to on networking. Your work wont sit in a corner - its the foundation everyone else builds on, and youll 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 - youve 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)
Network security and compliance experience
AWS certifications (Advanced Networking - Specialty or similar)
Compensation
We benchmark compensation using trusted market data and apply a tiered geographic framework to ensure competitive pay across locations. The ranges below represent the base salary band for this role by tier. Final offers are determined by experience, scope, internal parity, and location.
We consider several factors when determining compensation, including location, experience, and other job-related factors.
At Scribe, we celebrate our differences and are committed to creating a workplace where all employees feel supported and empowered to do their best work. We believe this benefits not only our employees but our product, customers, and community as well. Scribe is proud to be an Equal Opportunity Employer.