I applied online. I interviewed at Asana (Vancouver, BC)
Interview
Call with a recruiter who was nice but the process was quite robotic otherwise as all emails you receive are scheduled templated send-outs.
Coding test was the same hungry rabbit question everyone else got. I didn't get a response back after completing the test, not even a rejection. I didn't do well because I am a self-taught developer who's never needed to learn how to traverse a matrix. Very algorithm-focused coding test that is irrelevant for a SaaS product development role where the product is a CRUD app, but if you did CS and are good at puzzles, you should be able to complete it.
I think Asana could benefit from more diversity in hiring and maybe be open-minded to hiring more product-oriented engineers with better attention to detail as their product has a lot of user experience issues and front-end bugs, and maybe not focus on testing the ability for a developer to complete algorithm puzzles unrelated to the role.
Interview questions [1]
Question 1
Hungry rabbit gets plopped into the middle of a garden. If there is no real middle, find the most-middle square with the most carrots. From that point find the next square with the most carrots. Continue this pattern until you reach an edge of the garden. Sum up all the carrots eaten along the way.
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