Asana·Software Engineer·Onsite - System Design / Architecture
- Design a collaborative todo list application.
“This sounds straightforward until you start thinking about real-time sync between users editing the same list.”
Large Enterprises
Screna has 15 Asana interview write-ups. The most reported round is the system design round (6).
15 interview notes · updated Jun 2026
“This sounds straightforward until you start thinking about real-time sync between users editing the same list.”
“I started with the move logic and immediately got tangled up in the merge order.”
“I started with the Piece class and worked outward, which felt natural but I spent too long on edge representation before touching the Board at all.”
“Two hours for one problem sounds generous until you're actually in it.”
“I started with Piece and worked outward, which felt natural but I think I spent too long on the class hierarchy before touching the board structure.”
“The part that tripped me up was the justification.”
“Went fine.”
“I jumped straight to backtracking and the interviewer kind of let me run with it before asking how I'd handle ambiguous matches.”
“The match function being a black box was the part that messed me up early.”