Nuro·Backend Engineer·Onsite - System Design / Architecture
May 2026
Two back-to-back system design rounds at Nuro for a backend role, both pretty heavy on distributed systems fundamentals. One was a webhook delivery platform, the other a vehicle telemetry aggregation system. Left feeling like I did okay but probably undersold some of the tradeoffs.
- How would you design a multi-tenant webhook delivery platform?
- How would you design a telemetry ingestion and aggregation system for a fleet of connected vehicles sending measurements every few seconds?
- Why is exactly-once webhook delivery basically impossible in practice?
- If one customer's endpoint is consistently failing or slow, how do you prevent it from affecting the rest of the system?
- How do you handle out-of-order telemetry events in a vehicle metrics pipeline?
- What storage would you use for serving recent dashboard data versus storing raw historical telemetry long-term?
- If you change your aggregation logic, how do you replay historical telemetry to backfill the new results?
“This one took me a minute to scope properly.”