Asana Software Engineer Interview Experience — Two Onsites, Rejected Over "Communication Clarity"

Company: Asana

Role: Software Engineer

Round: Onsite

Seniority: General

Outcome: Rejected

Round 1: - Given two code snippets and asked what they do, plus their time/space complexity - Jigsaw Puzzle design — the forum said pseudocode was fine, but the interviewer still made me pick a language and write actual code Round 2 (split across two days): - Ascii Printer: 1 hour of coding (the last 45 minutes the interviewer asks questions about your code). A handful of functions to implement. A 10x6 canvas where each cell can hold a color and an ascii character. You implement draw_rectangle(char, left_x, top_y, right_x, bottom_y), DRAG_AND_DROP(select_x, select_y, to_x, to_y) (can't change the layer order), and ERASE_AREA(from_x, to_x, from_y, to_y) - BQ (projects I'd worked on, mentorship experience, how I resolved a conflict with a coworker) - An LC-style problem (the exact name got garbled when I copied this over) plus a 2048 game design question - Given a large local log file, count how many times each IP address shows up. They asked about a few edge cases too - Design Twitter, but not like a typical system design round — you don't draw anything, it's mostly you talking through it out loud and writing notes, so how well you click with the interviewer matters a lot here Even though every question here was something already posted on the forum, the whole experience was bad. At this point even if they extend an offer I'm not considering it — the team vibe felt pretty average. When people asked about company culture, the interviewers all answered with a cold, generic corporate line. Felt like they were burned out and didn't really want to be interviewing. Except for Round 1 and the woman who ran the system design round in Round 2, every male interviewer in Round 2 had this checked-out, unenthusiastic look on their face the whole time. The BQ with the hiring manager was the worst part of the whole loop. After I finished talking about a project there was zero interaction or follow-up — straight to the next question like talking to a machine. At the very start they took forever just picking which question to ask, and honestly their own speech wasn't that fluent either — might as well have done a TOEFL speaking test with an actual machine. So the feedback I ended up getting was the hiring manager saying my "communication clarity" wasn't up to par. Kind of funny, honestly 😀

Asana Software Engineer Interview Experience — Two Onsites, Rejected Over "Communication Clarity"

Asana·Software Engineer·Jan 2026
OnsiteRejectedmedium

Round 1:

  • Given two code snippets and asked what they do, plus their time/space complexity
  • Jigsaw Puzzle design — the forum said pseudocode was fine, but the interviewer still made me pick a language and write actual code

Round 2 (split across two days):

  • Ascii Printer: 1 hour of coding (the last 45 minutes the interviewer asks questions about your code). A handful of functions to implement. A 10x6 canvas where each cell can hold a color and an ascii character. You implement draw_rectangle(char, left_x, top_y, right_x, bottom_y), DRAG_AND_DROP(select_x, select_y, to_x, to_y) (can't change the layer order), and ERASE_AREA(from_x, to_x, from_y, to_y)
  • BQ (projects I'd worked on, mentorship experience, how I resolved a conflict with a coworker)
  • An LC-style problem (the exact name got garbled when I copied this over) plus a 2048 game design question
  • Given a large local log file, count how many times each IP address shows up. They asked about a few edge cases too
  • Design Twitter, but not like a typical system design round — you don't draw anything, it's mostly you talking through it out loud and writing notes, so how well you click with the interviewer matters a lot here

Even though every question here was something already posted on the forum, the whole experience was bad. At this point even if they extend an offer I'm not considering it — the team vibe felt pretty average. When people asked about company culture, the interviewers all answered with a cold, generic corporate line. Felt like they were burned out and didn't really want to be interviewing.

Except for Round 1 and the woman who ran the system design round in Round 2, every male interviewer in Round 2 had this checked-out, unenthusiastic look on their face the whole time. The BQ with the hiring manager was the worst part of the whole loop. After I finished talking about a project there was zero interaction or follow-up — straight to the next question like talking to a machine. At the very start they took forever just picking which question to ask, and honestly their own speech wasn't that fluent either — might as well have done a TOEFL speaking test with an actual machine. So the feedback I ended up getting was the hiring manager saying my "communication clarity" wasn't up to par. Kind of funny, honestly 😀

Curated and edited by PracHub

Practice the questions from this interview

Asana Software Engineer Interview Experience — Two Onsites, Rejected Over "Communication Clarity" | Asana Interview Experience