Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empleadores

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Uber

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Uber | Empleos en Uber | Sueldos en Uber | Prestaciones en Uber
      Entrevistas en UberEntrevistas para el cargo de Software Engineer en UberEntrevista en Uber


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

      • Ayuda
      • Pautas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de autorización de cookies

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información desde adentro.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista para Software Engineer

      8 de jul de 2015
      Candidato de entrevista anónimo
      San Francisco, CA
      Sin ofertas
      Experiencia negativa
      Entrevista promedio

      Solicitud

      Me postulé a través de una recomendación de un empleado. El proceso tomó 2 semanas. Acudí a una entrevista en Uber (San Francisco, CA) en mar 2015

      Entrevista

      I was contacted by a recruiter asking me to interview. In the initial phone screen we spoke for 30 minutes about my resume and they emailed that day to ask for a follow up with a technical person over the phone. The phone interview was an hour long collaborative coding session with a programmer who asked me to solve a sorting problem. It wasn’t difficult and we talked about the solution while I was coding. The focus was on me having something that compiled and ran. He was enthusiastic and polite. It was a positive experience. I was asked to come in for a longer interview of 4 technical parts and a meeting with one of the managers. I was asked to bring a laptop, but I don’t have one so we organised that they would provide one preloaded with an IDE for coding. For each technical part there were two interviewers. Each started the same – they introduced themselves and asked a generic “tell us what you’ve been doing?” I was surprised none of them asked specifics about my resume, knew what I’d been working on, or drilled down into anything I said. I got the impression none of them had seen my resume and didn’t care about previous experience. Given that, I wish I had paid more attention to the time and prepared an elevator pitch about myself so that I could have spent more time focused on the technical part. It was immediately obvious that in many cases the interviewers had no idea how to conduct an interview either solo or with a colleague. I was frequently given conflicting instructions from the two interviewers, or told to ignore something the other had said and answer a different question instead. At times they talked insistently and loudly over the top of each other. For the coding session despite organizing to have a laptop waiting for me it wasn’t provided and the interviewer strongly rebuked me for not having brought my own. When I mentioned organizing one with the recruiter they knew nothing about it. I ended up coding on the interviewer’s laptop in a basic text editor on an unfamiliar keyboard. There was no focus on actual output at all and I couldn’t spend much time sitting down writing code because I kept being asked to answer questions on the whiteboard. In a later session I was asked the question and started brainstorming a solution with some pseudo-code on the whiteboard. I was instantly rebuked “what do you think you’re doing? You’re not going to be able to solve this using a function.” Later while I was working through the code I mentioned an edge case to check and the interviewers were lost why you should check at all, then got annoyed when I explained that checking edge cases was something you should do. There was a consistent theme of elitism and “we know better than you” with the interviewer’s attitudes. One person introduced himself with just “Hi. I’ve been on this team for 6 months. Before this I was at Google.” Another made sure to mention the Ivy League college they’d attended. My last session was 1:1 . After "tell me what you’ve been doing?” he asked “why do you want to work at Uber?” I started to talk about things I’d been doing at my current job and how I was no longer challenged. He interrupted me with a disgusted look. “I asked *why you want to work at Uber*, not *why you don’t want to work at your current workplace*”. I explained I was doing that and continued with how from my experiences I had learned I was interested in things like cutting edge tech, big data, etc. and I felt I could get that at Uber. I talked about how I like what they do and how great it is. He then deadpanned “so I’m getting you like technology, and you like Uber.” I was a little stunned at his attitude, but I honestly believe they have a great product so I elaborated more on why I thought Uber was doing good things. He tried to justify his question, “I’m an engineering manager and my success is based on the success of my team members, so I want to know what’s going to keep you here in 4 years’ time?” I was confused so I asked “4 years?” He said “yes, what’s to stop you from just packing up and leaving in 4 years’ time?” I wondered if he was being deliberately difficult in order to see how I would react. After explaining I didn’t know what he was implying he asked if I had any questions for him. I asked several in-depth questions about the work they were doing, technical aspects, etc. but he was done and just wanted to leave. He turned side on to me and faced the door, kept looking at his watch and out the window and giving short, dismissive answers. The recruiter turned up slightly after that and he left. During the day, no one said to me “here’s why we want you to come work here and where we see you contributing”. No one said “here’s why you should be here instead of Amazon, or Google, or Facebook”, and no one said “we have a great team here, it’s an amazing environment and we love working here every day”. Overall a horrible experience.

      Preguntas de entrevista [3]

      Pregunta 1

      What have you been doing in your current job?
      Responder pregunta

      Pregunta 2

      Why do you want to work at Uber?
      Responder pregunta

      Pregunta 3

      What’s to stop you from just packing up and leaving in 4 years’ time?
      Responder pregunta
      21

      Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer en Uber

      Entrevista para Software Engineer

      12 de jun de 2026
      Empleado anónimo
      New York, NY
      Oferta aceptada
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Uber (New York, NY)

      Entrevista

      Recruiter call, then Phone screen, then 5 stage interview onsite. Onsite Rounds: 2 programming questions -one algorithms & one general low-level design 1 system design 1 past projects 1 manager behavioral interview

      Preguntas de entrevista [1]

      Pregunta 1

      Implement the game of minesweeper
      Responder pregunta

      Entrevista para Software Engineer

      30 de abr de 2026
      Empleado anónimo
      Oferta aceptada
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Uber

      Entrevista

      The interview process started with a recruiter screen where they covered my background and the role's expectations. Next, I had a phone screen focused on technical skills where I faced a DSA question on frequent elements in an array. I had practiced similar problems on prachub.com beforehand, which helped me tackle it effectively. The technical rounds consisted of coding and system design questions, including rate limiting. Finally, I had a behavioral interview where they assessed cultural fit. Overall, the experience was average, but I received and accepted an offer.
      2

      Entrevista para Software Engineer

      3 de abr de 2026
      Empleado anónimo
      San Francisco, CA
      Oferta aceptada
      Experiencia positiva
      Entrevista promedio

      Solicitud

      Acudí a una entrevista en Uber (San Francisco, CA) en abr 2026

      Entrevista

      Recruiter screen then there was a hiring manager round which felt more like a mix of product sense + execution - mostly a mix of OOP algorithms in Python or Java and some high-level system design. The onsite was 5 back to back rounds covering data structures, database management (heavy on SQL and data lifecycles), deep sys design, and behavioral. The sys design round was the real test where I had to walk through building a scalable real-time gaming leaderboard, discussing tradeoffs ofcourse in architecture, APIs, and data flow. The coding rounds was around things like linked lists and tree traversals, while the behavioral part focused heavily on ownership of my code and handling feedback. When you prep, make sure you can go a level deeper on database management and object oriented patterns instead of just grinding LC I’d say. I did grind LC though but ensure you understand the depth behind everything you solve. I also did a few mocks with uber swe on prepfully specifically for the sys design and database rounds and that honestly helped me catch some blind spots in my architecture knowledge and practice explaining my tradeoffs clearly. I’d say get a mock or two from anywhere if you can - helped me a lot!
      3

      Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti

      avatar
      Amazon
      3.7★Remuneración y prestaciones
      avatar
      Google
      4.5★Remuneración y prestaciones
      avatar
      eBay
      4.0★Remuneración y prestaciones
      avatar
      Amazon Web Services
      3.9★Remuneración y prestaciones