The interview was supposed to be for an hour, but after waiting for the shadow interviewer and introductions, I only had 45 minutes.
My advice to you: don't waste time on introductions (about yourself).
I had 45 minutes to solve two problems. One was a LeetCode easy to medium problem, and the other was a code design pattern question.
I was given 15 minutes to solve the LeetCode question. It was more of a conversation, and I was asked to write in pseudocode, but I wasn't really sure what pseudocode format they were expecting.
The second question was more of a code design question based on a game. If you have never played the game or don't have context, I don't think you will be able to solve the problem. Understanding the rules, then coming up with a solution requires too many things to be in play. I have 11 years of experience and have taken a lot of interviews in my career; this was way too rushed. Luck plays a bigger role here.
Overall, I am thankful for the unique experience. It will definitely help with future interviews.
On LeetCode, easy to medium problems based on arrays.
One code design pattern, method signatures, etc., based on a game.
The following metrics were computed from 1 interview experience for the Asana Software Developer role in Vancouver, British Columbia.
Asana's interview process for their Software Developer roles in Vancouver, British Columbia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Asana's Software Developer interview process in Vancouver, British Columbia.