J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Asana (Vancouver, BC) en janv. 2020
Entretien
i applied on Asana website for Engineer position and was contacted by the recruiter a month after somewhere in later January 2020. We spoke on the phone for 30 mins, Recruiter liked my resume and experiences, then we setup a phone interview with an engineer a week after our initial call. Engineer was a nice person and after introductions we jumped into a problem that i had to solve on a collaborative coding site, i was able to solve the problem and then he gave me a design problem, i thought i did okay in design problem as well.
After 1 hour of interview he seemed alright with my skills and told me that i would be contacted by the recruiter for next steps.
I waited a few days but didn't get any feedback, i sent an email to inquire and was told by recruiter that he would get back to me in a couple of days. And after that i was ghosted. Really not a good interview process to not let the candidate know how they did or if they would be moving forward or just rejected for some reason.
Thank you for sharing your honest feedback about your interview experience. Candidate experience is a priority of our recruiting team, and we apologize that you did not receive appropriate follow-up.
Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Asana
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.
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
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.
