Dyna Robotics builds general-purpose robots powered by a proprietary embodied AI foundation model with top-in-industry generalization and real-world performance. Already deployed with customers across multiple industries, our robots do commercial-grade work in the physical world. Our team comes from Google DeepMind, Meta, and Cruise, and we're backed by CRV, First Round, and other leading investors.

As a Senior Software Engineer, Fleet Connectivity, you’ll own 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. 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 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.

This is a full-time, on-site position in Redwood City.

What You’ll Do

Teleoperation Network Performance: Own network performance for remote teleoperation. Measure and minimize end-to-end latency and jitter, tune how video and control streams are transported and prioritized, and make sure sessions degrade gracefully (lower bitrate, prioritized control traffic, safe fallback behavior) instead of failing when the link gets worse. A reliable, low-latency link is what keeps a human safely in the loop.

Fleet Connectivity: Build the fleet connectivity stack. Monitoring, diagnostics, and automated failover software that keeps every robot’s connection healthy in production, turning a dropped connection into an automatic root cause and recovery, not a 2am page to go run tcpdump on-site.

Site Bring-Up: Own the network side of site bring-up. Build tooling that assesses a customer’s network before a robot ever arrives, then work with the deployment team to configure the right failover, QoS, and VPN setup for that site.

Real-World Connectivity Design: Design connectivity for real-world chaos: warehouse WiFi dead zones, cellular failover, and VPN-gated corporate networks with firewall rules you can’t change.

Field Diagnostics: Diagnose field issues on networks you don’t control, then build the fix so the same failure never happens twice.

Office & Demo Network: Make the office and demo network rock-solid by default, so a live demo never drops in front of a customer or investor.

Engineering & Research Partnership: Partner with engineers and researchers to keep the network ahead of what they need for training-data upload and live model debugging.

Incident Ownership: Be the person in the room when connectivity is on the line, whether that’s a live demo or a field incident.

What You’ll Bring

Network Debugging: Hands-on experience debugging real-world networks: WiFi/RF troubleshooting and packet-level diagnostics (Wireshark, tcpdump, iperf).

Protocols & Linux Networking: Deep understanding of TCP, UDP, and how they behave on lossy, high-jitter links, plus strong Linux networking skills (routing, traffic shaping with tc, firewalling, VPNs such as WireGuard).

Production Software: A track record of shipping production-quality software in C++, Rust, or Python, not just scripts and prototypes.

Field Work & Communication: Comfort working in the field and communicating clearly under pressure: you’ll be translating failures into fixes mid-demo and mid-deployment.

Education: Degree in CS, EE, or a related field, or equivalent practical experience.

Strongly Preferred

Real-Time Media & Transport: Experience with real-time media or low-latency transport: WebRTC, RTP, adaptive bitrate, congestion control, jitter buffers, or UDP-based protocols like QUIC or SRT.