Technical Interview: Python + SQL Questions - 1 hour

0-5 min: Interview started with normal introductions. It was like any other interview.

5-20 min: Questions based on the resume. I went deeper into my projects, but the interviewer couldn't understand. It felt like a fresher interviewing for a senior data engineer role.

20-30 min: Python question. It was too easy – counting each character from a string. I used defaultdict. To my surprise, the interviewer wanted me to use the Counter function from the collections library. I explained the difference and time complexity.

30-50 min: SQL, easy level. The worst part was that the interviewer was dictating 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 the time I was writing data for the tables. Chewy should really look at who they are asking to conduct these interviews. That's nonsense when you're interviewing senior-level candidates. The interviewer couldn't even frame the questions correctly and wanted me to write functions for simple static tables. (This is arguable, but at that point, everything was frustrating.)

50-60 min: Usual Q&A time with the interviewer.

Overall, I felt the interviewer was only expecting their own answers and was not open to alternatives.

1. Python: Count each character in a string.

2. SQL: Some basic join and window function questions.

3. Resume-related questions.