I applied through college or university. The process took 2 days. I interviewed at Asana in Feb 2018
Interview
Did an easy coding challenge (about matrices). Then had a first round technical phone interview. The first round interview was super weird. They didn't have you code, instead they had you like partially code on a google doc, but also talk through a question. The google doc just made it awkward and unclear how much you should be writing. Then the second question was a design question about a popular iphone game. The problem with this question was that the game chosen was relatively simple and it was unclear what direction the interviewer wanted you to take. It would be a good whiteboard question but it was far too awkward for a phone interview.
Interview questions [1]
Question 1
LRU Cache, How would you divide work a project between two people?
Thank you for taking the time to write a review of your interview experience. We're sad to hear you had a negative experience and have passed your feedback on to our recruiting team. We're constantly iterating on our interview process, so feedback like yours is really helpful as we strive to improve our candidate experience.
Other Software Engineer Interview Reviews for Asana
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.
I applied online. I interviewed at Asana in May 2026
Interview
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.
Interview questions [1]
Question 1
Tell me about a time you experienced mentorship, as a mentor or a mentee