Asana Software Engineer interviews, as candidates describe them, mix LeetCode-style coding with object-oriented and low-level design, plus behavioral conversations. Reported loops run from a recruiter call to a multi-round onsite.
$200K
Avg. Base Comp
$290K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates describing Asana's Software Engineer interviews often point to object-oriented and low-level design as a distinctive part of the loop. One candidate who received an offer described a two-hour OOP coding session where they wrote classes and methods and explained both the logic and the time complexity. Another reported a Design Jigsaw question in an onsite that also included coding and system design rounds.
The coding is described as familiar. Reports mention LeetCode-focused problems, the classic "very hungry rabbit" problem, returning the kth closest point, and a CodeSignal-style screen. One candidate said the bar felt like pattern recognition and clean explanation rather than obscure tricks. Another solved a data structures problem and an object-oriented design problem in an early screen, with Python preferred and pseudo-code allowed for one of them. Not every loop matched that pattern: one candidate faced a very hard algorithmic question with a 30-minute limit after expecting system design.
Behavioral rounds lean on project deep dives. One hiring manager asked about a time the candidate experienced mentorship, either as a mentor or a mentee, and that candidate called it one of the better parts of the process. The same candidate also reported a security-related round, so a security-flavored discussion is worth a little prep.
Outcomes and communication vary. Most reports in this set ended without an offer, and some candidates mention a stalled process or a rejection with no feedback. Ask your recruiter exactly what each round covers, since one candidate said the recruiter's prep email did not match the onsite.
Synthesized from 16 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.
Seems like it went relatively well at the time. The phone screening happened fast—recruiter reached out almost immediately after I submitted my CV—and they were friendly, walking me through my background and Asana's values before moving me forward. First technical round was online with my camera off. They gave me two problems: one on data structures and algorithms, the other on object-oriented design. I could use any language (Python was the preference), and for one problem they were okay with pseudo-code. Nothing felt impossibly hard, just solid technical screening.
I thought I'd done fine. But then the process just stalled. No status update for a while, so I reached out asking where things stood. After a pretty long delay, they came back with a rejection—no feedback, no follow-up call they'd initially mentioned, just a no. The frustrating part is how sudden it felt given how positive things seemed initially. I still don't actually know what derailed it or where I went wrong.
The process itself is well-organized: quick scheduling, clear expectations, flexible format. But there's definitely a gap between how smooth the interviews feel and what happens after. Communication post-interview isn't guaranteed, and you won't necessarily get feedback even if they promised it. Be proactive about chasing status yourself rather than waiting for them to circle back.
Prep tip from this candidate
Prepare for data structures (especially arrays and sorting patterns) and OOD design problems tested back-to-back in a single online session. The shift between algorithmic and design thinking happens fast, so drill both problem types together if possible.
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 | |
|---|---|
| Friend Requests Down | |
| Ranking Metrics | |
| Reservoir Sampling Stream | |
| Newsfeed Model | |
| Evaluate News | |
| Binary Tree Validation | |
| Client Solution Pushback | |
| A Simpler KNN From Scratch | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top 3 Users | |
| Random SQL Sample | |
| Find the Missing Number | |
| Upsell Transactions | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Largest Salary by Department | |
| Size of Joins | |
| Scrambled Tickets | |
| Prime to N | |
| String Shift | |
| Find Bigrams | |
| Comments Histogram |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter conversation, about 30 minutes in one report, covering their background. One recruiter also walked through Asana's values. Some candidates received a prep guide or prep email from the recruiter, so it is worth asking what each later round will cover.
Reports describe a CodeSignal-style screen, an online assessment, or a roughly one-hour screening. Candidates mention a LeetCode medium problem paired with a quick design discussion, or a data structures problem alongside an object-oriented design problem. One candidate's screen instead focused on system design for a well-known platform.
Candidates report LeetCode-style problems such as kth closest point and the very hungry rabbit problem. One senior candidate had a 90-minute solo coding session building out features, then discussed improvements with the interviewers. Another said a very hard timed problem was a surprise, so expect some variation between loops.
Several candidates describe object-oriented or low-level design rounds. Reported prompts include Design Jigsaw, an OOP-style design of a famous game, and a two-hour OOP coding session writing classes and methods with complexity explanations. Some loops also included more classic system design, so prepare for both.
Candidates report hiring manager rounds built around project deep dives and work-situation questions, including one about mentorship as a mentor or a mentee. One candidate described this conversation as thoughtful rather than scripted. Prepare concrete project stories with your specific impact and decisions.
Most reports here ended in no offer, while one candidate accepted an offer. Candidates describe stalled processes, long delays before a decision, and rejections without feedback. It may help to follow up on status with your recruiter rather than waiting for the next message.
