Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Asana

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Asana | Offres d’emploi chez Asana | Salaires chez Asana | Avantages sociaux chez Asana
      Entretiens chez AsanaEntretiens d’embauche pour Data Scientist chez AsanaEntretien chez Asana


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Data Scientist

      25 sept. 2018
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Asana en sept. 2018

      Entretien

      Initial phone screen followed by a take home data challenge, then another interview with the data science hiring manager. This would be followed by an onsite or onsites. In general they were very nice. However, their data science interview process isn't very good. This was also noted by another interviewee. The take home data challenge is fine, but the rubric for assessing it is a bit nebulous. Furthermore, they do not address the work you do in the take home challenge in the next interview with the hiring manager. A lot of companies do this, and it is I think a waste of candidates' time and effort. If there is anything candidates can do in the data science interview process that looks anything like the work they will actually do, it is the take home data challenge. The question, or 'gotcha,' that is asked during the technical interview with the data science hiring manager is perhaps a 'knowledge' question like the other interviewee alluded to. I initially was a bit hazy on where exactly they were going with the question, but I mentioned it looked kind of like reservoir sampling. However, I only vaguely remembered reservoir sampling. The hiring manager even addressed before asking the question that it isn't really the best type of question to ask over the phone. So why do they ask it? It is definitely an irrelevant question since it is really a poor proxy to determine whether a candidate could actually perform well as a data scientist. Just a bad question. Asana is not the only company that asks stuff like this, but that is no justification, companies really need to have have better, i.e. relevant assessments of data science candidates; there is really no excuse for this. If future data scientists read this, and have had similar experiences, I think they (you) should write about your experience. Companies really need to get their act together. Ironically, of all the disciplines that have an interview process one would think that data science would have a better approach to hiring and interviewing; experimental design and counterfactuals are a big part of data science. Finally, I was sent a generic rejection email, but the hiring manager did say the initial recruiter would get back to me. If you say you are going to do something, do it.

      Questions d'entretien [1]

      Question 1

      You get a stream of numbers, you don't know how many, you can't assume any underlying distribution for them. However you must return 1 of them with equal probability. There is a a naive approach. However,then the issue becomes storage, you don't want to store all the numbers, but still want to return 1. So the issue really is giving every number coming in a equal chance of being stored; not necessarily the issue of returning any number from the stream with equal probability. Yada, yada, yada.
      Répondre à cette question
      2

      Autres retours d’entretien d’embauche pour un poste comme Data Scientist chez Asana

      Entretien pour Data Scientist

      2 oct. 2024
      Candidat à l'entretien anonyme
      Vancouver, BC
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Asana (Vancouver, BC) en mars 2024

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Which success metrics would you choose for product A?
      Répondre à cette question

      Entretien pour Data Scientist

      8 août 2023
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 5 semaines. J'ai passé un entretien chez Asana en juin 2023

      Entretien

      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.

      Questions d'entretien [1]

      Question 1

      Solve SQL, think about this case
      Répondre à cette question

      Entretien pour Data Scientist

      4 nov. 2022
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Asana

      Entretien

      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.

      Questions d'entretien [1]

      Question 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.
      Répondre à cette question