← Back to Directory

Asana interview notes, page 2 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·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Asana for a software engineer role, three questions covering past work, mentorship, and conflict. Pretty standard stuff but they wanted real specifics, not vague answers.
  • Walk me through a past project you're most proud of, including your role, the technical challenges you faced, and the impact it had.
  • Describe a time you mentored a junior engineer or a peer. What did you actually do and how did it turn out?
  • Tell me about a conflict you had with a teammate, manager, or stakeholder and how you resolved it.

“This is the one I actually felt okay about.”

View Post

Asana·Software Engineer·Onsite - System Design / Architecture

May 2026
Interviewed at Asana for a backend/infrastructure-leaning engineering role. One system design question, pretty focused session, no small talk.
  • How would you optimize a Content Distribution Network (CDN)?

“I started with caching strategies and edge node placement, which felt right, but I think I spent too long on cache invalidation and never got to load balancing or geo-routing in any real depth.”

View Post

Asana·Software Engineer·Onsite - Product Sense / Strategy

May 2026
Asana EM interview with a single product design question. Pretty open-ended, which I wasn't fully prepared for.
  • Design a video streaming product for toddlers.

“I jumped straight into features and kind of forgot to anchor on the user first.”

View Post

Asana·Product Manager·Onsite - Product Sense / Strategy

May 2026
Product sense interview at Asana centered on designing social features for Stitcher. The prompt was open-ended and pushed hard on tradeoffs and metrics, which I wasn't fully ready for.
  • What new feature would you build to add social capabilities to Stitcher? Define your goals and target users, and walk through the alternatives you considered before landing on your choice.
  • How would the feature actually look and work? Walk through the user experience, ideally with a rough wireframe or visual description.
  • What are the tradeoffs and risks of the feature you proposed, and how would you measure whether it's actually successful? Can you think of a scenario where the feature gets used a lot but you'd still consider it a failure?

“I spent too long on the brainstorming list and not enough time actually justifying why I picked what I picked.”

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 pace was quick and I felt like I was just barely keeping up.
  • 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.

“I had a story ready but halfway through I realized I was spending too much time on context and not enough on what I actually did.”

View Post

Asana·Product Manager·Onsite - Product Sense / Strategy

May 2026
Asana PM interview, got a product metrics question dressed up in a silly wrapper. Pretty standard underneath the cat gif framing.
  • You're building CatGifs.com. How would you measure the site's performance?

“The cat gifs thing threw me for a second because I kept trying to make it mean something deeper.”

View Post

Asana·Software Engineer·Technical Phone Screen

May 2026
Asana software engineer interview with three coding problems back to back. Nothing behavioral, just pure implementation and problem-solving. The canvas question was the wildest one I've seen in a while.
  • Build a small ASCII drawing engine for a fixed 10x6 canvas. Each cell holds a character and an optional color. Implement draw_rectangle, drag_and_drop, and erase_area operations, then render the canvas as text. Discuss edge cases.
  • Given an integer array, return a new array where each element is the product of all other elements. No division allowed, O(n) time, O(1) extra space beyond the output array. Handle zeros.
  • Count how many times each IP address appears in a very large local log file that may not fit in memory. Discuss parsing, validation edge cases, and performance tradeoffs.

“This one took me a second to parse.”

View Post

Asana·Product Designer·Onsite - Product Sense / Strategy

May 2026
Asana product design interview where they asked me to whiteboard a wishlist-sharing app from scratch. Pretty open-ended, which sounds fun until you're staring at a blank whiteboard.
  • Whiteboard a mobile or web app that lets users build and share wishlists with their friends.

“I jumped straight into features and completely skipped defining the user.”

View Post

Asana·Software Engineer·Technical Phone Screen

Jun 2026
Asana software engineering interview that went deep on game logic design. The main problem was implementing 2048 from scratch, which sounds fun until you're live-coding merge behavior and trying to explain a clean API at the same time.
  • Implement the core game logic for 2048 on a 4x4 grid, including tile shifting, merging, spawning new tiles, and detecting win/game-over conditions.
  • Design a move() API that returns enough information for a frontend engineer to render the UI, including the updated board, which tiles merged, where the new tile spawned, the current score, and the game status.
  • How would you separate game state management, move logic, and rendering concerns in this design?

“I started with the move logic and immediately got tangled in the merge-once-per-move constraint.”

View Post

Asana·Software Engineer·Onsite - Coding / Algorithms

Jun 2026
Coding round at Asana with four problems ranging from backtracking to grid simulation. The questions were varied enough that you couldn't just grind one topic and coast through. Felt like they wanted to see clean code and complexity awareness more than just a working solution.
  • Given N square tiles each with labeled edges (top, right, bottom, left), and the ability to rotate each tile, determine if the tiles can be arranged into an R x C grid where all touching internal edges match. N is small enough for backtracking.
  • Implement an ASCII canvas of size H x W. Support commands: fill a rectangle with a character, draw a horizontal line, draw a vertical line. Later commands overwrite earlier ones. Print the final canvas.
  • Return an array where each element is the product of all other elements in the input array. No division allowed, O(n) time, O(1) extra space beyond the output array.
  • Simulate a single move in 2048 on a 4x4 grid. Given a direction, slide and merge tiles correctly. For example, [2, 2, 2, 0] moving left becomes [4, 2, 0, 0]. Return the updated grid.

“This one took me a while to even set up correctly.”

View Post