Asana interview notes, page 1 of 5

“Two hours for one problem sounds generous until you're 45 minutes in and still not sure you understand the output format correctly.” The rest of the author's notes on Software Engineer interview at Asana, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight to enterprise because the revenue argument felt obvious, but I think I underplayed the network effects you get from consumer adoption.” The rest of the author's notes on Product Manager interview at Asana, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to just sketch out a basic CRUD API and call it a day, which would have been embarrassing.” The rest of the author's notes on Software Engineer interview at Asana, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started by trying to define who actually uses wishlists and why, which felt like the right move, but I spent too long on that and rushed the actual improvement ideas.” The rest of the author's notes on Product Manager interview at Asana, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew the prefix/suffix product trick going in, so the core solution came out okay.” The rest of the author's notes on Software Engineer interview at Asana, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I spent the first few minutes just trying to figure out who exactly 'senior citizens' meant and what their actual pain points were with existing streaming services.” The rest of the author's notes on Product Manager interview at Asana, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight for adoption metrics and kind of forgot to anchor on what problem the improvement was actually solving first.” The rest of the author's notes on Product Manager interview at Asana, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to treat it like a graph problem and I spent too long thinking about it that way before realizing a hash map keyed on edge descriptors was way cleaner.” The rest of the author's notes on Software Engineer interview at Asana, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to jump straight into features, which was a mistake.” The rest of the author's notes on Product Manager interview at Asana, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I had a decent story ready but I kept jumping between the technical decisions and the business outcome without connecting them well.” The rest of the author's notes on Software Engineer interview at Asana, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.