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 Software Engineer 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 Software Engineer

      2 juin 2016
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Asana

      Entretien

      I had a coding challenge, a phone-interview and an on-site interview. The initial phone screen and the first interview of the on-site was fine. The interviews were enjoyable and resulted in a reasonable reflection of my ability. The interviewers were courteous and supportive. The last on-site interview, however, was the worst interview that I have ever had. During this interview, the interviewer came across as distracted, aggressive and increasingly frustrated. It felt obvious that he had already decided to fail me. I perceived him to be programming during the interview, rather than taking notes, which was off-putting. He seemed visibly frustrated each time he gave me a hint, and seemed to make this very clear to me. He made one or two sarcastic comments during the interview and by the end he had lost all interest in answering my questions. It is a single data point and it may have just been an engineer having a really bad day or I may have made a misjudgement in my assessment. That being said, my overall description would be that the interview left me feeling small and humiliated. The experience was so bad, that had I been extended an offer, I would have seriously considered choosing elsewhere based on this single experience*. Upon reading Glassdoor, it seems this experience corroborates with another negative interview experience. For each Glassdoor review, there will be many more similar interview experiences in which the candidates did not write a review. Based on the Glassdoor sample, 10% (2/20) of Asana's software engineering interviews resulted in the candidate having the worst interview experience they’ve ever had. Engineer time and interviews are expensive, so Asana has an incentive to fix this. However, the most damaging aspect is probably that it hurts the reputation of the company, which reduces the likelihood of attracting great people. *Asana is a small company, so if you are considering working here, it is likely that you will work alongside this engineer.

      Questions d'entretien [1]

      Question 1

      A dependency management question, which can be represented as a topological graph.
      Répondre à cette question
      6
      avatar
      Réponse de Asana
      9y
      Hi, I'm part of the technical recruiting team here at Asana, and wanted to respond to your review—our apologies for the delay! While we're pleased to hear that the majority of your interviews went well, I wanted to sincerely apologize for the nature of your final on-site interview. The treatment that you received is inexcusable—nobody should feel small and humiliated after an interview, and making a candidate feel that way goes against all of our interview training and principles. We've taken your feedback, as well as other interview feedback that you've referenced here, and are addressing it across the team in the hopes that future candidates don't have the same experience. Thank you again for your feedback—without it, we wouldn't have been made aware of the kinds of experiences candidates are having, or been able to take the steps to ensure that it doesn't happen again.

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Asana

      Entretien pour Software Engineer

      3 juin 2026
      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 mai 2026

      Entretien

      Initial screening went well and I felt genuinely excited about the opportunity. The technical interview itself was different from what the preparation PDF described — less collaborative, minimal engagement from the interviewer's side. I didn't receive any feedback after the session; the interviewer went on sick leave and I waited several weeks before receiving a rejection email. I'm fine with rejection — that's part of the process. What was harder was the uncertainty and the lack of feedback. The prep materials set clear expectations around collaboration and communication, and the actual experience didn't match that.

      Questions d'entretien [1]

      Question 1

      lc medium + system design.
      Répondre à cette question

      Entretien pour Software Engineer

      13 mars 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Asana en févr. 2026

      Entretien

      Overall, it was a good experience. There was one interviewer who acted standoff-ish and strange. But, for the most part, it was conducted very professionally. What I didn't like was the Systems interview question, which is a very specific modelling problem and unless you've worked on building such a feature, it's unlikely that you'll recognize such a pattern and come up with a decent solution. And for a mid-level position, it's quite surprising. But I guess they gotta justify the high comps somehow. Also, infrastructure knowledge is not tested at all in this interview, which is atypical. The coding interviews were great. Study typical LLD problems. Leetcode is minimal and simple. Focus on understanding patterns and not memorizing solutions. The HM interview was great. He probed in ways typical EMs have never done before, and it gave me a really good impression of the company and his team, despite also not passing this interview, which I take full responsibility for.

      Questions d'entretien [1]

      Question 1

      Tell me about a time you experienced mentorship, as a mentor or a mentee
      Répondre à cette question

      Entretien pour Software Engineer

      20 janv. 2026
      Candidat à l'entretien anonyme
      Vancouver, BC
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Asana (Vancouver, BC)

      Entretien

      classic lc style medium question, and some basic intro be havioral in technical. good inter viewers. made sure the ex perience is pleasant for interviewee. did not get offer tho.

      Questions d'entretien [1]

      Question 1

      lc style medium qu estion
      Répondre à cette question