Uber’s behavioral round tests fit against its eight cultural norms, such as ownership, grit and customer obsession, rather than a scripted HR chat. Common Uber behavioral interview questions map straight to those norms: a problem you owned that nobody assigned to you, a setback or long grinding problem you pushed through, and a time you disagreed with someone more senior and your idea won out.
In the Uber interview process, US new grads get one behavioral interview in a final loop of three, and experienced hires get a Collaboration & Leadership round with the hiring manager, sometimes plus a Bar Raiser. A 2025 US intern on Taro said the round opened with tell me about yourself and then went deep into the resume. Round-by-round reports are on the Uber interview experience page.
Uber’s eight cultural norms
Uber replaced its earlier “always be hustlin’” era values after a 2017 culture reset. The current norms, still used to frame hiring and performance conversations, are: we build globally, we live locally; we are customer obsessed; we celebrate differences; we act like owners; we persevere; we believe in the power of grit; we value ideas over hierarchy; and we make big bold bets. Expect at least one or two behavioral questions to map directly onto these rather than being generic “tell me about a challenge” prompts.
How to use the eight norms in your answers
You do not need to quote norm slogans in every sentence. Name the norm once when it fits (“that was me acting like an owner”), then spend the rest of the time on facts, trade-offs, and metrics. Uber’s Collaboration & Leadership round (often 45–75 minutes with the hiring manager) reportedly pushes for numbers and individual actions, not “we tried hard.” Prepare at least one story each for ownership, grit, customer/rider impact, speaking up to senior people, and integrity when expedient options existed.
Common Uber HR questions
1. Tell me about yourself
Framework: Present → Past → Future (60–90 seconds). Land on why Uber and the level you are interviewing for.
Sample answer: “I’m a CS grad who interned on a logistics dashboard - my main win was reducing manual dispatch checks by building a map view with live driver status. I like marketplace problems where software meets the physical world. I’m interviewing for Uber because matching, ETA, and pricing are the kind of messy, high-impact systems I want to learn on, and I’d relocate to New York or Seattle for a Software Engineer I role.”
2. Why Uber?
Sample answer: “Uber is a real-time marketplace, not a static content app - drivers move, demand spikes, and the system has to stay fair and fast. I’m specifically interested in dispatch and location data (how you index moving supply and rank by time-to-pickup, not straight-line distance). Culturally, I respect that Uber reset its norms in 2017 toward safety and accountability; I want to work somewhere behavioral standards are explicit.”
3. Tell me about a time you owned a problem nobody assigned to you (we act like owners)
Sample STAR: “Situation: Our campus ride-share prototype had duplicate bookings when two users tapped confirm at once. Task: No ticket existed; QA was informal. Action: I added idempotent booking IDs, a short DB transaction, and a one-page runbook for club operators. Result: Duplicate rides dropped to zero in two weeks of testing; the club adopted it for three events without me being on the org chart.”
4. Tell me about a time you pushed through a setback or a long, grinding problem (we persevere)
Sample STAR: “Situation: A graph routing bug in my project only appeared on large city datasets - intermittent for weeks. Task: I owned the backend path. Action: I logged inputs, reproduced with a 500-node fixture, bisected commits, and found an off-by-one in edge relaxation. I added regression tests and a visual diff tool for routes. Result: p95 route compute fell from ~800 ms to ~120 ms on the test set; the grind was boring debugging, not one insight.”
5. Describe a time you disagreed with someone more senior and your idea won out (we value ideas over hierarchy)
Sample STAR: “Situation: A senior dev wanted to block the release until we rewrote the whole auth module. Task: We had a fixed demo for partners. Action: I prepared a one-page risk table: what we could ship with token refresh vs full rewrite, with rollback steps. I proposed shipping scoped API keys for the demo only. Result: Leadership picked the scoped path; partners signed; we scheduled the rewrite next quarter with tests - the disagreement was data, not volume.”
6. Tell me about a time you changed something because of user feedback or user impact (we are customer obsessed)
Sample STAR: “Situation: Cafeteria staff said students couldn’t tell if pre-orders were ready. Task: Improve clarity without a new app store release. Action: I added SMS when status = ready and a large-screen queue view from the same backend field. Result: Average wait confusion complaints dropped (staff estimate ~40% over two weeks); order throughput at peak lunch improved because the line moved.”
7. Tell me about a time you took a real risk on a project (we make big bold bets)
Sample STAR: “Situation: We could ship a rules-based recommender in a week or wait a month for ML. Task: Choose for a hackathon with judges who cared about novelty. Action: I bet on a simple ML baseline with a frozen training set and a manual fallback if inference failed live. Result: Demo worked; we placed top three. If it had failed, we’d have flipped to rules-only - the risk was bounded and reversible.”
8. Tell me about working with a very different team or background (we celebrate differences)
Sample STAR: “Situation: I built APIs; designers and ops students owned UX and vendor calls. Task: Ship a lost-and-found portal in three weeks. Action: Daily 15-minute standups, shared Figma comments, and I translated ops jargon into API fields on a living doc. Result: Launch on time; ops reported faster handoffs because they could trace status in the same tool they already used.”
9. Strengths and weaknesses
Strength sample: “Customer impact awareness - I ask who suffers if this breaks (rider, driver, eater) before I optimize code elegance.”
Weakness sample: “I sometimes under-communicate progress when heads-down. I now send end-of-day three-line updates in team channels; my last internship lead said it fixed visibility issues.”
10. Are you willing to relocate / what’s your notice period?
Sample: “Yes - I can work from New York, San Francisco or Seattle, and I’m fine with in-office days Tuesday through Thursday. I can start after graduation on [date] / after two weeks’ notice to my current employer. I’m on F-1 OPT, so I’d like to confirm sponsorship before the final loop.”
11. What do you know about Uber?
Sample answer: “Beyond the rider app: Uber runs a global marketplace with real-time location, matching, ETA, and surge as core engineering problems - often using geospatial indexing (public talks mention H3-style cells). After 2017, leadership replaced founder-era values with eight cultural norms (ownership, customer obsession, ideas over hierarchy, do the right thing, etc.). Publicly, Uber continues to invest in safety, compliance, and multi-product growth (Rides, Eats, Freight). The Graduate 2026 Software Engineer I posting lists a $150,000-$158,000 base in the US - I’d confirm the rest on the offer.”
12. Tell me about a time you did the right thing when something easier was available (we do the right thing)
Sample STAR: “Situation: A teammate suggested logging real phone numbers in plain text for debugging a delivery tracker. Task: I was junior but uncomfortable. Action: I raised it in standup, proposed hashed IDs and structured logs with retention limits, and offered to implement masking that day. Result: Team agreed; we avoided a privacy incident and kept enough logs to debug. The expedient path wasn’t worth the risk.”
13. Tell me about a time you used data to change a team’s direction
Sample STAR: “Situation: We assumed users wanted more filters on a campus marketplace. Task: Validate before building. Action: I pulled two weeks of click logs, ran a five-user hallway test, and showed 80% of purchases used search, not filters. Result: We shipped search improvements first; conversion on mobile rose ~12% in our A/B slice.”
14. Do you have any questions for us?
Strong questions: How does this team live ideas over hierarchy day to day? What does success at six months look like for a Software Engineer I here? How is on-call shared, and what’s the stack for dispatch-adjacent services on your squad?
Avoid leading with compensation or WFH unless the recruiter invited it.
Real examples to prepare before Uber’s HR round
| Story type | Prompt | Maps to |
|---|---|---|
| Ownership | Fixed or improved something without being asked | We act like owners |
| Grit | Pushed through a long, difficult bug or deadline | We persevere / power of grit |
| Bold bet | Took a real risk on a project’s direction | We make big bold bets |
| Speaking up | Disagreed with someone more senior and were right | We value ideas over hierarchy |
| User impact | Changed something because of user feedback or data | We are customer obsessed |
| Collaboration | Worked well with a very different team or background | We celebrate differences |
Answers that hurt in Uber’s behavioral round
- Answering “why Uber” with only the consumer app, no engineering or scale angle
- Badmouthing gig workers, drivers, colleges, or other companies
- Stories told only with “we”, when the hiring manager round pushes for numbers and your own actions
- Naming a cultural norm with no story behind it, or a “disagreed with a senior” story where you simply gave in
Uber India: SE I behavioral round
India campus loops fold behavioral questions into a 30-45 minute hiring manager or HR round after two technical rounds. Entry-level hiring is mostly for Software Engineer I in Bengaluru, so expect a direct relocation question (“I’m targeting Bengaluru for SE I and can join after 30 days’ notice” is a fine answer), and keep the same norm-mapped stories. Community reports put India SE I total compensation around ₹20-36 LPA.