Asana·Software Engineer

Asana Software Engineer interview experience

No offer

Easy

Negative

United StatesPosted Jun 2020 · Candidate report, summarized by Dataford

My experience turned negative fast because the evaluation criteria felt mismatched to what was being asked.

I went into a stage with two technical components: a data structures and algorithms problem that was essentially LeetCode medium and something I completed fairly quickly, and then an open-ended OOP design question. I could see what I thought the design should do, but the interviewer had a very strict sense of how the solution needed to look.

During the OOP portion, the interviewer kept stopping me when they weren’t aligned with my approach, and then they even changed the question midway because they believed my design wouldn’t work for a different function than what had initially been asked.

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Asana Software Engineer interview guideThe full process, round by round, with the question bank Practice Software Engineer interview questionsReal questions from this role across companies All Asana interview guidesEvery role we cover at this company