The first round was an Online Assessment (OA) from CodeSignal.
The second round was conducted on CodeSignal. Expect to read some code snippets and discuss their complexity. Try to finish this part quickly, as you will then move on to an OOP design question. The interviewer will try to keep you focused on the right solution, which feels like collaboration.
Onsite interviews include three rounds:
For the 2-hour coding session, the interviewer lets you ask questions and then logs out, allowing you to work alone for 70 minutes. After that, they return to go over your implementation and ask questions.
For the system design rounds, expect some LeetCode-style coding and OOP design. Be ready to communicate clearly and think out loud. I actually had a lot of fun and learned something new during this round; it was very practical.
Overall, the people I interacted with were engaging and smart.
The onsite interviews have built-in 15-minute breaks between rounds. Additionally, there is a 45-minute session to talk to an engineer and learn more about the company.
My recruiter was willing to give me some high-level feedback, which is something not many companies do.
I would say that I had a pretty good experience with Asana.
The following metrics were computed from 100 interview experiences for the Asana Software Engineer role in United States.
Asana's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Asana's Software Engineer interview process in United States.