Uber

Role: Software Engineer II (SE-2)

College: Not Specified

Interview Date: 2025-10-25

Interview Type: Full-Time

Result: Accepted

Difficulty: Not Specified

Rounds: 6 rounds (CodeSignal Test, Technical Screening, Coding 1 - DSA, Coding 2 - LLD, Design & Architecture - HLD, Collaboration & Leadership)

Topics Asked: Data Structures, Algorithms, Dynamic Programming, Low-Level Design, High-Level Design, Behavioral

Experience:

The candidate applied through a referral for the Uber Software Engineer II role.

Pre-Screen Round - CodeSignal Test: Two coding questions were presented, both solved completely, passing 100% of test cases.

Technical Screening: Focus on DSA. One coding question based on Dynamic Programming was solved successfully. The problem was: Given two strings, s and t, consisting only of lowercase English characters, determine the minimum number of times s must be appended to itself for t to be a subsequence of the resulting string. Example: s: boy, t: oyb -> ans: 2 ("boyboy").

Interview 1 — Software Engineering - Algorithms & Data Structures (Coding 1): Focus on DSA. Two questions were asked, with a strong emphasis on time and space complexity.
1st Question: LeetCode - Cheapest Flights Within K Stops.
2nd Question: LeetCode - Maximum Points You Can Obtain from Cards.

Interview 2 — Software Engineering - Depth in Specialization (Coding 2): Focus on Low-Level Design (LLD). The problem was to implement file system APIs: `mkdir`, `pwd`, `cd`. `mkdir` and `pwd` were easy. `cd` was difficult due to a wildcard `*` that could match '.', '..', or any child directory. The interviewer focused on a working solution.

Interview 3 — Design & Architecture - New Problem: Focus on High-Level Design (HLD). The task was to design a backend system for an e-commerce website that displays merchandise, specifically the browsing experience, excluding the purchase process. Popularity data should be used to highlight top items. The candidate had to prepare an event processor for events like 'Product added to Cart', 'Product viewed', etc. Questions included data storage and prioritizing consistency vs. availability. The candidate used Kafka for event ingestion, MongoDB for product catalog, and Redis for leaderboards/caching.

Interview 4 — Collaboration & Leadership: This round was scheduled but then cancelled.

The candidate received an offer.