Ho presentato la mia candidatura online. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Asana nel mese di nov 2018
Colloquio
First was a phone screening with a software engineering manager, then a “take-home” screening which was a leetcode style problem which was timed. After that, I was contacted the next day to move on to the next phase and we set up a video interview (I am not located near the companies HQ in San Francisco, so this was the “in person” portion of the process). The video interview was one hour each with two different interviewers, so two hours total. The interviewers were engineers and the interview consisted of Leetcode style algorithm questions and one more design oriented question. These were done over a google doc page where I could write out pseudo code while I talked my way through the problem. I got stuck on some and the interviewers were very nice in trying to guide me to complete and optimize my solutions. A few days later I received a standardized email that they decided not to continue the interview process with me. I would say make sure you are very familiar with leetcode style questions if you interview here since that was pretty much what the whole interview was based on. Basically no questions about my past experience or soft skills.
Thank you for taking the time to share this feedback with us. The skills and experiences that you have are important to our team, and we apologize that this was not reflected in the interview. Thank you for interviewing at Asana and sharing your experience.
Esperienza neutra
Colloquio nella media
Candidatura
Ho sostenuto un colloquio presso Asana (San Francisco, CA)
Colloquio
HR intro call was typical questions about resume, experience, and goal fit. I didn't get pass this round of the process unfortunately. Seemed like it was a formality call since I had a referral.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso Asana nel mese di mag 2026
Colloquio
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.
Ho sostenuto un colloquio presso Asana nel mese di feb 2026
Colloquio
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.
Domande di colloquio [1]
Domanda 1
Tell me about a time you experienced mentorship, as a mentor or a mentee