← Back to Directory

Asana interview notes, page 3 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·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Asana, got a prioritization question that sounds straightforward until you're actually in the seat trying to answer it.
  • As a PM, how would you prioritize improving product performance versus building new features?

“I went straight to impact framing and talked about user retention signals tied to latency, which felt right in the moment.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Asana software engineer interview that went deep into object-oriented design, specifically around a jigsaw puzzle game. More involved than I expected for what I thought would be a standard coding round.
  • Design an object-oriented model for a jigsaw puzzle game in a real programming language. Your model should include a Puzzle class composed of Pieces, each with a position in the solved image and edges that can be flat, tab (outward), or blank (inward). Pieces should be placeable on a board with valid interlocking logic, support rotation, snapping of connected groups, and a solved-state check. Walk through your class hierarchy, key data members, the edge-matching algorithm, and how you'd unit-test piece compatibility.

“I spent the first few minutes just staring at this because I kept second-guessing whether to start with the edge type enum or the board class.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Asana for a software engineer role. The whole thing was basically a deep dive into building a scaled-down Twitter, which sounds approachable until you realize how many tricky tradeoffs are buried in it.
  • Design a simplified Twitter-like system that supports posting tweets, following/unfollowing users, a home timeline feed, and viewing a user's profile tweets.

“I started with the data model and APIs which felt like solid footing, but then we got into feed generation and that's where I stumbled a bit.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jun 2026
Coding round at Asana centered on an ASCII art rendering problem. The core question was straightforward enough but the follow-ups kept coming and that's where things got interesting.
  • Given a fixed-height ASCII art character set, render an input string by concatenating each character's block side by side, line by line.

“The base case clicked pretty fast.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jun 2026
Asana software engineer interview with a code review style technical round where they hand you two snippets and ask you to break down what they do, analyze complexity, and spot any problems. Pretty standard stuff but the depth they expected on the analysis 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.

“The part I underestimated was the justification.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Asana system design round, one meaty question about large-scale file processing. The kind of problem that sounds straightforward until you're twenty minutes in and realizing your first answer doesn't actually work.
  • You have a file of IP addresses, one per line, that's too large to fit in memory. How do you find the most frequent IP address(es)?

“Started with the hashmap answer because of course I did.”

View Post

Asana·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Interviewed for a PM role at Asana and got hit with a product design question that was way more open-ended than I expected. Short round, one big question, left feeling like I either nailed it or completely missed the point.
  • Design an on-demand laundry service app, similar to how Uber works for rides.

“I spent the first minute just mapping out who actually uses this: busy professionals, people without in-unit washers, maybe college students.”

View Post

Asana·Product Manager·Hiring Manager Screen

Jun 2026
Interviewed at Asana for a product management role. One question, pretty standard PM leadership territory, but it made me think more than I expected.
  • How do you get your team bought into a product vision and keep them motivated around it?

“I rambled a bit on this one.”

View Post

Asana·Product Manager·Onsite - Product Sense / Strategy

Jun 2026
Asana PM interview with a single product design question. Pretty open-ended, which sounds fun until you're actually sitting there trying to figure out who the user even is.
  • How would you design a ClassPass-style product for children?

“My first instinct was to just map ClassPass one-to-one onto kids and call it a day.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jun 2026
Asana software engineer interview with three back-to-back technical questions: code reading with complexity analysis, then two object-oriented design problems. The OOD problems were heavier than I expected and felt more like mini system design than classic coding.
  • You're given two short code snippets. Explain what each one does in plain English, then analyze the time and space complexity of both.
  • Design the core classes and APIs for a jigsaw puzzle application. Pieces can be rotated, each piece has four sides that must match neighbors, and the board needs to support placing, removing, and validating placements.
  • Design the core logic and data model for the 2048 game, including how a move is processed, tile merging, spawning new tiles, score tracking, and game-over detection.

“This part felt manageable but I fumbled a bit on stating assumptions out loud.”

View Post