← Back to Directory

Asana

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

Asana·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Asana for a software engineer role. Just one question but it had a lot of surface area and I don't think I covered everything I should have.
  • Design a collaborative todo list application.

“This sounds straightforward until you start thinking about real-time sync between users editing the same list.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jun 2026
Did a technical round at Asana for a software engineer role where they had me implement the full game logic for 2048, including the API design for a frontend consumer. More design-heavy than I expected for a coding interview.
  • Implement the core game logic for 2048 on a 4x4 grid, including tile shifting, merging, new tile spawning, and win/loss detection.
  • Design an API for the 2048 game engine so a frontend engineer can cleanly drive the UI. What does the move function return, and how do you separate game state, move logic, and rendering concerns?

“I started with the move logic and immediately got tangled up in the merge order.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jun 2026
Asana asked me to design an object-oriented model for a jigsaw puzzle game in a real language, with working code. It was a deep OOD question that also touched on algorithms and testing strategy, so it kept branching in ways I didn't fully anticipate.
  • Design an object-oriented model for a jigsaw puzzle game in a real programming language. Your model should include a Puzzle composed of Pieces with edge types (flat, tab, blank), a Board where pieces can be placed with interlocking validation, and support for operations like picking up a piece, rotating it, placing it, snapping connected groups, and checking if the puzzle is solved. Also discuss your class hierarchy, edge-matching logic, and how you'd unit test piece compatibility.

“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.”

View Post

Asana·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Two-hour coding round at Asana for a software engineer role, centered on a single ASCII Printer problem. Not a lot to say about the process itself but the problem was more involved than the name suggests.
  • Implement an ASCII Printer: given some input, produce formatted ASCII art or text output according to specified rules.

“Two hours for one problem sounds generous until you're actually in it.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Asana system design round for a software engineer role, focused entirely on object-oriented design for a jigsaw puzzle game. Pretty deep dive, more than I expected from what sounds like a toy problem.
  • Design the core classes for a jigsaw puzzle game. Walk through Puzzle, Piece, Edge/Side, and Board, including how pieces represent their four sides and how the assembled board is structured.
  • How would you determine if two puzzle pieces are compatible with each other? What does that compatibility check look like in code?
  • Define the API for the puzzle board: placePiece, removePiece, isComplete, and getNeighbors. What are the method signatures and what does each return?
  • How would you extend this design to support arbitrary puzzle shapes, a hint or auto-solve feature, and multi-player collaborative solving?

“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.”

View Post

Asana·Software Engineer·Technical Phone Screen

May 2026
Asana SWE interview with a code analysis round where they hand you two snippets and want you to walk through what they do, complexity, and any improvements. Pretty standard but the depth they expect on the analysis side caught me a bit off guard.
  • Given a code snippet, explain in plain English what it does, analyze its time and space complexity with justification, and identify any edge cases or inefficiencies. Propose a more efficient version if one exists.
  • For a second code snippet (e.g. a recursive or memoized implementation), repeat the same analysis: describe behavior, state complexity in Big-O with reasoning, and comment on hidden costs or improvements.

“The part that tripped me up was the justification.”

View Post

Asana·Software Engineer·Technical Phone Screen

May 2026
Did an object-oriented design round at Asana for a software engineer role. One question, LeetCode-style, nothing too wild but worth knowing what you're walking into.
  • Solve a LeetCode-style object-oriented design problem.

View Post

Asana·Software Engineer·Hiring Manager Screen

May 2026
Behavioral round with the hiring manager at Asana for a software engineer role. Four prompts, all pretty standard territory, but the mentorship one tripped me up more than I expected.
  • Tell me about a project you worked on.
  • Describe a time you mentored someone.
  • Tell me about a conflict you had at work and how you handled it.
  • Walk me through a time you improved an existing system or process.

“Went fine.”

View Post

Asana·Software Engineer·Onsite - Coding / Algorithms

May 2026
Asana coding round with a puzzle assembly problem that sounds deceptively manageable until you're mid-explanation and realize you haven't thought through the edge cases at all.
  • Given a set of 2D jigsaw puzzle pieces where each piece has descriptors for its four edges, assemble them into a complete grid so that adjacent edges match correctly.

“I jumped straight to backtracking and the interviewer kind of let me run with it before asking how I'd handle ambiguous matches.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Asana system design round, one question the whole time. The problem was deceptively open-ended and I kept second-guessing myself on where to even start.
  • Design a jigsaw puzzle solver. You're given a match(e1, e2) function that tells you whether two edges fit together. The number of rows and columns is not known in advance. How do you implement the solve function?

“The match function being a black box was the part that messed me up early.”

View Post