Asana interview notes, page 5 of 5

Large Enterprises

Most of these Asana write-ups come from Software Engineers (31), then Product Managers (15) and Product Designers (1). The most reported rounds are the product sense round (15), the technical phone screen (13), the system design round (11) and the hiring manager screen (4).

47 interview notes · updated Jul 2026

Asana·Software Engineer·Hiring Manager Screen

Jul 2026

Interviewed for an account manager role at Asana, pretty standard stuff, just one question that I can remember clearly.

Where do you see your career heading, and what are you working toward professionally?

“I fumbled this a bit.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jul 2026

Coding round at Asana for a software engineer role. The problem was an ASCII art renderer, which sounds straightforward but has enough edge cases to keep you busy for a while.

Implement an ASCII art printer that renders an input string using a given font, where each character is defined as a fixed-height glyph. Characters are concatenated horizontally row by row, with a single blank column between them. Newlines in the input start a new glyph block. Spaces render as blank glyphs. Unsupported characters should either error or use a placeholder. The solution must run in O(S) time where S is the total size of the rendered output, and must return a string rather than printing to stdout.

“I went straight to the horizontal concatenation logic and got that working pretty quickly.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jul 2026

Asana OOD round, got asked to design the 2048 game. Not the hardest thing in the world but there's more to it than you'd think when you're on the spot.

Design the 2048 game using object-oriented principles.

“I started with the board and tile classes which felt right, but then I kind of fumbled explaining how the merge logic should live.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jul 2026

Asana system design round focused entirely on building a collaborative todo-list service, the kind of thing that sounds deceptively simple until you're 20 minutes in and realize you haven't even touched real-time sync yet. Heavy on trade-offs, concurrency models, and consistency decisions.

Design a collaborative todo-list service where teammates can create shared lists, add and edit items, assign owners, set due dates, reorder items, and see each other's changes in near real time across web and mobile.
How would you order concurrent changes to a shared list so every client, including one that's been offline, can reason about what happened and catch up from a single cursor?
When multiple users reorder items at the same time, what goes wrong with dense integer positions and how do you handle the merge?
Walk through how a committed write reaches all other connected clients. What guarantees that the published event isn't lost if the message bus is briefly unavailable?
How does your design change if a single hot list suddenly has thousands of simultaneous editors instead of tens?
An offline client made three edits while disconnected, two of which conflict with changes committed by others in the meantime. What happens on reconnect and what does the user see?
How do you prevent the operation log from growing indefinitely while still letting a client that's been offline for days catch up?
If you needed to add collaborative rich-text editing inside an item's description, what would you change and why is that harder than syncing item fields?

“This is the main question and it ate the whole session.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jul 2026

System design round at Asana for a software engineer role. The whole thing was centered on designing a Twitter-style microblogging platform, which sounds familiar until you actually have to defend your choices under pressure.

Design a Twitter-like microblogging system that supports posting short messages, following/unfollowing users, and viewing a home feed of recent posts from followed accounts at high read and write volume.
What APIs and data models would you define for this system?
How would you handle storage choices and caching for the feed at scale?
How would you approach rate limiting, abuse detection, and observability for this platform?

“I went straight to the feed generation question because I knew that was the meat of it.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jul 2026

Asana software engineer interview, object-oriented design round. The whole session was built around designing 2048, which sounds like a toy problem until you're 20 minutes in and realize you've been thinking about it wrong.

Design the object model and core game logic for a 2048 game on an N x N grid. Focus on classes, responsibilities, relationships, and the algorithm for a move, not on UI or rendering.
How would you handle the 'each tile merges at most once per move' rule in your merge function, and what does a line like [2, 2, 2] produce?
How would you inject randomness so the game logic is deterministically testable?
How would you implement undo? Compare snapshotting the whole board versus recording a reversible move delta.
How would you detect game-over efficiently, and is 'board full' a sufficient condition?
How would you generalize the merge rule so that the slide logic doesn't need to change if the merge condition changes, for example Fibonacci-style merges or a different target tile?

“I started sketching a Board class and a Tile class, which is fine, but I immediately went down the road of writing four separate move handlers.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jul 2026

Asana system design round for a software engineer role. The problem was a classic large-scale log processing question but with enough memory constraint twists that it kept me on my toes the whole time.

You have a log file that's too large to fit in memory, where each line is an IPv4 address. How would you find the most frequent IP address, or the top K most frequent, under strict memory constraints? Walk through your data structures, disk usage, and how your approach shifts as the file grows to hundreds of GB or if an approximate answer is acceptable.

“This one took me a minute to get my footing.”

View Post