Uber HR Interview Questions
Overview
Section titled “Overview”Uber’s HR/behavioural round tests fit against its eight cultural norms - ownership, grit, and customer obsession - not a scripted generic HR chat.
Uber’s eight cultural norms
Section titled “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 behavioural questions to map directly onto these rather than being generic “tell me about a challenge” prompts.
Common Uber HR questions
Section titled “Common Uber HR questions”1. Tell me about yourself
Section titled “1. Tell me about yourself”Framework: Present → Past → Future (60-90 seconds). End with why you are interviewing for this Uber role today, not a full career recap.
2. Why Uber?
Section titled “2. Why Uber?”Sample direction: “Uber’s engineering problems - matching millions of riders and drivers in real time - are exactly the kind of scale and ambiguity I want to work on.” Add one concrete product, team, or engineering detail you actually know, not a generic compliment about the app.
3. Tell me about a time you owned a problem nobody assigned to you (we act like owners)
Section titled “3. Tell me about a time you owned a problem nobody assigned to you (we act like owners)”Framework: STAR, with emphasis on what made you step in without being asked, and what the actual outcome was. Uber wants evidence you’ll pick up gaps rather than wait for a ticket.
4. Tell me about a time you pushed through a setback or a long, grinding problem (we persevere / power of grit)
Section titled “4. Tell me about a time you pushed through a setback or a long, grinding problem (we persevere / power of grit)”Framework: Situation → what made it genuinely hard → what you kept trying → the result, even if it was partial. Avoid a story that resolves in one lucky attempt; Uber is checking for sustained effort, not a single flash of insight.
5. Describe a time you disagreed with someone more senior and your idea won out (we value ideas over hierarchy)
Section titled “5. Describe a time you disagreed with someone more senior and your idea won out (we value ideas over hierarchy)”Framework: STAR, but be specific about how you raised it (not just that you were “right”) and what changed as a result. Vague “I spoke up” answers land weaker than a concrete before/after.
6. Tell me about a time you changed something because of user feedback or user impact (we are customer obsessed)
Section titled “6. Tell me about a time you changed something because of user feedback or user impact (we are customer obsessed)”Framework: Describe the signal you noticed (a complaint, a metric, a support ticket pattern), what you changed, and the measurable effect - riders/drivers/users, not just “the team was happier.”
7. Tell me about a time you took a real risk on a project (we make big bold bets)
Section titled “7. Tell me about a time you took a real risk on a project (we make big bold bets)”Framework: Explain the safer default option, why you chose the riskier path anyway, and the actual outcome - including what you’d do differently if it hadn’t paid off.
8. Tell me about working with a very different team or background (we celebrate differences)
Section titled “8. Tell me about working with a very different team or background (we celebrate differences)”Framework: A concrete collaboration story - cross-functional, cross-geography, or cross-discipline - not a generic “I value diversity” statement.
9. Strengths and weaknesses
Section titled “9. Strengths and weaknesses”Strength: give evidence tied to one of the norms above. Weakness: real, non-fatal, with a concrete improvement action - not “I work too hard.”
10. Are you willing to relocate / what’s your notice period?
Section titled “10. Are you willing to relocate / what’s your notice period?”Answer directly. Uber’s India entry-level hiring is concentrated in Bengaluru, so relocation questions are common and usually asked plainly, not as a trick.
11. What do you know about Uber?
Section titled “11. What do you know about Uber?”Prepare 3 facts beyond the consumer app: the 2017 cultural-norms reset and why it happened, one specific engineering problem (dispatch, ETA, or surge pricing), and one recent public business or safety initiative.
12. Do you have any questions for us?
Section titled “12. Do you have any questions for us?”Ask about how the team handles a norm like “ideas over hierarchy” day to day, what success looks like for this role in six months, or the tech stack for the team you’d join. Avoid making compensation your first question.
Real examples to prepare before Uber’s HR round
Section titled “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 |
Red flags to avoid
Section titled “Red flags to avoid”- Answering “why Uber” with only the consumer app, no engineering or scale angle
- Badmouthing gig workers, drivers, colleges, or other companies
- Vague “I’m a team player” answers with no specific story attached
- Memorized speeches that ignore the actual question asked
- Only asking about CTC/WFH in the first breath
- Zero questions at the end