[Hiring] Senior Network Engineer @StackYak

Role Description

We need someone who understands networks from Linux host to data-center fabric to carrier connectivity to cloud, and can automate the whole path.

• A customer's traffic has to reach a GPU workload, securely and reliably, over a path that no single party controls.
• This job is about making multiple paths work efficiently and provisioning them with minimal customer effort.
• This is not a traditional network-operations role; we need a network engineer who codes, debugs systems end to end, participates in architecture, and owns production outcomes.

What You Will Own

• The whole path from a customer to their workload.
• Routing and segmentation.
• BGP, VLANs, VRFs, firewalling, and policy.
• Tenant isolation and defining "isolated" precisely.
• Secure private access using WireGuard, IPsec, and overlays.
• The fabric inside our facilities and its interaction with external fabrics.
• Carrier and cloud connectivity.
• Network observability and incidents.
• The layer-boundary call.
• Turning networking into a product.
• Working alongside infrastructure and inference engineers.

What We Need

• Run BGP in production.
• Designed and operated VLANs, VRFs, segmentation, and firewall policy.
• Troubleshot Linux networking on hosts carrying real traffic.
• Worked inside a data-center network.
• Operated cloud networking in at least one major cloud.
• Built connectivity on IPsec and/or WireGuard.
• Kept tenants apart and been accountable for that claim.
• Chased packet flow across administrative domains.
• Replaced manually managed device configuration with automation.
• Written Python and Terraform for production use.
• Reasoned about networking decisions impacting distributed systems.

You Will Be Especially Strong If

• You have worked at a hyperscaler, neocloud, hosting provider, or enterprise networking vendor.
• You have designed or operated networks for high-bandwidth distributed workloads.
• You understand RDMA and network requirements for multi-node GPU workloads.
• You have experience with carrier connectivity and NaaS platforms.
• You have built network automation.
• You can turn connectivity patterns into repeatable processes.
• You are comfortable debugging from application symptoms to physical paths.
• You run labs or experiment with networking outside of work.

This Is Probably Not For You If

• You primarily configure network devices through tickets.
• You do not code.
• You think the network ends at the top-of-rack switch.
• You think cloud networking makes physical networking irrelevant.
• You prefer architecture diagrams to implementation.
• You want every customer connection to be bespoke.
• You have strong certification knowledge but limited experience.
• You need networking to be your exclusive domain.

What Success Looks Like

You can take a requirement like:

A customer needs secure, private, reliable access from their environment to a workload running on GPUs in one of our facilities.

…and design and implement the path from customer edge to workload — routing, isolation, security, observability, automation, failure handling — and then make the second customer's version of it take a fraction of the effort.

How We Work

• Small, senior team with direct access to the founders.
• Strong opinions, loosely held.
• Everyone participates in technical decisions.
• Shared responsibility for production and on-call.
• Value on what you have built and operated over degrees or certifications.
• Expect people to leave ego at the door and execute decisions.
• Remote and distributed across time zones.
• Hiring involves real conversations with potential colleagues.
• This is an early-stage startup with high pace and evolving scope.

Compensation

Competitive compensation plus meaningful equity. Exact structure will depend on location, engagement model, and experience.

A Note For Agencies

We are not using external recruiters or agencies for this role, and we will not be persuaded otherwise by an email. We do not want your spam.