The initial HM screen was followed by a technical phone screen, which included a mix of LeetCode medium problems, object-oriented programming (OOP), and general problem-solving. The interviewer was pleasant, and I left thinking that this seemed like a decent company to work for.
The on-site interview, however, was a different story. Every interviewer asked very contrived questions and expected very specific answers. They were very rigid and thwarted any attempts at collaboration, despite the Asana interview guide stating it would be a "collaborative" interview.
Their concept of "System Design" is way off (in the context of tech interviews). Do not expect to design a product or distributed system. Expect an OOP and/or API specification question that has a very specific answer.
A mix of ones provided in other reviews.
The following metrics were computed from 9 interview experiences for the Asana Software Engineer role in Vancouver, British Columbia.
Asana's interview process for their Software Engineer roles in Vancouver, British Columbia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Asana's Software Engineer interview process in Vancouver, British Columbia.