I applied online. The process took 2 weeks. I interviewed at Asana in Oct 2019
Interview
The process started with their coding challenge (hungry rabbit) which focuses primarily on code cleanliness and good practices. Quickly afterwards I was invited to phone interview with an engineer. The interview was 1 hour, over Google Docs. The focus was on one algorithm question, and then one OOP design question. I've noticed that they have a bank of questions, which is good for more accurately assessing different candidates. Unfortunately, I had a pretty difficult (or at least, novel) OOP question which I got stuck on. My interviewer was nice, but not overly helpful with providing hints or guidance. Overall, the process was fast, personal, and actual specific feedback is provided with the rejection. I'll be applying again in the future.
Design a jigsaw puzzle algorithm, given a Piece class, a Side class containing sideTypes, and a helper function which returns whether or not two pieces are a match
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