🚀 Uber L4 (SDE-2 - Backend) Interview Experience (OFFER Received)
- Posted
- 28 Mar 2026
Summary
I completed Uber's L4 Backend interview process, solved all coding rounds, designed a circuit breaker and a stock price tracking system, and received an offer.
How it went
Hey, hope everyone is doing good. Recently finished my loop with Uber L4 and got an offer. Here are the rounds and what I got asked.
- Coding test - Hackerrank. 2 Medium-Hard questions. Was able to solve both. [PASS]
- BPS (Screening Round) - 2 DSA questions, a basic DFS evolving to Dijakstra and DFS+Binary Search. Was able to solve both in under 30 mins. Discussed some projects. [Strong Hire]
- Coding Round 1 (DSA) - 3 DSA questions. Starts from a 2D count number of islands, moved to 3D version of the same, finally moves to implementation of a 2D DSU. Was able to solve all questions, talk about Ackerman function.[Strong Hire ++]
- Coding Round 2 (LLD/Machine Coding) - Design a Circuit Breaker. The question slighly threw me off because the requirements looked like a rate limiter combined with a circuit breaker. The breaker opened when the number of requests (NOT number of errors) exceeded a threshold. Was able to solve it, come up with test cases, show OPEN, CLOSED, HALF_OPEN states and answer concurrency questions properly. [Strong Hire/Hire]
- Hiring Manager Round - Nothing unusual here. Regular "tell me about a time questions". I usually go deep into explaining the scenario and I was surprised the manager wanted me to go even into more details in some cases. Probably tired of hearing made-up stories from candidates. [PASS]
- System Design (HLD/Bar Raiser) - Design a price tracking systems for stock tickers. The requirement was to allow users to subscribe to stocks and notify them when stock price movement exceeded a DELTA value. This was a completely new problem for me and it was kinda a combination of Top-K (with sliding windows) and CamelCamelCamel. [MEETS BAR]
Key takeaways
- For HLD problems, interviewers won't necessarily let you build the basic system first before asking you to do deep dives. In essence, the Hello Interview pattern could backfire and you need to be ready in that case. I wasn't completely comfortable.
- Have some stories prepared for HM round. And real ones are better. For me the Amazon LPs prep worked good. Make sure to add anecdotes here and there to reinforce your story once in a while.
Happy to answer in any questions in the comments. Best of luck to everyone preparing for their interviews.
Questions asked (5)
- 01
Count Number of Islands (2D)
Data Structures & Algorithms · Medium
Given a 2D grid of
'0'(water) and'1'(land), count the number of distinct islands. An island is a group of horizontally or vertically adjacent'1'cells. - 02
Count Number of Islands (3D)
Data Structures & Algorithms · Hard
Extend the classic island‑counting problem to a 3‑dimensional grid. Each cell can be
'0'or'1'. An island consists of'1'cells that are adjacent along any of the three axes. - 03
2D Disjoint Set Union (DSU) Implementation
Data Structures & Algorithms · Medium
Implement a Disjoint Set Union (Union‑Find) data structure that works on a 2‑dimensional grid, supporting
union(x1, y1, x2, y2)andfind(x, y)operations efficiently. - 04
Design a Circuit Breaker
System Design · Medium
Design a circuit‑breaker component. The breaker opens when the number of requests (not errors) exceeds a configurable threshold. It must expose three states (OPEN, CLOSED, HALF‑OPEN), allow defining test cases, and handle concurrency correctly.
- 05
Design a Price‑Tracking System for Stock Tickers
System Design · Hard
Build a high‑level design for a service where users can subscribe to stock tickers and receive notifications when the price movement exceeds a user‑defined delta. The solution should handle real‑time price streams, support top‑K queries over sliding windows, and be similar in spirit to the CamelCamelCamel price‑tracking approach.