Real, anonymous reports from people who interviewed for Software Engineer at Asana Spa, newest first and distilled into what to expect across the loop.
Get your personalized Asana Spa Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
I started with an initial stage that felt promising, and then the process dragged longer than it needed to. After the interview, I realized I’d effectively fallen through the cracks in their system, so I had to chase for any status update.
There wasn’t a clear communication cadence. I’d been told I’d hear back within a timeframe, but the delay kept stretching, and when a response finally arrived, it was essentially that they were no longer interested. What hurt most was the lack of any promised feedback conversation and the absence of any meaningful feedback at all—just a generic closeout.
6 months ago
Difficult Neutral Canada
I went through a multi-round process that felt professionally run overall, but the technical structure had a couple of surprises. Most of the interviews were conducted in a standoff-free, respectful way, and the coding rounds themselves felt solid—good-quality problems where discussion mattered more than memorization.
What threw me off was a “systems” style modeling question that was unusually specific. I didn’t have the exact background to recognize the pattern they were looking for, and it made it harder to produce a decent solution in the time. I was also struck by what didn’t show up: infrastructure knowledge wasn’t really tested in that systems-focused round.
7 months ago
Difficult Positive San Francisco, CA
My process was heavy on structured technical rounds. It started with coding and system design, then moved into a dedicated security-related interview.…
7 months ago
Average Neutral Vancouver, BC
My experience started with a process that felt fairly organized and transparent. I was given materials ahead of time that helped me understand what to…
8 months ago
Easy Negative San Francisco, CA
The part that defined my experience wasn’t the interviews themselves—it was how the recruiting pipeline was managed. Throughout the scheduling and pro…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruitment Process & Communication
Candidates reported mixed experiences with the recruitment process, often highlighting issues with communication and scheduling. Many felt that follow-ups were lacking, leading to frustration and uncertainty about their application status.
CommunicationSchedulingTransparency
Technical Interview Structure
The technical interviews typically included a mix of coding challenges and system design questions, with a strong emphasis on algorithm and data structure problems. Candidates noted that the coding rounds were often LeetCode-style, requiring both problem-solving skills and clear communication of thought processes.
CodingSystem DesignLeetCode
Onsite Interview Experience
Onsite interviews were described as lengthy and intensive, often lasting several hours and covering multiple rounds. While some candidates appreciated the structured approach, others found the experience exhausting and felt that the atmosphere could be combative rather than collaborative.
OnsiteMultiple RoundsAtmosphere
Behavioral Interviews
Behavioral interviews were generally well-received, with candidates noting that interviewers focused on understanding past experiences and decision-making processes. The tone was often supportive, contributing positively to the overall experience.
BehavioralSupportivePast Experiences
Feedback & Follow-Up
Many candidates expressed disappointment over the lack of meaningful feedback after interviews, with some reporting that they received generic responses or no feedback at all. This contributed to a sense of dissatisfaction with the overall process.
FeedbackFollow-UpSatisfaction
Overall Difficulty & Expectations
Candidates found the overall difficulty of the process to be high, with some struggling to meet the expectations set during initial communications. The mismatch between expected and actual interview content led to confusion and stress for several candidates.