Asana logo

Candidate-reported interview insights

Asana Software Engineer interviews, decoded.

Explore commonly reported questions, interview rounds, difficulty, duration, and candidate experiences for the Software Engineer role at Asana.

4.1 rating Enterprise Software & Network Solutions

Interview overview

Difficulty

Average

Average rounds

2.8

Average duration

~44 days

Difficulty and candidate experience

Interview difficulty

easy9.2%
average59.9%
difficult30.9%

Candidate experience

neutral18.8%
positive55.1%
negative26.1%

Candidate-reported interview process

It was a pretty simple process. Started with a Codesignal, then a coding interview, and finally an onsite interview which included a system design question and a behavioral question. The questions were mostly LeetCode style and pretty easy to find online.

The interview process was generally good, though one interviewer was a bit off. The Systems interview was tough, focusing on a niche modeling problem that's hard to solve without prior experience, which felt surprising for a mid-level role. They didn't test infrastructure knowledge, which is unusual. The coding interviews were good, with a focus on LLD and simple Leetcode problems where understanding patterns is key. The Hiring Manager interview was impressive, with probing questions that gave a positive impression of the company and team, even though I didn't pass.

So first there was a coding round and a system design round. Then a security related round. After that, I had a 2 hour coding round for an OOP coding where I was expected to write classes and methods and explain the logic and time complexity. Lastly, the Hiring Manager round for project deep dives.

Interview question formats

Coding37.4%
Technical30%
System Design17.2%
Behavioral13.8%
Other1%

Ready to prepare for Asana?

Practice technical, system design, and behavioral questions with Zitlee.

Interview information is based on candidate reports and may not represent the current official hiring process of Asana.