Uber Software Engineer Interview Questions

I would split services by responsibility, keep contracts clear, and avoid introducing too much coupling between teams. Then I would think about retries, observability, and how services recover when dependencies are slow or unavailable. Good microservice design is about clarity and resilience, not just splitting code.

I would compare the options against correctness, maintainability, and delivery risk instead of treating it like a personal debate. Then I would try to align on the simplest solution that solves the actual problem. A strong answer shows collaboration, not just technical opinion.

I would first look at the real bottleneck, whether it is the data model, the search space, or the scoring step. Then I would reduce unnecessary work by pruning candidates early and reusing computed results when possible. The best optimization comes from understanding the current path cost.

I would make sure the system reacts to real supply and demand signals while staying stable and understandable. Then I would think about fairness, latency, and how to prevent overreaction to noisy data. A good answer shows that pricing is both a technical and product problem.

I would start by identifying whether the graph is weighted, directed, or unweighted, then choose the right traversal or shortest-path method. After that I would explain the time and space complexity clearly. Interviewers want to see that I can reason about structure before jumping into code.