Skip to content

Dyna Robotics

Senior Software Engineer, Fleet Connectivity

Location
Redwood City, CA, US
Arrangement
On-site
Employment type
Full-time
Level
Senior
Posted
23 September 2026 (7 days ago)

Checked 6 days agoApplications go to the employer, never to RoleSprint

About this role

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.

THE ROLE

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.

WHAT YOU'LL DO

- 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.

- 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.

- 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.

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

- Diagnose field issues on networks you don't control, then build the fix so the same failure never happens twice.

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

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

- 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

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

- 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)

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

- Comfort working in the field and communicating clearly under pressure: you'll be translating failures into fixes mid-demo and mid-deployment

- Degree in CS, EE, or a related field, or equivalent practical experience

STRONGLY PREFERRED

- 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

- Experience managing connectivity for a fleet of edge devices (robots, vehicles, IoT) deployed on networks you don't own

- Hands-on work with cellular/LTE/5G failover hardware, link bonding, or multipath networking

BONUS POINTS FOR

- Experience with pub/sub or messaging middleware (ZeroMQ, ROS 2, DDS, or similar), especially running it over WiFi or WAN links

- Experience with network hardware: managed switches, access points, mesh networking, cellular routers

- Experience supporting live events, demos, or on-site customer deployments where network reliability was your responsibility

At Dyna Robotics, we build technology for the real world, which requires a team as diverse as the environments our robots inhabit. We are an equal opportunity employer committed to technical rigor and mutual respect.

Don’t let a checklist stop you. Data shows that underrepresented groups often only apply if they meet 100% of the criteria. We value problem-solving and grit over keyword matching. If you’re passionate about robotics, no matter your discipline, we want to hear from you, even if you don't check every box.

Work location

  • Redwood City, CA, US

Related jobs

Ready to make a decision?

This role is either worth your time or it isn’t.

Analyze the posting against your experience, see the gaps clearly, and build the right materials only if the opportunity makes sense.

Nothing is submitted automatically. You choose what happens next.

About this listing

Published on Ashby under the board identifier Dyna Robotics, which is the name the employer’s own job board carries. RoleSprint has not verified the company’s registered or trading name, so it is shown exactly as published rather than tidied up.

RoleSprint is not the employer and not a recruiter. Applications are made on the employer’s own site and never reach us; what RoleSprint does is help you decide whether a role is worth your time and prepare for it if it is.

Published 23 September 2026, last checked 6 days ago. A posting stops being advertised here 90 days after the employer published it, and one the employer takes down is marked closed rather than quietly removed.

More searches like this one

Browse all current openings

No credit card requiredStart free