Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Asana (San Francisco, CA) en feb 2016
Entrevista
I was contacted by a recruiter to apply for a data science position. Initial phase was a coding challenge. They sent a dataset, and you were expected to produce some results and answer some questions. Pretty typical. Next phase was a phone interview with one of the data scientists. Basically walked through one sampling/probability type problem for about 20 minutes and then answered some data science systems level type problems.
After that, they flew me out to have an onsite interview. The place they put you up in overnight is really nice. The interview lasted about 5 hours in total, lunch included. This consisted of several one-on-one interviews with a handful of the data scientists and a data science manger. Primarily systems level, experimental design type questions, with some technical deep dives when necessary. To be honest, I think the conversations might have gotten more technical if I had done better in my interviews, so YMMV. Was in the wrong frame of mind going in; I was thinking and prepping very technical material, lots of coding, machine learning and the discussions were pretty much on the other side of the spectrum. Little to no coding questions through the whole process, which I was surprised by.
The whole process was great, and the company seems really awesome. I wish I had done better! :)
Preguntas de entrevista [1]
Pregunta 1
I'm not going to answer this in specific. Be prepared to answer lots of experimental design questions. How you would direct new features, test changes to a product, what types of data to collect, etc.
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Asana (Vancouver, BC) en mar 2024
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Which success metrics would you choose for product A?
Envié una solicitud electrónica. El proceso duró 5 semanas. Acudí a una entrevista en Asana en jun 2023
Entrevista
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.
Envié una solicitud electrónica. Acudí a una entrevista en Asana
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 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.
