Uber behavioral interview: Interview competencies (official interview guide)
The official guide lists these as the competencies scored across rounds; the recruiter tells you which apply to your role. The behavioral round wants STAR stories showing ownership, influence and grit.
| Progress | Principle | Your story |
|---|---|---|
| Collaboration & LeadershipCollaboration and inclusion | Write a story | |
Sample answer: Describe a project that needed several teams. How did you get them aligned?Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out. Situation We had to replace our login flow with a new identity service by the end of the quarter. It touched four teams: backend, web, mobile and a small team in another time zone that ran the identity service. Two earlier attempts had stalled because teams kept waiting on each other. Task I was the backend engineer and was asked to coordinate the engineering side. None of the other engineers reported to me. Action I started by meeting each team separately to hear what they needed and what had gone wrong last time. The same issue came up: nobody agreed on the interface, so web and mobile could not start until backend was done. I wrote the API contract first and shared it as a short document for comments, then set up a mock server so web and mobile could build against it from day one. I replaced a long weekly meeting with a 20-minute sync, plus a written update for the identity team, because the meeting time was late in their evening. When mobile fell behind because of a release freeze, I moved two backend tasks earlier so their work was not on the critical path. In the final demo, I asked each team to present their own part. Result All four teams shipped within the quarter, a week ahead of the date, with no login incidents at launch. The identity team said it was the first cross-team project where they did not feel like an afterthought, and the contract-first approach became our default for shared APIs. Tip: Show how you helped others succeed and made people feel they belonged. Collaboration and inclusion: weak answer, follow-ups and level differences | ||
| Design & ArchitectureBig impact and long-term thinking | Write a story | |
Sample answer: Tell me about the most ambitious project you have proposedWhether you can see past the next sprint, propose something with a larger or longer payoff, and make a convincing case for it while still delivering value along the way. Big ideas without a plan or results score poorly. Situation Every team in our organisation sent analytics events in its own format. Each new report needed an engineer to write custom parsing code, and data analysts spent about a day a week cleaning events before they could use them. Task I was asked to fix the parsing for one new report. I thought the real fix was a shared event format for the whole organisation, which no single team owned. Action I did the one report as asked, then wrote a two-page proposal for a shared event schema with a small registry: teams would describe each event once, and invalid events would be flagged as they arrived. I estimated the cost honestly at two quarters of part-time work across teams, and showed the payoff using the analysts' own time logs. To make it less of a leap, I proposed starting with the three teams that sent the most events and keeping the old formats working in parallel. I got agreement from the analytics lead and two engineering managers, then built the registry and validation with one other engineer. I paired with each of the first three teams for their migration and wrote a guide so later teams could move on their own. Result After two quarters, nine of twelve teams had moved over. New reports went from about a week of engineering work to a day, and analysts got back most of the day a week they spent cleaning data. Invalid events were caught in minutes instead of being found weeks later in reports. Tip: Show you thought beyond the next sprint and made a bet with a long payoff. Big impact and long-term thinking: weak answer, follow-ups and level differences | ||
| Software EngineeringHigh standards | Write a story | |
Sample answer: Tell me about a time you were not satisfied with good enoughWhether you notice quality problems others have learned to live with, fix them in a way that sticks, and know when high standards matter more than speed and when they do not. They want a standard you raised for the team, not just your own code. Situation On my team, about one in five builds failed because of flaky tests, tests that pass or fail at random. Everyone had learned to click "re-run" until the build went green, and real failures were sometimes re-run away. Task Nobody had asked anyone to fix it, but in one month two real bugs reached production because their failing tests were dismissed as flaky. I decided to get flaky failures down to a level where a red build meant something again. Action I started by measuring. I wrote a small script that read three months of build history and listed every test that had both passed and failed on the same code. Twenty-three tests caused almost all the flakiness, and most shared two causes: tests that depended on the clock and tests that shared one database without cleaning up. I fixed the worst ten myself over two sprints, mostly by using a fake clock and giving each test its own data. For the rest, I proposed a simple rule to the team: a flaky test goes into quarantine within a day with a ticket and an owner, so it cannot block builds or hide real failures, and it comes back only when fixed. I added a weekly report of the flaky rate to our team channel so the number stayed visible. Result Flaky failures dropped from about 18 percent of builds to under 2 percent in two months, average time to merge fell by about a third, and we had no more bugs reach production that were dismissed as flaky. The quarantine rule is still part of how the team works. Tip: Show you raised the bar on quality even when nobody asked, and why it mattered. High standards: weak answer, follow-ups and level differences | ||
| AdaptabilityResilience and courage · Ambiguity and judgment | Write a story | |
Sample answer: Describe a setback that almost made you give up. What kept you going?Whether you keep going after something goes wrong, without denial or blame, and whether you have the courage to make or support a hard call. They want to see how you kept yourself and others steady and what changed because you persisted. Situation My team rebuilt the checkout page of our shopping app to make it faster. We launched it twice, and both times we rolled it back within a day: first for a payment bug on one browser, then for a drop in completed orders we could not explain. Leadership was close to cancelling the project. Task I was the lead engineer. Morale on the team was low, and I had to decide whether to argue for a third attempt and, if so, make sure it would not fail the same way. Action I took a day to understand both failures. The browser bug was simple; the order drop was the real issue. From session recordings, I found that the new page hid the delivery-date selector behind a tap, and people abandoned when they could not see the date. Neither failure meant the rebuild was wrong; both meant our launch process was. I wrote a short plan for a third attempt with three changes: an automated test across our top five browsers, a gradual rollout starting at five percent with a comparison of completed orders against the old page, and an automatic switch back if orders dropped more than one percent. I presented it to leadership and said plainly that if this attempt failed, I would recommend stopping. I also talked to the team openly about the two rollbacks so nobody carried the blame alone. Result The third launch went to a hundred percent over two weeks with no rollback. Page load time fell by 40 percent and completed orders rose by about two percent. The gradual rollout with an automatic switch back became the standard for every customer-facing launch on our team. Tip: Show you kept going through a setback or made an unpopular call that was right. Resilience and courage: weak answer, follow-ups and level differences | ||
| Bias Towards ActionSpeed and delivery | Write a story | |
Sample answer: Tell me about a time you delivered under a tight deadlineWhether you deliver on time by making smart choices: cutting scope deliberately, removing blockers early and telling people the truth about risk. Heroics like working every night score lower than a plan that made the deadline safe. Situation Our team had to support a new invoice format required by a regulation in one of our markets. The date was fixed by law, and we found out about the full requirements with five weeks left, when the original estimate was ten weeks. Task I was the lead engineer for the change. I had to get something compliant out by the date without breaking invoicing for the rest of our customers. Action In the first two days I went through the regulation with our compliance colleague and split the work into "required by the date" and "nice to have". Only about half was truly required: the new fields, the digital signature and storing invoices for the legal period. Automatic corrections, a nicer PDF layout and support for older invoice types could wait. I wrote this down and got product and compliance to sign off on it. The riskiest part was the signature service, which depended on an outside provider, so we built and tested that first, in week one, instead of last. I put the new format behind a flag for that market only, so other customers were untouched. I gave a short written status every Friday with what was done, what was at risk and what I needed. Result We went live four days before the deadline. The later parts shipped over the next five weeks with no rush. Nobody on the team worked weekends, and there were no invoicing incidents during the switch. Agreeing the cut list in writing in week one was what made it possible. Tip: Show a hard deadline met by cutting scope wisely, not by heroics alone. Speed and delivery: weak answer, follow-ups and level differences | ||
| EntrepreneurialInvention and simplification | Write a story | |
Sample answer: Tell me about a time you simplified a complex processWhether you look for a simpler or new way of doing something instead of accepting how it has always been done, and whether the change had a measurable result. Interviewers also check that you brought people along, because simplifying usually means changing other people's habits. Situation Releasing our main backend service took a 14-step manual checklist: tagging, building, running database changes, updating three config files, a manual smoke test and posting notes. A release took about half a day, so we only released once a week, and roughly one release in five had a mistake in a manual step. Task I was not asked to fix this, but I was the one releasing that month and I wanted to make releases fast and boring enough to do daily. Action I timed each step for two releases and asked the three engineers who released most often which steps they feared. Most of the time went into three steps: updating the config files, waiting on the smoke test and writing notes. Instead of automating the whole checklist at once, I removed what I could first. Two of the config files only existed to hold a version number, so I replaced them with one value set by the build. I turned the manual smoke test into a short automated check against the staging environment, and generated release notes from merged pull request titles. Then I put the remaining steps into our pipeline with a single approval button. I ran the old and new process side by side for two weeks, and wrote a one-page guide so anyone on the team could release. Result Release time went from about four hours to 25 minutes, and we moved from weekly to daily releases. In the next quarter we had no releases with manual-step mistakes, and two other teams copied the pipeline. The biggest win was removing steps, not automating them. Tip: Show a simpler or new way of doing something and the measurable result. Invention and simplification: weak answer, follow-ups and level differences | ||
| GritResilience and courage · Ambiguity and judgment | Write a story | |
Sample answer: Describe a setback that almost made you give up. What kept you going?Whether you keep going after something goes wrong, without denial or blame, and whether you have the courage to make or support a hard call. They want to see how you kept yourself and others steady and what changed because you persisted. Situation My team rebuilt the checkout page of our shopping app to make it faster. We launched it twice, and both times we rolled it back within a day: first for a payment bug on one browser, then for a drop in completed orders we could not explain. Leadership was close to cancelling the project. Task I was the lead engineer. Morale on the team was low, and I had to decide whether to argue for a third attempt and, if so, make sure it would not fail the same way. Action I took a day to understand both failures. The browser bug was simple; the order drop was the real issue. From session recordings, I found that the new page hid the delivery-date selector behind a tap, and people abandoned when they could not see the date. Neither failure meant the rebuild was wrong; both meant our launch process was. I wrote a short plan for a third attempt with three changes: an automated test across our top five browsers, a gradual rollout starting at five percent with a comparison of completed orders against the old page, and an automatic switch back if orders dropped more than one percent. I presented it to leadership and said plainly that if this attempt failed, I would recommend stopping. I also talked to the team openly about the two rollbacks so nobody carried the blame alone. Result The third launch went to a hundred percent over two weeks with no rollback. Page load time fell by 40 percent and completed orders rose by about two percent. The gradual rollout with an automatic switch back became the standard for every customer-facing launch on our team. Tip: Show you kept going through a setback or made an unpopular call that was right. Resilience and courage: weak answer, follow-ups and level differences | ||
| Interpersonal InfluenceCollaboration and inclusion | Write a story | |
Sample answer: Describe a project that needed several teams. How did you get them aligned?Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out. Situation We had to replace our login flow with a new identity service by the end of the quarter. It touched four teams: backend, web, mobile and a small team in another time zone that ran the identity service. Two earlier attempts had stalled because teams kept waiting on each other. Task I was the backend engineer and was asked to coordinate the engineering side. None of the other engineers reported to me. Action I started by meeting each team separately to hear what they needed and what had gone wrong last time. The same issue came up: nobody agreed on the interface, so web and mobile could not start until backend was done. I wrote the API contract first and shared it as a short document for comments, then set up a mock server so web and mobile could build against it from day one. I replaced a long weekly meeting with a 20-minute sync, plus a written update for the identity team, because the meeting time was late in their evening. When mobile fell behind because of a release freeze, I moved two backend tasks earlier so their work was not on the critical path. In the final demo, I asked each team to present their own part. Result All four teams shipped within the quarter, a week ahead of the date, with no login incidents at launch. The identity team said it was the first cross-team project where they did not feel like an afterthought, and the contract-first approach became our default for shared APIs. Tip: Show how you helped others succeed and made people feel they belonged. Collaboration and inclusion: weak answer, follow-ups and level differences | ||
| InquisitivenessCuriosity and growth | Write a story | |
Sample answer: Tell me about something you had to learn quickly for a projectWhether you can learn something unfamiliar quickly and on purpose: a plan for what to learn first, using people and code as well as documents, and applying it to real work. Curiosity should lead to a result, not just a course you finished. Situation The engineer who owned our team's pricing service moved to another team with two weeks' notice. The service was written in a language nobody else on the team knew, and it was due for a change to support a new discount type in five weeks. Task I volunteered to take it over. I had never written that language, so I needed to become safe on call for the service within two weeks and ship the discount change on time. Action I made a plan around the service rather than the language. In the first three days I read the code path for a single price request from start to finish and drew it, writing down every language feature I did not understand. I learned only those features first, from the official tutorial and by writing small throwaway programs. I booked three one-hour sessions with the departing owner and used them only for questions I could not answer from the code, such as why certain decisions were made. To learn by doing, I fixed two small open bugs in my first week and asked an engineer from another team who used the language daily to review them. I kept a notes page of patterns and pitfalls, which became the service's onboarding guide. Result I took over on-call for the service after two weeks and shipped the new discount type a week early, with no incidents. A second teammate onboarded in four days using my notes. I still use the same approach for unfamiliar systems: trace one real request, learn what it needs, and ship something small in week one. Tip: Show something you learned on your own and how you used it at work. Curiosity and growth: weak answer, follow-ups and level differences | ||
How to answer
Use STAR: the Situation in one or two sentences, the Task you owned, the Actions you took (in the first person, the longest part), and the Result with a number. One strong story can cover several principles, so write a few good ones in the story bank and tag them.
Behavioral questions by theme, with a tip for each · How the behavioral round is scored
Questions people ask
What is the Uber behavioral interview based on?
Interview competencies (official interview guide): Collaboration & Leadership, Design & Architecture, Software Engineering, Adaptability, Bias Towards Action, Entrepreneurial, Grit, Interpersonal Influence, Inquisitiveness. The official guide lists these as the competencies scored across rounds; the recruiter tells you which apply to your role. The behavioral round wants STAR stories showing ownership, influence and grit.
How do I answer Uber questions on "Collaboration & Leadership"?
Whether you can get people who do not report to you to work towards one goal: making the plan clear, removing friction between teams, and giving others credit. They also look for how you included people who were easy to leave out. Show how you helped others succeed and made people feel they belonged. A typical question: Describe a project that needed several teams. How did you get them aligned?
How do I answer Uber questions on "Design & Architecture"?
Whether you can see past the next sprint, propose something with a larger or longer payoff, and make a convincing case for it while still delivering value along the way. Big ideas without a plan or results score poorly. Show you thought beyond the next sprint and made a bet with a long payoff. A typical question: Tell me about the most ambitious project you have proposed