Real, anonymous reports from people who interviewed for Software Engineer at Asana, newest first and distilled into what to expect across the loop.
I hit mostly an early-stage stop in the process, and what stood out was how long it took to hear back (or how thin the feedback was) after my initial technical attempt.
I went through a fairly standard Asana software engineering loop over a few rounds, with mostly LeetCode-style questions and an onsite that mixed technical and behavioral.
The interview process typically begins with a recruiter screen that covers background, motivations, and role fit, but candidates often report issues with scheduling and communication, leading to a lack of clarity and engagement early on.
Candidates can expect a technical screen focused on LeetCode-style problems, often including a mix of algorithmic questions and design discussions, with varying levels of engagement from interviewers.
The onsite typically involves multiple rounds that include coding, system design, and behavioral interviews, but the format can feel rigid and may not align with the collaborative atmosphere advertised by the company.
Candidates frequently report receiving minimal feedback after interviews, with many experiencing vague rejection messages or prolonged waiting periods for closure, which can lead to frustration.
The technical rounds are often perceived as challenging, with candidates needing to prepare for a mix of coding, design, and system thinking under time constraints, which can lead to performance pressure.
Candidates have noted significant issues with the reliability of the interview process, including missed schedules and unclear communication, which can overshadow their technical performance.