Uber SWE Interview: Coding Screen Guide
Updated:
Estimated read time: 8-10 minutes
Summary: The Uber software engineer (SWE) coding screen is a common early technical stage. Expect algorithmic coding, complexity analysis, tests, and follow-up constraints, with team-specific variations for mobile and infrastructure roles.
See the full Uber Software Engineering interview roadmap, including coding screens, loop coding, system design, behavioral or hiring manager interviews, and team/headcount approval. View the Uber Software Engineering interview roadmap
TL;DR + FAQ (read this first)
At-a-glance takeaways
- Expect an early engineer-led coding screen where used.
- Plan for algorithmic coding, complexity analysis, tests, and follow-up constraints.
- Role context can affect the screen, especially for mobile and infrastructure paths.
- Strong candidates clarify constraints, code cleanly, test edge cases, and respond to hints.
Quick FAQ
How long is the screen?
Often 45-60 minutes, but confirm timing with your recruiter.
What should I practice first?
Arrays, strings, graphs, shortest path, hash maps, intervals, heaps, and dynamic programming.
Should I expect an Uber-domain problem?
Do not assume that. Use Uber-like data to practice constraints, not to memorize tasks.
At a glance
- Stage: Screen.
- Round: Coding screen.
- Typical duration: often 45-60 minutes; confirm with your recruiter.
- Likely interviewer: engineer.
- Relevant levels: intern through staff-plus, possible or role-dependent.
What happens in this round
The screen usually asks you to solve an algorithmic problem in a shared editor. Prepare for arrays, strings, graph traversal, shortest path, dynamic programming, hash maps, frequency counting, complexity, and edge cases.
For Uber, domain-adjacent thinking can help: routes, marketplaces, dispatch, locations, scheduling, events, and mobile state. Still, do not assume the screen will be a domain problem.
Level-specific expectations
Intern and new grad candidates should focus on fundamentals and speed.
Junior and mid-level candidates should show correct implementation, tests, and complexity.
Senior candidates should add clarity, adaptation, and tradeoff reasoning under follow-ups.
Candidate-facing questions to prepare
- Given a stream of trip events, group by rider or driver and return the highest-frequency pattern.
- Find the shortest path in a graph when some edges become temporarily unavailable.
- Solve a dynamic programming problem involving routes, costs, or scheduling constraints.
- Use a hash map to deduplicate events and detect conflicting records.
- Write a sliding-window solution for a time-bounded marketplace signal.
- Explain time and space complexity, then optimize one bottleneck.
- Test empty input, duplicated records, disconnected graphs, and large inputs.
Use a mock interview to practice Uber-style coding screens with edge cases and constraints.
Strong signals
- Clear plan before code.
- Correct implementation with tests.
- Complexity analysis and adaptation.
- Good handling of graph, interval, and hash-map problems.
- Steady communication when hints appear.
Common failure modes
Rushing implementation. Clarify constraints first.
Weak testing. Edge cases are a recurring risk.
Not responding to hints. Follow-ups can matter as much as the first solution.
Practice one coding task with a follow-up that changes scale, graph structure, or timing constraints.
How to prepare
- Review arrays, strings, graphs, shortest path, hash maps, intervals, heaps, and dynamic programming.
- Practice test cases before finalizing.
- Prepare for shared-editor communication.
- For mobile roles, confirm if platform-specific coding appears.
- For senior roles, practice optimization and tradeoff follow-ups.
Continue through the full Uber SWE roadmap to see how coding screens connect to loop coding, system design, behavioral, and approval stages. View the Uber Software Engineering interview roadmap