Taro Logo

Software Engineer Interview Experience

June 2, 2020
Negative ExperienceNo Offer

Process

I originally really wanted to work here, but now my view on the company has changed.

This is my first interview review, and I'm doing it to express the negative interview experience I had. The evaluation criteria make no sense.

  1. DS&A problem: LC Medium (Completed in 15-20 minutes with optimal complexity.)

  2. Open-ended OOP design question.

The interviewer has a very strict idea of how they want to do things. They will constantly stop you and ask questions when they don't agree with your design. The interviewer changed the question midway because they thought my design would not work for a different function, even though that wasn't initially asked for.

I don't agree with asking OOP design questions that are connected to a very specific game. Many people are not familiar enough with a game to deliver the desired representation in 30 minutes.

Unless you spend your time modeling and recreating different kinds of games, you will not pass here. If you have experience playing the games they ask about, you will have a better chance just from familiarity alone.

I doubt these engineers can pass their own criteria for design questions without knowing the problem beforehand.

Questions

LC medium

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