Asana Software Engineer interview: two-hour OOP coding session

Asana·Software Engineer·Reported Jan 2026
Technical ScreenOtherOfferHard

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 produce code.

The final step was a hiring manager round with a deeper discussion of specific projects from my background. By the end, I had covered design, security, and OOP implementation, so the evaluation felt comprehensive, and I got an offer.

Location: San Francisco, CA. Overall feedback: Positive. Offer status: Got 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 → Other
Outcome
Offer
Difficulty
Hard
Date
Reported Jan 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