The first step was a coding challenge, identical to what many others have posted on Glassdoor (e.g., a "hungry rabbit navigating a matrix"). I anticipated this would be the challenge and spent time beforehand coding up a solution. Once the challenge began, I more or less just copy-pasted my code in.

Afterwards, the recruiter contacted me to schedule a 1-hour phone interview with an engineer. The engineer wasn't very warm. He sounded almost arrogant and full of himself—not very friendly nor helpful during the interview. He asked very generic algorithm questions (e.g., "check if a binary tree is a binary search tree"). The second question was about designing a chess game using object-oriented principles.

The recruiter contacted me again a few days later, stating I didn't move forward. Overall, the process left a bad taste. It didn't really get me excited about working at Asana, and I didn't feel the company was particularly warm. It really just seems they have engineers pull questions from "Cracking the Coding Interview" and throw them at as many candidates as they can.

How do you check if a binary tree is a BST?

How would you design a chess game?

What classes and objects would you use?

What methods would they have?