Uber | SDE 2 | Backend Engineer | June 2026 | Reject

Uber SDE II Backend Interview Experience

Experience: 3 years 3 months

Current Role: Software Engineer at a FAANG company in India

Education: B.Tech, CS, Tier 1, India

Current Compensation: ₹33 LPA

I recently interviewed for an SDE II Backend Engineering role at Uber. Below is the complete process and the questions asked.

Application

I applied directly through the Uber career portal without a referral. After around 5 days, I received an email from a recruiter to schedule the initial recruiter call. I scheduled the call for the following week.

Round 1 — Recruiter Screening

The recruiter screening was primarily an alignment and fitment discussion. Topics discussed included my current role and experience, reasons for switching, projects, backend vs frontend experience, technologies used, and overall technical background.

Result: Cleared

Based on the discussion, the recruiter scheduled the Business Phone Screen, the first elimination round, about 3 weeks later.

Round 2 — Business Phone Screen — DSA

Duration: 60 minutes. The round focused on Data Structures & Algorithms.

Question

First Unique Number – similar to a LeetCode problem. I solved it using the optimal approach.

Result: Hire

Round 3 — DSA

Question

Design Hit Counter – similar to a LeetCode problem. The version I received had three methods: put(element), getCount(element), and getTotalCount() (total count across all elements).

Result: Hire

Round 4 — HLD

Question

Design a chat application similar to ChatGPT. The application needed to support starting a new chat, continuing a previous chat, and other similar requirements.

I had prepared for HLD using Hello Interview, but got stuck at a few places and made several mistakes, which led to a poor performance.

Result: No Hire

Round 5 — DSA

Question

My Calendar I – similar to a LeetCode problem.

Result: No Hire

Round 6 — Behavioral

The behavioral round focused on previous work experiences and situational questions such as conflict resolution, challenging projects, receiving critical feedback, and writing suboptimal code under time constraints.

Result: Hire

Final Outcome

Rejected