The first round was a normal recruiter screening which was casual and a good conversation.
The second round was a coding challenge.
The process specified that the challenge could be done in any language, but unfortunately they asked me to do it in SQL, whilst I only use Python + PySpark at work. Had I known, I would have brushed up my SQL beforehand.
The coding challenge would've been easier in SQL, but I chose to use python as I was thrown off by the surprise. As a result, there were quite a few difficulties because of the query-type nature of the question. If I were to go back again, I'd give it a shot in SQL rather. Or pyspark, but they didn't let me do that.
Feedback to recruiters / interviewers: Don't surprise us like this!
Domande di colloquio [1]
Domanda 1
First round: Normal recruiter screening
Second round: Coding challenge
Ho presentato la mia candidatura online. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Asana (Vancouver, BC) nel mese di mar 2024
Colloquio
One screening interview with a recruiter and after an SQL/product analytics interview with a Data Scientist. Got declined after the latter.
The SQL/product interview was a weird experience with the interviewer showing up late and having network connectivity issues even after joining. We also had technical difficulties with the online coding tool zoom so that I could not see large areas of the editor at any given time.
After the technical difficulties, we rushed through the questions without a real chance for a true discussion.
Domande di colloquio [1]
Domanda 1
Which success metrics would you choose for product A?
Ho presentato la mia candidatura online. La procedura ha richiesto 5 settimane. Ho sostenuto un colloquio presso Asana nel mese di giu 2023
Colloquio
One of the most disappointing and frustrating interview processes I have experienced. Applied online, contacted by a recruiter to set up a screen. Recruiter missed the initial phone screen and we rescheduled to another day that week (first red flag for this recruiter). After recruiter screen, set up technical screen - part SQL, part Case Study. Reasonable questions. Again, recruiter took a full week to get back to me after the screen, with positive news. I asked to accelerate the process as I had other offers/was further along with other companies then. Followed up several times to be ghosted for 2 weeks. 2 weeks later, recruiter emails asking if I can do the final round the following day. I couldn't - had other commitments and need time to prep, etc. so asked for a couple more days. I sent it my availability and while waiting for the final round to be scheduled, I get an email that they filled the role. I understand when companies want to move fast and fill the role, but this was a colossal waste of my time and the recruiter was honestly terrible. All the interviewers I did get to meet seemed nice and reasonable.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Asana
Colloquio
I applied online, and the recruiter reached out one week later to schedule a 30-min video chat with HR. One round of 1hr technical phone screening and then one day of onsite.
Domande di colloquio [1]
Domanda 1
Intro, SQL, Case. The interviewer is not very experienced, there are a couple of times that the interviewer struggled to lead the conversion and obviously can tell that they are looking for some really specific answers as opposed to an open-ended case study.
