Katkat

Company

Asana interview questions

24 practice questions in the style of Asana's interviews, covering Behavioral & Leadership, Coding & Algorithms, Software Engineering Fundamentals, System Design.

Questions24

0 easy24 medium0 hard

Your progress0/24

Asana interview questions by the numbers

Last updated

Katkat has 24 Asana interview questions. The largest topics are Software Engineering Fundamentals (38%), Coding & Algorithms (29%) and Behavioral & Leadership (21%). By difficulty: 100% medium. The most common round is Onsite (46%). Frequent concepts include Data Structures, Design Patterns, Geometry and Heap.

Difficulty

  • Medium100% · 24

Interview rounds

  • Onsite46% · 11
  • Technical Screen42% · 10
  • Other13% · 3

Roles

  • Software Engineer100% · 24

Frequent concepts

  • Data Structures8% · 2
  • Design Patterns8% · 2
  • Geometry8% · 2
  • Heap8% · 2
  • Object-Oriented Design8% · 2
  • OOP8% · 2

Showing 1–24 of 24 results

  • This question evaluates leadership, communication, mentorship, conflict-resolution, and ownership competencies by prompting examples of project contribution, mentoring, stakeholder conflict handling, and system or process improvements.

    AsanaSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates array manipulation skills, arithmetic reasoning with cumulative products, edge-case handling for zeros and negative numbers, and time/space complexity optimization for in-place or constant-extra-space algorithms.

    AsanaSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates leadership and interpersonal competencies—mentorship, conflict resolution, communication, ownership, and impact articulation—along with judgment about technical and product trade-offs, and it is categorized under Behavioral & Leadership for software engineering roles.

    AsanaSoftware EngineerBehavioral & LeadershipOnsite
  • This question evaluates object-oriented design, state management, deterministic randomness handling, and algorithmic reasoning for implementing game rules on a configurable N x N grid.

    AsanaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates system-design skills for building real-time collaborative applications, covering data modeling, read/write paths, real-time synchronization, concurrent edits and reordering semantics, permission models, and consistency trade-offs within the System Design domain.

    AsanaSoftware EngineerSystem DesignOnsite
  • Design a clean, object-oriented command processor for a fixed 10x6 ASCII canvas that supports drawing, layering, and rendering overlapping filled rectangles.

    AsanaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This problem tests the ability to design a distributed, high-concurrency counter system that maintains strict consistency while ensuring low-latency updates for collaborative task management.

    AsanaSoftware EngineerSystem DesignTechnical Screen
  • This problem tests object-oriented design principles, state management, and the ability to decouple business logic from external dependencies like random number generation to ensure testability.

    AsanaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates system design competencies including scalable architecture, data and API modeling, feed generation trade-offs, storage and caching strategies, consistency expectations, and operational concerns such as rate limiting, abuse mitigation, and observability.

    AsanaSoftware EngineerSystem DesignTechnical Screen
  • This question tests your ability to design a decoupled, extensible object-oriented system that separates game state, rule validation, and game flow logic.

    AsanaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates leadership, project ownership, mentorship, interpersonal communication, and conflict resolution competencies through concrete examples of past work and team interactions.

    AsanaSoftware EngineerBehavioral & LeadershipTechnical Screen
  • This multi-part question evaluates code comprehension and algorithmic complexity analysis alongside object-oriented design competencies for interactive applications, covering skills in analyzing time and space complexity, class modeling, API design, and state management.

    AsanaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's competency in large-scale data processing and algorithm design, focusing on memory- and disk-constrained frequency estimation, streaming and approximation concepts.

    AsanaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This problem tests proficiency with heap-based priority queues and custom sorting logic for spatial coordinates.

    AsanaSoftware EngineerCoding & AlgorithmsTechnical Screen
  • This question evaluates the ability to implement text rendering and string/array manipulation concepts, including glyph concatenation with inter-character spacing, newline-preserved blocks, blank glyph rendering for spaces, and handling of unsupported characters.

    AsanaSoftware EngineerCoding & AlgorithmsOnsite
  • This question set evaluates algorithmic problem-solving competencies including backtracking and constraint satisfaction for jigsaw assembly, simulation and state manipulation for ASCII canvas and 2048 move logic, and linear-time in-place array transformation for the product-of-array problem.

    AsanaSoftware EngineerCoding & AlgorithmsOnsite
  • Design the object model, game state invariants, and move-validation engine for an asymmetric turn-based grid game played on a 7x7 board.

    AsanaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This problem tests object-oriented modeling skills and the ability to implement a backtracking algorithm with state pruning for a combinatorial search task.

    AsanaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question assesses a candidate's ability to communicate complex interpersonal dynamics and technical problem-solving within a unified narrative structure.

    AsanaSoftware EngineerBehavioral & LeadershipTechnical Screen
  • A low-level design exercise asking for the classes, responsibilities and core code of a two-player chess program. It tests object modeling of pieces, board and game state, move validation including check and special moves, checkmate and stalemate detection, and keeping the design open to undo, network play or a computer opponent.

    AsanaSoftware EngineerSoftware Engineering FundamentalsOther
  • A behavioral interview question about how you work with teams outside your own, such as other engineering groups, product and design, when your work depends on or affects theirs. It tests aligning goals and interfaces, managing dependencies, resolving disagreements directly, and communicating clearly across team boundaries.

    AsanaSoftware EngineerBehavioral & LeadershipOther
  • A coding exercise on a sorted integer array: return the k elements nearest a target value in ascending order, where equal distances favor the smaller value. It tests exploiting sorted order, handling targets outside the array's range, and treating duplicate values correctly.

    AsanaSoftware EngineerCoding & AlgorithmsOther
  • This problem tests the ability to efficiently find the nearest neighbors to a target coordinate while maintaining a deterministic ordering for ties, ensuring reproducible results.

    AsanaSoftware EngineerCoding & AlgorithmsOnsite
  • This question evaluates algorithmic problem-solving, constraint satisfaction, search and pruning strategies, and handling combinatorial state such as piece rotation and placement.

    AsanaSoftware EngineerCoding & AlgorithmsTechnical Screen

Asana interview experiences

All 11 →
  • Design-Heavy Loop After Lots of Peer Mock InterviewsAsana · Software Engineer · Other · Sep 2026

    I'm a mid-level engineer with roughly 3-4 years of experience, almost all of it in backend work, mostly distributed systems at fintech companies. I went to a state school and did just one internship during college. Asana hands candidates a study guide, and I'd tell anyone to work through it, even if they're interviewing somewhere else. Most of my own studying was the video lessons and quizzes fro…

  • Rejected

    I went through an intense, multi-step process that felt excessive for the role. After speaking with a recruiter, I had several interview rounds with detailed technical questions. The process stretched across six stages, ending with a 45-minute presentation that required a lot of preparation on top of everything else. I passed every stage with positive feedback and felt that the conversations were…

  • Asana Software Engineer coding interview with no feedback before rejectionAsana · Software Engineer · Technical Screen · Jun 2026
    Rejected

    I started with an initial screening that left me genuinely excited about the opportunity. The technical part didn’t match what I expected from the preparation materials. Instead of feeling like a collaborative back-and-forth, the interaction was noticeably less engaging, and the interviewer’s involvement felt minimal. I didn’t receive feedback after the coding interview, so the uncertainty dragge…

  • Asana Software Engineer interview with a referralAsana · Software Engineer · HR Screen · Jun 2026

    My process was short and ended quickly. It started with an HR introduction call focused on standard resume and experience questions, along with how my background fit the role. It didn't feel like much of an exploration of my strengths or working style. The call felt more like someone moving through a checklist. Because I had a referral, the conversation also felt somewhat ceremonial. After the HR…

  • Asana Software Engineer interview with a specific systems modeling problemAsana · Software Engineer · Technical Screen · Mar 2026
    Rejected

    The overall experience felt professional, and most of the rounds ran cleanly. One interviewer came across as standoffish, which threw me off more than anything technical, but the logistics and tone were mostly well handled. The part I struggled with was the systems interview. It involved a very specific modeling problem that didn't resemble the general patterns I expected. Unless I'd previously b…

More companies