Asana Interview Experiences

11 results

• 

  Design-Heavy Loop After Lots of Peer Mock InterviewsAsana · Software Engineer · Other · Sep 2026

  I'm a mid-level engineer with roughly 3-4 years of experience, almost all of it in backend work, mostly distributed systems at fintech companies. I went to a state school and did just one internship during college. Asana hands candidates a study guide, and I'd tell anyone to work through it, even if they're interviewing somewhere else. Most of my own studying was the video lessons and quizzes fro…

• 

  Asana Account Executive interview with six stages and a final presentationAsana · Account Executive · Other · Jun 2026

  Rejected

  I went through an intense, multi-step process that felt excessive for the role. After speaking with a recruiter, I had several interview rounds with detailed technical questions. The process stretched across six stages, ending with a 45-minute presentation that required a lot of preparation on top of everything else. I passed every stage with positive feedback and felt that the conversations were…

• 

  Asana Software Engineer coding interview with no feedback before rejectionAsana · Software Engineer · Technical Screen · Jun 2026

  Rejected

  I started with an initial screening that left me genuinely excited about the opportunity. The technical part didn’t match what I expected from the preparation materials. Instead of feeling like a collaborative back-and-forth, the interaction was noticeably less engaging, and the interviewer’s involvement felt minimal. I didn’t receive feedback after the coding interview, so the uncertainty dragge…

• 

  Asana Software Engineer interview with a referralAsana · Software Engineer · HR Screen · Jun 2026

  My process was short and ended quickly. It started with an HR introduction call focused on standard resume and experience questions, along with how my background fit the role. It didn't feel like much of an exploration of my strengths or working style. The call felt more like someone moving through a checklist. Because I had a referral, the conversation also felt somewhat ceremonial. After the HR…

• 

  Asana Software Engineer interview with a specific systems modeling problemAsana · Software Engineer · Technical Screen · Mar 2026

  Rejected

  The overall experience felt professional, and most of the rounds ran cleanly. One interviewer came across as standoffish, which threw me off more than anything technical, but the logistics and tone were mostly well handled. The part I struggled with was the systems interview. It involved a very specific modeling problem that didn't resemble the general patterns I expected. Unless I'd previously b…

• 

  Asana Software Engineer interview: CodeSignal, coding round, and onsiteAsana · Software Engineer · Online Assessment · Mar 2026

  Rejected

  The process started with a CodeSignal assessment, followed by a dedicated coding round. After that, I attended an onsite that included system design and a behavioral interview, all in a fairly standard sequence. The questions leaned toward LeetCode, but they didn't feel too extreme. Many covered the kinds of problems I could find online with the right search terms. I didn't move forward, although…

• 

  Asana Software Engineer interview: six-step Salesforce-focused processAsana · Software Engineer · Mar 2026

  My interviews followed a longer, structured process with six steps and plenty of feedback between rounds. Everyone I spoke with was professional and attentive, and the process never felt chaotic or improvised. The technical portion was for a role related to Salesforce development. The topics were what I expected: async processes, bulkification, trigger contexts, and the relevant syntax. The round…

• 

  Asana Software Engineer interview with repeated reschedulingAsana · Software Engineer · HR Screen · Feb 2026

  From the beginning, the scheduling and communication felt unreliable. I had multiple rounds where steps seemed to be skipped without much explanation, and I kept waiting for the next stage to move forward. Several interviews also had to be rescheduled because the interviewers didn't show up at the scheduled times. One HR conversation felt mostly like a checklist. The questions seemed to come from…

• 

  Two Onsites, Rejected Over "Communication Clarity"Asana · Software Engineer · Onsite · Feb 2026

  Rejected

  Round 1: Given two code snippets and asked what they do, plus their time/space complexity Jigsaw Puzzle design — the forum said pseudocode was fine, but the interviewer still made me pick a language and write actual code Round 2 (split across two days): Ascii Printer: 1 hour of coding (the last 45 minutes the interviewer asks questions about your code). A handful of functions to implement. A 10x6…

• 

  Asana Software Engineer interview with roughly six roundsAsana · Software Engineer · Jan 2026

  Rejected

  My interview process felt well organized overall and took place over about two weeks, with roughly six rounds. The interviewers were friendly and collaborative, and the questions generally matched what I had seen mentioned elsewhere, including coding and design topics related to the role. I received a rejection with a list of areas to improve. That was discouraging because when there are several…

• 

  Asana Software Engineer interview: two-hour OOP coding sessionAsana · Software Engineer · Technical Screen · Jan 2026

  Offer

  My process started with a coding round, followed by a system design round, and then security became part of the evaluation too. After that, I had a longer, two-hour coding session focused on OOP. That coding block was less about solving one algorithm and more about writing classes and methods, then explaining my logic and time complexity. I had to talk through my thinking as I worked, not just pr…