Asana software engineer candidates report recruiter contact, coding assessment and phone stages, followed by onsite coding, object-oriented design, system design, and behavioral conversations.
$189K
Avg. Base Comp
$265K
Avg. Total Comp
6 rounds
Typical Rounds
3-6 weeks
Process Length
Asana software engineer interviews reported here center on coding clarity alongside design judgment. One candidate described a six-round path from recruiter call through an online assessment and phone interview to a three-interview onsite. Another candidate reported a CodeSignal-style screen, coding, and an onsite that included system design and behavioral discussions. Prepare to explain your implementation choices and time complexity, not just reach an answer.
Coding reports include familiar algorithmic patterns: a kth-closest-point prompt, a “very hungry rabbit” problem, and LeetCode-medium-style work. A senior candidate also described a 90-minute solo coding exercise followed by a discussion of improvements, so it is worth practicing how to state an initial approach, make tradeoffs visible, and revise it when prompted.
The onsite material is broader than algorithms. Candidates report object-oriented or low-level-design exercises, including writing classes and methods, plus system design. One report also mentioned a security-related discussion, while another described bash/CLI questions in a systems round. Hiring-manager conversations focused on project deep dives, work situations, and mentorship. The available reports do not establish a universal format, but they consistently point to a mix of coding, design, and behavioral communication.
Synthesized from 3 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Asana process.
I went through six rounds from the recruiter phone call to a rejection after the onsite. The process started with a recruiter chat, then an online assessment, then a phone interview, followed by a final onsite with three interviews back to back. The onsite included object-oriented design, coding, and system design rounds. The interview process felt fair, and there were plenty of resources available online.
Questions asked: Design Jigsaw.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Asana
How would you calculate daily user retention and rolling activity for Lime's app using login data?
| Question | |
|---|---|
| Reservoir Sampling Stream | |
| Binary Tree Validation | |
| A Simpler KNN From Scratch | |
| Client Solution Pushback | |
| Ranking Metrics | |
| Friend Requests Down | |
| Newsfeed Model | |
| Your Strengths and Weaknesses | |
| Evaluate News | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Comments Histogram | |
| Upsell Transactions | |
| Raining in Seattle | |
| String Shift | |
| Customer Orders | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report beginning with a recruiter chat or call, followed by an online or CodeSignal-style assessment and, in one account, a phone interview. A senior-level report described a 30-minute recruiter call and a one-hour screen with a LeetCode-medium problem plus a brief discussion of an Asana feature.
Reported coding work used recognizable interview patterns, including kth closest point and the “very hungry rabbit” problem. One candidate described a 90-minute solo coding round followed by a discussion of solution improvements, so candidates may need to articulate tradeoffs after implementing an initial solution.
Candidates report object-oriented design during the onsite. One account describes a two-hour session writing classes and methods and explaining logic and time complexity; another names an OOP design question involving a well-known game. Practice may therefore combine implementation with design explanation.
Onsite reports include system design and a hiring-manager behavioral conversation. One candidate also encountered a security-related round, while a senior candidate reported bash/CLI questions with a short system-design discussion. Behavioral prompts reportedly covered project experience, work situations, and mentorship.
