Fragen im Vorstellungsgespräch zu Beschäftigung als Senior Data Scientist bei Uber

Remote interviews with hr, hiring manager and 4 teammates The interviews had 4-5 specific questions to cover and timing was tight There was a coding step that I was informed it would be a SQL question but in the end it was actually to implement a model in Python

they literarily just ghosted me. i followed up with recruiter and still no response. is this really how you treat your candidates? when they first reach out, recruiter was super attentive and bubbly. all fake...

All the interviews mainly focussed on SQL, AB Testing and product analytics. I was rejected in the final round. At first HR will screen followed by below 5 rounds. Round 1: Conducted by a senior data scientist a) Live SQL Coding - given a case and 4 tables, I had to solve it using SQL (usage of joins, window functions etc.) b) Meta and Uber product related metric questions Round 2: Conducted by a product manager a) Metric cases b) A/B testing etc. Round 3: Conducted by a data scientist a) Stats, ML and probability questions b) Product case c) A/B Testing case Round 4: Hiring Manager Round a) Product questions b) Past experience Round 5: Bar Raiser from a Director a) Random behavioural questions Seems like Uber is hiring in India now. Interviews were medium level difficulty and it can be cleared if one is exposed to product metrics and SQL. You can practice SQL using stratscratch and Hackerrank. And for product data science questions, refer to dataandmetrics.com or interviewquery.

It was very awkward and strange. I was asked " how would I select a random row from a table efficiently from a DB" and I replied "There are inbuilt random functions in SQL" and then proceeded to explain that other functions exists depending on the SQL engined like "table bernouli" for a bernoulis random sample. For some reason The interviewer wasn't satisfied and asked how I would construct my own random algorithm.

There were two initial interviews, and then a virtual on-site split over two days, with a total of six interviews. One of those was a coding interview, another was econ modelling, and another was statistics.

The interview process was fairly organized throughout. The hiccup occurred when I had to push my on-site by a week because of the death of a first degree relative. When I showed up to the interview, I was informed that the original role had already been filled. This had not been communicated anytime prior, and I had just traveled from across the country for that interview. We still proceeded with the on-site but it was obvious there was no match since the original team was doing work in a very specific field.

First recruiter reached out to me and we chatted, then general chat with hiring manager which went very well. Next was technical phone screen which was challenging and very stats oriented. Apparently, there were some "concerns" but they still wanted to move forward and give me an exam. After this I got a ridiculously long take home exam, I spent literally 10-12 hours working intensely on it, but easily could have spent much more and I am somebody that can work quickly. The 3 sections were all reasonable but just was a lot to ask. After turning it in, I heard back from the recruiter that said I scored very well on it (apparently they send the test to a separate Data Scientist outside the team you interview with to grade it). I was happy to hear this and expected to be called in for the final round in-person interviews. But then the recruiter told me that the hiring manager wanted to chat with me again on the phone. I agreed and expected a chat about the test I turned in or perhaps just more background on what the role would be and whether it made sense for me to go in for the in-person final round. Instead, after telling me he hadn't seen my exam nor the score for it and proceeded to give me ANOTHER technical phone screen which I was NOT expecting. I was annoyed but still tried to answer the questions but it did not go smoothly. I then heard back 2 weeks later that they did not want to move forward. Think very carefully about whether you want to invest the time in doing the take home exam. Overall, a terrible experience.

First got referred by a friend's friend. Then got an phone call with a recruiter. She asked me about my interest and introduced the team. Then got a take-home exercise. Some practical problems Uber is facing. 3 Problems. Turned it in one week then got rejected. I wrote a 8 pages report.

First phone screen was was with a refreshingly knowledgeable recruiter; usually those are pretty weak. On site was technically easy (e.g. describe these distributions, how do you use R to plot this and that) for a Sr Data Scientist. The interviewers did a good job of describing the role in its day-to-day, and did a very good job at selling the responsibility of it. The offered salary, however, was far below the norm for a Senior Data Scientist role — hiding behind the line of "we're a startup so it's low cash and good options" doesn't work for Uber anymore . . . the strike price for new hires isn't very good; I would hesitate to even exercise offered options