I applied through an employee referral. The process took 2 weeks. I interviewed at Amazon (Boston, MA) in Mar 2022
Interview
the first round: one coding problem and one case study with statistical knowledge. Coding is not easy, you need to practice a lot. Case study is kind of simple but you need to be familiar with the statistical concepts.
Interview questions [1]
Question 1
one coding problem and one case study with statistical knowledge. Coding is not easy, you need to practice a lot. Case study is kind of simple but you need to be familiar with the statistical concepts.
I applied online. The process took 2 weeks. I interviewed at Amazon (Los Angeles, CA) in Apr 2022
Interview
There's an initial phone screening by a recruiter and after that there is a technical phone screening by a Sr data scientist. If you pass that they invite you to do a group interview.
Interview questions [1]
Question 1
breath of knowledge in data science with a live coding assessment
I applied through a recruiter. The process took 2 weeks. I interviewed at Amazon (San Francisco, CA) in May 2022
Interview
Contacted by a recruiter, started with a normal recruiter phone screen. Advanced to a 1 hour online technical. The technical was given individually by a data engineer (not data scientist).
During the technical I was asked a relatively basic SQL question to pseudocode in a shared notebook type thing (The interview was through Amazon's Chime app). Despite informing the interviewer that I can eventually make SQL work, but I find the syntax inside out and upside down (and need an interpreter to check my syntax), he still insisted on smashing through this question instead of moving on to python (he did eventually let me solve the question using pandas pseudocode instead of SQL, after wasting at least 20 minutes where I was googling syntax and talking out my solution). Multiple times the interviewer effectively accused me of lying about "knowing SQL", even while I reminded him that I did not use SQL as a primary language, and that while I was capable with extended amounts of time and an actual interpreter, I was not presuming to be an expert. In the end we didn't even have time to go past the first python-type question (which I answered in 1/10th the amount of time as we wasted on the very-basic SQL question).
Icing on the cake, I received a rejection email on a Saturday evening, which I consider to be fairly unprofessional. At that point I expected to be rejected, but it still seems like information you should transmit at least during business hours, if not on a business day.
Interview questions [1]
Question 1
How to build a summary table out of a written-in-a-notepad-document table of cricket wins and losses by country.
How to check the validity of an IP address string given some list of constraints.