Telnyx - Software Engineer (Python) — Programmable Networking

• Languages: Python (asyncio: aiohttp, uvloop, SQLAlchemy, Alembic, aiopg), Go (Envoy control plane), Jinja2, Bash • Languages: • Data: PostgreSQL (schema design, migrations, advisory locking, as a job queue), RabbitMQ • Data: • Network OS / routing: VyOS, FRR, Linux networking (VRFs, netfilter/NAT, netplan, GRE, WireGuard), BGP (VRFs, route reflectors, communities/labels, anycast), Unbound • Network OS / routing: • Automation: Ansible / ansible-runner, netmiko, asyncssh, NetBox-style IPAM (pynetbox, netaddr) • Automation: • Proxy / data plane: Envoy, xDS (ADS, go-control-plane) • Proxy / data plane: • Vendor & cloud: Equinix Fabric, Equinix Metal, AWS / Azure / GCP interconnect regions • Vendor & cloud: • Platform: Docker/OCI, GitHub Actions, HashiCorp Vault, OpenAPI 3 + Redocly, pytest (unit → e2e), mypy/ruff/black • Platform: • Architecture: clean/hexagonal (usecases, repository interfaces, adapters) — the service is structured, not a script pile • Architecture: • 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. • 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. • Envoy/xDS control-plane work (go-control-plane, ADS snapshots). • Cloud interconnect products — AWS Direct Connect, Azure ExpressRoute, GCP Partner Interconnect, or Equinix Fabric/Metal provisioning APIs. • IPAM internals (NetBox or equivalent), address-plan and route-distinguisher design. • Linux → VyOS (or equivalent NOS) migration experience on live customer traffic. • Mobile core exposure — routing toward PGW/PCEF/EPC, GRE toward packet gateways. • OpenAPI spec authorship and public developer documentation. • Operating multi-site PoP fleets (bare metal + Equinix-hosted). • What this role is not • Not a NetOps/NOC role. The deliverable is software — APIs, control planes, automation — not manual device changes. • Not a NetOps/NOC role. • 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. • Not a pure backend CRUD role.