Uber Business Analyst Interview Experience
Uber
They took my Power BI project apart step by step, from ETL and Power Query to row-level security, and then switched straight into live SQL on window functions. It felt less like a trick interview and more like a full check on whether I really knew my own work.
Interview process
My Uber process was short because I did not get past the first round. The round itself started with a normal introduction, then they had me explain one of my resume projects, and they went pretty deep into my Power BI work from ETL all the way to row-level security. After that, they switched into live SQL and asked questions around window functions, aggregates, CASE statements, PIVOT and UNPIVOT, plus a bunch of core SQL concept differences. Even though I was rejected after that round, the interview itself felt smooth, very professional, and focused on whether I really understood the work I had done. What stood out to me was that they were not rude or trying to trick me, but they were very thorough in testing end-to-end project knowledge and SQL fundamentals.
Interview rounds · 1
- 1
Technical round
BehavioralData Pipeline DesignSQLThe first round started with a basic introduction, then they had me walk through my strongest Power BI project in detail, and after that they moved into live SQL and quick-hit concept questions.
Q1. Can you introduce yourself and walk me through your education, tenure, and work experience?
How they answeredI started with a short introduction about my education, tenure, and work experience, and then we moved pretty quickly into my resume. The tone was professional and polite from the start, so it felt structured rather than stressful.
Q2. Can you explain one of the most prominent projects on your resume?
How they answeredI chose a Power BI dashboard I built for an insurance client to show the turnover of a team. I walked them through the full flow from procuring the data and ETL, then Power Query, data modeling, building the visualizations, publishing the report on Power BI web, and fixing row-level security. They also asked about DAX, especially time-related functions for monthly, quarterly, and yearly views. I explained how I used filter functions with CALCULATE and then applied the appropriate filter based on the requirement.
Follow-up questions- How did you procure the data and handle the ETL process?
- What did you do in Power Query and data modeling?
- How did you build the visualizations, publish the report, and secure row-level access?
- What DAX functions did you use, especially for time-based reporting and filtering?
Q3. Can you write SQL queries live and explain some core SQL concepts?
How they answeredThe SQL part was live, so I had to write queries in front of the interviewer. The patterns I saw were mostly around window functions combined with aggregate functions, CASE statements, and also PIVOT and UNPIVOT. On the verbal side, they asked standard but important distinctions like WHERE vs HAVING, RANK vs DENSE_RANK, CTE vs subquery, and DELETE vs DROP vs TRUNCATE. It felt like they wanted to check both hands-on query writing and whether my fundamentals were clear.
Follow-up questions- How would you use window functions together with aggregate functions and CASE statements?
- How would you handle PIVOT and UNPIVOT?
- What is the difference between WHERE and HAVING?
- What is the difference between RANK and DENSE_RANK?
- What is the difference between a CTE and a subquery?
- What is the difference between DELETE, DROP, and TRUNCATE?
Tips from the candidate
I would tell a friend to prepare one strong project end to end and be ready to explain every step without skipping anything. For me, that meant data procurement, ETL, Power Query, data modeling, visualizations, publishing, and row-level security. Also practice DAX around time-based reporting and filter logic with CALCULATE. On SQL, do live practice on window functions with aggregates and CASE statements, and make sure you can clearly explain basics like WHERE vs HAVING and RANK vs DENSE_RANK without overthinking.
Company culture
They came across as very professional and polite, and they maintained a tone of dignity throughout the interview. I felt they were genuinely trying to understand whether I had actually done the project work I claimed, not just asking random questions. The process felt structured, with a strong focus on practical BI knowledge and SQL fundamentals. Compared to some interviews that feel aggressive, this one felt smooth and respectful even though the evaluation was still thorough.