Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

10 stories

Likes earn the author +10 XP for the first 3 likes each day

AsanaSoftware Engineer
Reported Jun 2026

Asana Software Engineer interview with a referral

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…

HR Screen0
AsanaAccount Executive
Reported Jun 2026

Asana Account Executive interview with six stages and a final presentation

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…

RejectedOther0
AsanaSoftware Engineer
Reported Jun 2026

Asana Software Engineer coding interview with no feedback before rejection

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…

RejectedTechnical Screen0
AsanaSoftware Engineer
Reported Mar 2026

Asana Software Engineer interview with a specific systems modeling problem

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…

RejectedTechnical Screen0
AsanaSoftware Engineer
Reported Mar 2026

Asana Software Engineer interview: six-step Salesforce-focused process

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…

0
AsanaSoftware Engineer
Reported Mar 2026

Asana Software Engineer interview: CodeSignal, coding round, and onsite

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…

RejectedOnline Assessment0
AsanaSoftware Engineer
Feb 2026

Two Onsites, Rejected Over "Communication Clarity"

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…

RejectedOnsite0
AsanaSoftware Engineer
Reported Feb 2026

Asana Software Engineer interview with repeated rescheduling

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…

HR Screen0
AsanaSoftware Engineer
Reported Jan 2026

Asana Software Engineer interview with roughly six rounds

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…

Rejected0
AsanaSoftware Engineer
Reported Jan 2026

Asana Software Engineer interview: two-hour OOP coding session

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…

OfferTechnical Screen0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP