← Back to Directory

serve robotics

Small

Serve Robotics is a company that develops autonomous, AI-powered sidewalk delivery robots designed to transport food and goods over short distances. Originally spun off from Uber's Postmates, it operates in the last-mile delivery space and is known for partnering with services like Uber Eats to deploy its robots in urban markets.

3 interview notes · updated Jul 2026

serve robotics·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Serve Robotics for a software engineering role. The whole thing revolved around one big ambiguous prompt and how you break it down. Felt more like a product-meets-infrastructure exercise than a pure coding interview.
  • A team asks you to build a 'robot heat map.' How do you figure out what they actually need, and what do you build?
  • For each use case you identified, what metrics would you emit and what tags or dimensions would you attach to each data point?
  • What storage solution would you choose for geospatial data at this scale, and what are the trade-offs between options like Redis, Cassandra, PostGIS, and Elasticsearch?

“The prompt is intentionally vague and I think that's the whole point.”

View Post

serve robotics·Software Engineer·Technical Phone Screen

May 2026
Serve Robotics coding round focused entirely on concurrency. One meaty design problem that took up the whole session, and they really wanted to see you think through thread safety rather than just produce working code.
  • Design and implement a thread-safe cache with add(key, value, ttl) support and a background scheduler that evicts expired entries every 5 seconds. The design must handle concurrent adds and evictions safely, and you should provide test cases.

“This one took me a while to get my footing.”

View Post

serve robotics·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Serve Robotics for a software engineering role. It was a conversation with a PM, which I wasn't fully expecting, so some of the questions felt more product-flavored than pure engineering.
  • Walk me through a past project you led. What was your role and how did it go?
  • Tell me about a time you pushed back on a feature request from a PM or stakeholder. How did you justify it, what reasoning or data did you use, and what happened?

“Pretty standard opener but I fumbled the structure a bit.”

View Post