I was reached out to by a recruiter on linkedin and applied on their website. I was immediately sent a "2-3 hour" assessment without anyone in the company having taken even 5 minutes to chat with me and see if expectations aligned. While I believe a technical interview is necessary for a technical role like this, asking me to spend hours up front without having spoken to me is disrespectful of my time.
Interview questions [1]
Question 1
1. read JSON data containing user login behavior from an AWS SQS Queue, that is made available via a custom localstack image that has the data pre loaded. 2. Fetch wants to hide personal identifiable information (PII). The fields `device_id` and `ip` should be masked, but in a way where it is easy for data analysts to identify duplicate values in those fields. 3. Once you have flattened the JSON data object and masked those two fields, write each record to a Postgres database that is made available via a custom postgres image that has the tables pre created.
I applied online. The process took 2 weeks. I interviewed at Fetch in Jul 2024
Interview
It started with a take home assessment which included building a pipeline. After a week, I was selected for a zoom interview. The interview was going well. Towards the end, I was not able to answer some of the technical questions. The position was data engineer and DevOps. This must be the reason for my rejection. The best thing is I got a feedback later suggesting improvements on my weak areas.
Interview questions [2]
Question 1
Asked to describe my projects that were mentioned in my resume
I applied online. The process took 3 weeks. I interviewed at Fetch (Chicago, IL) in Apr 2024
Interview
1. Was first given a take-home assessment that's about cleaning a given dataset and took me a day ish to finish
2. Zoom interview (90 minutes) about past experiences and then a SQL challenge
3. On-site interview (4 hours). Everyone seemed to be nice but you need to be careful about showing your thinking process of how to solve the problems as I sort of overlooking it when I started solving the coding problem. The interviewer consider me as memorizing the solution. I did have done the same question before but jumped into setting up the question for 2 minutes, then explained the solution I had in mind. I guessed it was these two minutes that made the interviewers think I had it memorized and lacked iterative thinking, which I did not expect them would think this way as I did walk them through my thinking process before I started coding the main logic. Overall the interview was not too hard, it's just that you did not know when you would accidentally give them a reason to red flag you.
Interview questions [1]
Question 1
Write SQL queries based on business questions and ERD
