Solicité el puesto a través de la recomendación de un empleado. El proceso duró 4 semanas. Acudí a una entrevista en Uber (San Francisco, CA) en jul 2017
Entrevista
Applied through a referral. Went through a technical phone screen that included a live coding problem using coderpad. Then went through a all day on site interview. The interviewers were professional and well trained. Though I thought the interviews went pretty well they decided not to move forward. It took more than a week for them to get back to me, the recruiter wanted to give me feedback then disappeared, eventually someone got back to me after a long pause, that was rather sloppy of them.
Preguntas de entrevista [4]
Pregunta 1
An Android coding challenge to write a image viewer app from a open api.
Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en Uber
Entrevista
Applied online through my University portal. Two skype interviews of one hour each. Good questions asked. Data structures and algorithms questions asked in each interview. Any language was ok. Interviewer was friendly. In-detail questions asked about Android development. Overall good learning experience even though I was out in second round.
Preguntas de entrevista [1]
Pregunta 1
1. Given a list of list, of type [x,y] each such that this driver is available between x to y; find the time having maximum number of drivers available for a ride.
2. Add two binary strings
Asked a lot about Android.
Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Uber (San Francisco, CA)
Entrevista
Applied a long time ago on the ATS system. Got a email from a sourcer on LinkedIn to invite me to interview. I setup one time but it was cancelled due to "unforeseen circumstances" so we rescheduled for next week. I did the phone interview but I thought it was unfair. The interviewer was using my resume from two years ago. Apparently on CodePair it tells the interviewer every time you change windows. Also, the interviewer said something factually wrong saying ArrayList get method is O(n) and not O(1). The interviewer made a big deal about using a data structure that had O(1) lookup time that I could use along with HashMap. I suggested using ArrayList but he said it was O(n) lookup like LinkedList so it wouldn't work. I went along with it since I wasn't EXACTLY sure but failed to solve the problem in the end trying to follow the interviewer's dubious hints. The interviewer wanted the solution done a certain way. I received a no-reply rejection email the following HOUR with no recruiter feedback.
Preguntas de entrevista [1]
Pregunta 1
LRU Cache and some various Android questions, mostly about threading
