Amazon Business Intelligence Engineer interview questions
based on 293 ratings - Updated Jun 17, 2026
Averageinterview difficulty
Mostly positiveinterview experience
How others got an interview
49%
Applied online
Applied online
25%
Recruiter
Recruiter
20%
Employee Referral
Employee Referral
4%
Campus Recruiting
Campus Recruiting
2%
Other
Other
0%
Staffing Agency
Staffing Agency
Interview search
293 interviews
Viewing 226 - 230 of 293 Interviews
Amazon interviews FAQs
Candidates applying for Business Intelligence Engineer roles take an average of 30 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Amazon overall takes an average of 27 days.
Common stages of the interview process at Amazon as a Business Intelligence Engineer according to 1 Glassdoor interviews include:
Presentation: 50%
One on one interview: 50%
Here are the most commonly searched roles for interview reports -
I had interviewed for another role in the past where they said the first round is technical and it wasn't. All behavioral based so be ready for both. This interview was no different even though I confirmed with the person who set up the interview that the first round was technical. What a mess.
Amazon is a machine and as a result their recuritment is too. Don't expect any feedback because you won't get any. They are obsessed with the leadership principals which some are just down right creepy. Like "customer obsession"? Seems stalkerish.
I am over these whole let-me-fill-out-a-worksheet-interviews. It makes the interaction so one sided and not as it should be: a conversation.
You are just another number to them. If that's what you want then go for it. If you want to make an impact go somewhere else.
I applied through an employee referral. I interviewed at Amazon (Seattle, WA)
Interview
Was referred by an existing employee.
The steps in the interview process where
1. Technical discussion - Mostly SQL related questions
2. Onsite - 5 rounds of technical and behavioral-related questions
I applied through a recruiter. The process took 5 weeks. I interviewed at Amazon (Seattle, WA) in Jul 2019
Interview
I was contacted by a recruiter on Linkedin. I was a great match for the job description that was posted. I had 1 phone interview set up with the Director, but at the last moment he could not make it so I had a rushed, unprepared interview with someone else on the team. Phone interview was mostly regular data warehousing concepts and SQL questions (types of joins, paritioning, etc). I did well enough in this conversation to make it to the on-site interview. The radical differences in expectations, questions and answers to my questions about the role/team between the 5 interviewers made me think that they were not on the same page about this role. The Data Engineer said that BI Engineers just build views that the users ask for; but then he quizzed me on data engineering concepts for the rest of the hour. At least in my interview with the BI Engineer who would be my peer, I actually wrote SQL for the first time in this process (on a worksheet they had printed out for me, during the last interview of the day in the final round on-site). But the BI Engineer said that they basically do everything and data engineering would only get involved in really complex situations; he then proceeded to also give me a vocab quiz on advanced data modeling and big data performance topics. Mind you, the job description only required "Experience with MS Excel, Access and SQL/SAS"... "MBA preferred"... I thought they were looking for someone to develop KPIs and help automate their customers' processes... not architect the whole Redshift cluster. On the plus side, if you read and memorize Kimball you can crack this interview with very, very little actual SQL skills.
Interview questions [2]
Question 1
From a financial analyst: "Why isn't Excel your favorite analytics tool? Isn't it the best? What would you possibly use except for Excel?".
From data & BI engineers: redundant vocabulary pop quizzes on dimensional modeling, performance tuning, big data. Really simple SQL questions that required knowledge of joins and Group By.