Senior Network Engineer

About the role

Waabi is a leader in Physical AI, building autonomous trucks and robotaxis. The Senior Network Engineer will own the design, deployment and lifecycle management of Waabi’s multi‑site network across its offices.

Key responsibilities

• Design, deploy and manage switching, routing, wireless and firewall infrastructure for all locations.
• Plan ISP bandwidth and ensure redundant, appropriately sized throughput.
• Lead network incident response, on‑call coverage and create runbooks.
• Audit and harden network configurations, including loop protection, STP and MC‑LAG.
• Define hardware and firmware standards and replace ad‑hoc site configurations.
• Maintain IP addressing, VLAN architecture and segmentation for workstations, servers and guests.
• Evaluate and manage zero‑trust remote‑access tools such as Tailscale, Cloudflare and Zscaler.
• Support vehicle connectivity in partnership with product and fleet teams.
• Partner with engineering to provide reliable developer‑facing network paths and scale on‑prem compute clusters.
• Create and maintain network documentation, topology diagrams and disaster‑recovery runbooks.

Required profile

• Deep knowledge of the OSI model and enterprise networking.
• Hands‑on experience with switching, routing and wireless platforms.
• Experience operating firewalls, VPNs and WAN optimization in multi‑site environments.
• Familiarity with mesh/overlay VPN and zero‑trust networking tools.
• Proficiency with IP address management, VLAN design and Linux.
• Experience with infrastructure‑as‑code tools such as Ansible, Puppet, Chef or Terraform.
• Strong background in network monitoring, observability and incident‑response processes.
• Excellent communication skills and a collaborative mindset.

Required skills

• OSI model
• Enterprise switching
• Routing
• Wireless platforms
• Firewalls
• VPNs
• WAN optimization
• Mesh/overlay VPN
• Zero‑trust tools
• IPAM
• VLAN design
• Linux
• Ansible
• Puppet
• Chef
• Terraform
• Network monitoring
• Observability
• Incident‑response processes