Real, anonymous reports from people who interviewed for Software Engineer at Asana, newest first and distilled into what to expect across the loop.
After a recruiter call, I had the first technical conversations about a week later. The format felt pretty interactive: the interviewer guided the flow in a way that kept things moving and made it clear what they were looking for. I worked through one LeetCode-style problem and then a second question that was more game-like in presentation.
My process was short and ended quickly. I started with an HR intro call where the discussion centered on typical resume and experience questions, plus how my background fit the role. It didn’t feel like much of an exploration of my strengths or working style—it was more like the call followed a checklist.
The interview process typically consists of multiple stages, starting with a recruiter call, followed by technical assessments and onsite interviews. Candidates reported a range of experiences regarding the organization and pacing of these rounds, with some noting a smooth progression while others faced scheduling issues.
Candidates can expect a mix of coding challenges, often in the style of LeetCode problems, focusing on data structures and algorithms. The technical interviews may also include object-oriented design questions, and some candidates found the coding questions to be manageable while others felt they were misaligned with their preparation.
Onsite interviews typically include system design questions and behavioral assessments, with a focus on communication and collaboration during problem-solving. However, some candidates reported discrepancies between the expected collaborative approach and the actual interview dynamics, which felt rigid or contrived.
Feedback during the interview process varies, with some candidates receiving detailed notes on areas for improvement while others experienced a lack of feedback or clarity on their performance. Many expressed a desire for more transparency regarding their progress and outcomes.
Overall candidate experiences ranged from positive and engaging interactions with interviewers to feelings of frustration due to scheduling issues or perceived lack of interest from interviewers. Many candidates appreciated a friendly tone during interviews, which contributed to a more comfortable environment.
Candidates noted the importance of thorough preparation, especially regarding the technical content and interview format. Some felt misled by the preparation materials, which emphasized collaboration but did not align with the actual interview experience, leading to confusion and disappointment.