Process
Phone Screening with Recruiter, then Phone Call with Engineer.
The phone call was better than with other companies. They didn't use LeetCode; instead, they provided snippets of code and asked me to go through them in detail. I made mistakes on a few snippets, followed by a design question.
It felt very conversational, which was nice.
I didn't advance to the next rounds, so I guess they expected perfection in these steps. Although I felt an hour wasn't enough to go through everything, my mistake was taking too long on the introduction. I should try to speed through that part to get more time.
Questions
Jigsaw Puzzle, asking for implementation.
Was this helpful?
Interview Statistics
The following metrics were computed from 100 interview experiences for the Asana Software Engineer role in United States.
Success Rate
Asana's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Asana's Software Engineer interview process in United States.
Asana Work Experiences
- 5.0Great Place, Huge CompanySoftware Engineer • Current EmployeeSan Francisco, California, United StatesAugust 28, 2024Pros: I enjoy working there; it's great.Cons: It's a very large company.
- 5.0Great people and a great companySoftware Engineer • Current EmployeeSan Francisco, California, United StatesFebruary 19, 2016Pros: It is very fun to work with the smart people at Asana. I have learned a lot from the great team here.Cons: Cannot think of any so far.
- 5.0A great place to work and growSoftware Engineer • Current EmployeeSan Francisco, California, United StatesMarch 23, 2015Pros: Very intentional and thoughtful culture. I trust the leadership and I feel comfortable raising issues when I have them. Asana focuses a lot on personal growth. Coworkers are smart, hard-working, and enjoyable to spend time with.Cons: The backend is written in JavaScript, and in an in-house framework that ended up being essentially a dead end. As a result, there's a lot of technical debt that needs to get paid off.
Asana Interview Questions
