Asana Software Engineer coding interview with no feedback before rejection

Asana·Software Engineer·Reported Jun 2026
Technical ScreenRejectedMedium

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 dragged on. After the interviewer went on sick leave, I waited several weeks before a rejection email finally arrived.

The rejection itself didn’t bother me. I understood that it happens. The lack of feedback and the long silence made the experience harder to sit with. What threw me off most was that the preparation materials emphasized collaboration and communication, while the actual session felt misaligned with those expectations.

Location: Poland. Overall feedback: Negative. Offer status: No offer.

Published

Curated and edited by PracHub

Discussion

Sign in to join the discussion. The author is notified of every comment.

Loading comments…

Interview at a glance

Company
Asana
Role
Software Engineer
Rounds
Technical Screen
Outcome
Rejected
Difficulty
Medium
Date
Reported Jun 2026

Real Asana interview experiences

First-hand reports from Asana candidates — the rounds, the questions they were asked, and how it went.

All 10 Asana interview experiences