Initial resume screening took some time (approximately one month). I then received a reply from HR. We talked briefly about my previous and current job responsibilities.
The next step was a technical phone interview over Zoom. The first question involved a brief discussion of a software design problem, lasting about ten minutes. Following that, I was given a LeetCode medium-level question. I implemented the first solution that came to mind. After finishing, I compiled the code and ran it using a HackerRank interpreter for Python. I encountered two to three small syntax errors, which I quickly fixed and ran again. The code passed all test cases provided by me and the interviewer. The interviewer added some more tests, and they all passed.
We then started discussing how to optimize the solution and what tools could be used for optimization.
I felt it was an easy interview, despite my own fear of failing. However, the day after, I received a rejection without any feedback.
Overall, I felt disappointed by their attitude towards candidates. They do not consider the candidate's state while answering questions. Some candidates may be scared of failing, some stressed, and some may have hearing disabilities, among other factors.
The following metrics were computed from 2 interview experiences for the Uber Software Engineer, Backend role in Amsterdam, Netherlands.
Uber's interview process for their Software Engineer, Backend roles in Amsterdam, Netherlands is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Uber's Software Engineer, Backend interview process in Amsterdam, Netherlands.