I applied online. The process took 3 weeks. I interviewed at Uber (Pittsburgh, PA) in Oct 2016
Interview
Recruiter contacted to discuss if I have a suitable background. Then one telephonic interview to go through my resume and project. Some questions about debugging techniques and C++ fact checks.
Then there was one take home assignment. It was to test C++ 11 skills and design skills. The assignment was about writing a data structure.
Next were 5 onsite interviews. 45 Minutes each. First 2 were medium and hard array based questions. Both of them could be found on leetcode. Next was a design question. I was asked to write classes and api signatures. No implementation. Next was more about digging into resumes, coursework, projects and concepts. There were all sorts of questions relevant to computer science, but were short questions. Last one was about system details. More about what happens when you execute a program. Very fine details. More about memory access, instructions and their operands, representation of data in memory etc. The same interviewer asked me another basic question and write a code on whiteboard. It was a simple one.
Interview questions [1]
Question 1
Signed NDA. But questions were very standard ones.
I applied through a staffing agency. I interviewed at Uber (Hyderâbâd) in Aug 2016
Interview
it was telephonic&online round.it supposed to be 1 hour(max).there was lot of internet connectivity problem from their office.interview went for 1hour 30 minutes.he told my approaches were good.because of connectivity problem i couldn't write,compile and run code fast enough.i got rejected in the round.no issues :)
but i mailed them for technical feedback and there was no response.please try to provide feedback to candidates.
Interview questions [1]
Question 1
questions are of average complexity like merging 2 sorted arrays
I applied through college or university. The process took 3 days. I interviewed at Uber (Pittsburgh, PA) in Oct 2016
Interview
Phone interview with several background questions. Discuss my research and so on. It's like I'm not who they search for. The interviewer is a senior robotics engineer. You have to show what you know in depth. Otherwise he can tell whether you really understand it or not. It is like a phone screen.