About the role
You give people secure, observable access to computers they own or are authorised to use, wherever those machines are. Much of this happens across home networks, which are hostile in ways data-centre networking is not: NAT, flaky links, and no operator.
The work
Build authenticated device discovery, encrypted connections, NAT traversal and network-aware scheduling. Measure bandwidth, latency, data movement and disconnections. Separate remote task dispatch from tightly coupled distributed training, and enforce limits on data leaving the user's device.
What good looks like
In your first 90 days, deliver a two-site execution prototype with revocation, transfer accounting and clear behavior during network loss.
Evidence we look for
Bring networking and distributed systems experience, including protocol debugging and practical understanding of home-network constraints. RDMA or high-performance cluster networking is valuable for specialized workloads.
What we need to see
- Networking and distributed-systems experience, including protocol debugging at the packet level
- Practical understanding of home-network constraints, not just data-centre assumptions
- You can make a connection observable enough to diagnose without making it a surveillance channel
- Security instincts about anything that crosses a network boundary
Nice to have
- RDMA or high-performance cluster networking for the specialised workloads
- NAT traversal, QUIC, or WireGuard-style tunnelling
- You have shipped something that had to work on consumer routers
The exercise
Compare placing computation beside the data with moving the data across a slow uplink, using explicit assumptions.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.