The public API on api.telnyx.com — /networks, /virtual_cross_connects, /wireguard_interfaces, /wireguard_peers, /global_ips, /public_internet_gateways and their coverage/health/usage endpoints. Resource modeling, OpenAPI 3 specs (public and private), edge API-gateway routing, and backward compatibility for live customers
The orchestration control plane (Python 3.12, asyncio) — translating POST/DELETE into network deployments: resource allocation (IPAM, port/route-distinguisher/GRE-ID pools), Postgres-backed job queues (SKIP LOCKED), retries, rollback on partial failure, deploy/decommission runners, and long-running health-check and reconciliation daemons
The network automation layer — Ansible + asyncssh/netmiko pushing Jinja2-templated config to a fleet of Linux and VyOS nodes: WireGuard interface and peer lifecycle, FRR/VyOS BGP (VRFs, route reflectors, BGP labels), GRE tunnels, static NAT and firewall rules, Unbound DNS, anycast announce/withdraw driven by health checks, and config-drift detection
Cloud interconnect integrations — Equinix Fabric and Equinix Metal APIs to land virtual cross connects into AWS, Azure, and Google Cloud regions
Envoy-based data planes — a Go xDS control plane on envoyproxy/go-control-plane, pushing CDS/RDS/EDS over ADS to edge and gateway Envoy fleets
Production — Prometheus/Telegraf metrics and alerting, Bugsnag, customer escalations that span app logic and the network, and billing sync (MRC) for network resources
You've built and operated customer-facing REST APIs over real infrastructure — APIs where a POST ends in a router being configured, not just a row inserted — and you've lived with the async-job, rollback, and eventual-consistency problems that creates
Strong async Python in production, and comfortable writing and reviewing Go
Working routing knowledge: you can configure and debug BGP sessions, VRFs, GRE tunnels, NAT, and WireGuard, and read FRR or VyOS configs. Certification not required; hands-on ability is
Postgres beyond ORM basics — migrations on live systems, locking semantics, queue patterns
Fleet automation over SSH — Ansible at production scale, idempotent roles, safe rollout/rollback, drift detection
You've debugged incidents across layers in one sitting — tcpdump, wg show, vtysh, and application logs — ending in either a code fix or a config fix, and knowing which
Not a NetOps/NOC role. The deliverable is software — APIs, control planes, automation — not manual device changes
Not a pure backend CRUD role. If the network layer in the stack above reads as someone else's problem, this is the wrong fit