Taro Logo

Software Engineer Interview Experience

November 1, 2018
Neutral ExperienceNo Offer

Process

The interview process began with a phone screening by a software engineering manager.

Following that, I completed a timed, LeetCode-style "take-home" screening.

The next day, I was contacted to advance to the next phase. Since I am not located near the company's San Francisco headquarters, the "in-person" portion of the process was conducted via video interview.

This consisted of two one-hour interviews with different interviewers, totaling two hours. The interviewers, who were engineers, asked LeetCode-style algorithm questions and one design-oriented question.

These were completed using a Google Doc, where I could write pseudocode while explaining my thought process. I encountered some difficulties, but the interviewers were very helpful in guiding me to complete and optimize my solutions. A few days later, I received a standardized email stating that they had decided not to continue the interview process with me.

I would recommend ensuring you are very familiar with LeetCode-style questions if you interview here, as this comprised the majority of the process. Essentially, there were no questions about my past experience or soft skills.

Questions

Algo questions

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

9%
Pass 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

Positive45%
Neutral19%
Negative36%

Candidates reported having mixed feelings for Asana's Software Engineer interview process in United States.

Asana Work Experiences