Dyna’s robots only create value when they’re reliably connected. Robotics isn’t like typical enterprise software: latency that an ordinary business app would shrug off turns teleoperation and remote supervision into jerky, unsafe, or outright failed robot behavior. A degraded link here isn’t a background IT ticket: it can be the difference between a robot finishing a task and stalling mid-motion. This role owns the technical side of network performance in two settings: making sure a demo never drops mid-pitch, and making sure a deployed robot stays online, monitorable, and controllable on network infrastructure Dyna doesn’t own or control. This is a build role, not a network-admin or support role: you’ll design and build the systems (monitoring, automated failover, self-healing diagnostics) that make connectivity reliable by default, so stability is a property of the system rather than something a person has to catch and fix after it breaks.