TheJobsMapRole not stated
Not selectedunknown. 1 round. Shared by Jormundir on hn, 2016-03-29
- 1Onsite interviewsTechnicalOne database problem followed by several academic algorithm questions.Covered: Database design, Algorithms
Asana interview questions
From 9 candidate accounts, updated Oct 12, 2026
- Candidate accounts
- 9
- Rounds on average
- 1.6
- Fewest and most rounds
- 1 to 3
- Open roles at Asana
- 102
How the loop works
This guide draws on 9 first-hand interview accounts from Hacker News. Candidates describe about 2 rounds on average, most often a take-home task, a phone screen and technical interviews.
These 9 writeups cover data, software engineering roles. All of them were posted under a forum handle, so we could not verify the authors’ identities.
Interview experiences at Asana
Product Engineer
Outcome not sharedunknown. 1 round. Shared by colinsidoti on hn, 2012-01-20
- 1InterviewsFinalCandidate came away without a clear idea of what they would actually be building.
What Asana is hiring for now
102 open roles in our index. Advertised pay floors run $164k to $248k (median $202k, from 45 postings that state pay).
Most-posted roles
- Developer Advocate3
- Corporate Account Executive3
- GM, Product - Command2
- Corporate Account Executive - Dutch Speaking2
- Forward Deployed Engineer, Command by Asana2
- Lead Product Manager, Enterprise Services Management2
Top locations
- San Francisco28
- Vancouver19
- Warsaw17
- New York City9
- Dublin6
Asana interviews: FAQ
- What is the interview process like at Asana?
- This guide draws on 9 first-hand interview accounts from Hacker News. Candidates describe about 2 rounds on average, most often a take-home task, a phone screen and technical interviews.
- What topics does Asana test in interviews?
- Commonly reported topics include Algorithms, SQL, Feature importance, Statistical modeling, Database design, News feed ranking.
These guides summarize public, first-hand interview experiences shared by candidates. They describe the shape of each loop and the topics that came up, not a leaked question bank, and every experience links back to its original source. Processes change often. Treat this as directional prep, not a script.