I originally really wanted to work here, but now my view on the company has changed.
This is my first interview review and I'm doing it to express the negative interview experience I had. The evaluation criteria makes no sense.
1. DS&A problem.
LC Medium (Completed in 15-20min with optimal complexity.)
2. Open ended oop design question .
The interviewer has a very strict idea of how they want to do things. They will constantly stop you and ask questions when they don't agree with your design. The interviewer changed the question on me midway because they thought my design would not work for a different function even though it that wasn't initially asked for.
I don't agree with asking oop design questions that are connected to a very specific game. Many people are not familiar enough with a game to deliver the desired representation in 30 minutes.
Unless you spend your time modeling and recreating different kinds of games, you will not pass here. If you have experience playing with the games they ask, you will have a better chance just from familiarity alone.
I doubt these engineers can pass their own criteria for design questions without knowing the problem beforehand.
Thank you for taking the time to interview at Asana. We apologize that your interview experience was not a positive one, and we appreciate you sharing your feedback.
Other Software Engineer Interview Reviews for Asana
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
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.
