Asana interview notes, page 4 of 5

“The match function being a black box was fine, what tripped me up was not knowing the grid dimensions.” 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 way too long on the UI side and not enough tying it back to the actual hypothesis.” 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 jumped straight into features and had to backtrack when I realized I hadn't defined who 'kids' even meant.” 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.

“This one wrecked me for the first few minutes because I kept trying to figure out the grid shape and piece placement at the same time, which is just too much to hold in your head.” 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 started with Piece and Puzzle and thought I was doing great, then the interviewer asked how I'd actually represent a tab vs a blank on an edge and I kind of froze.” 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.

“This is where I spent most of my time and also where I probably went too broad too fast.” 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.

“Not enough detail shared about how it went to say much.” 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 went straight to users and use cases, office workers with different schedules, shared space frustrations, food theft drama.” 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 fumbled the opener a bit, spent too long setting up context before getting to the actual trade-off.” 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 froze for a second because it sounds fun until you realize they're asking you to basically narrate your entire PM philosophy in a creative wrapper.” The rest of the author's notes on Product Manager interview at Asana, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.