Technical Interview Python + SQL questions - 1hr 0-5 min: Interview started with normal introductions. it was like any other interview 5-20 min : questions based on resume. i was going deeper into projects but interviewer couldnt understand. it felt like some fresher interviewing for senior data engineer role. 20-30 min : Python question, it was too easy - counting each char from string. i used default dict. and to my surprised interviewer wanted me to use counter function from collection libraries. i explained the difference and time complexity 30-50 min : SQL easy level. worst case was interviewer was dictating me the tables and i was writing each value for each column in google docs. that was ridiculously funny. we did almost 3-4 follow up SQL questions and half of the time i was writing data for tables. Chewy should really look who they are asking to take these interviews. thats nonsense when you interview senior level candidates. Interviewer couldnt even frame the question correctly. and wanted me to write function for simple static tables. (this is arguable but at that point everything was frustrating) 50-60: usual Q&A time with interviewer, overall i felt like interviewer was only expecting their own answers and they were not open about alternatives.

Interview Process is friendly and Good with more focus on product sense and optimization of ETL process what kind of customer data is integrated and understanding of the business process