Asana was built towards maintaining its values and culture. You can see how they manifest through people's actions and how they set up their teams and their work. People seem like they always look forward to setting each other up for success and rely on collaboration a lot to ensure things are working. The work people do is very visible, as we all use Asana as a work tool. This brings great clarity and makes each person feel useful within the big picture of things. All values are well lived and demonstrated through everyone's work. It is executed very smoothly, and people are typically very careful on optimizing for alignment and clarity before making strong decisions and taking feedback openly.
Getting used to Asana's way of work is quite a learning curve. Starting up can be overwhelming, and the onboarding is thorough and at times heavy. However, it's helpful to have it as a reference for the future. Still, I don't think I'm able to remember many things from onboarding, as there were so many different topics. It takes some time going through it and internalizing the knowledge.
Thanks for cultivating this positive and collaborative culture.
Recruiter call followed by a technical screen. Then onsite. Onsite was nice and there was a break for lunch too. Overall a pretty smooth process though they did kind of lag in between the screen and onsite.
Gave a simple 90-minute interview with discussion afterwards. The question was easy, and the discussion was smooth. Have a good understanding of your code and be prepared to explain all of your design decisions.
This was a discussion about some algorithm. It was an open-ended question about how I would solve the problem, essentially a proxy for remembering graph algorithms. I didn't pass, primarily because I wasn't familiar with the specific technique for f
Recruiter call followed by a technical screen. Then onsite. Onsite was nice and there was a break for lunch too. Overall a pretty smooth process though they did kind of lag in between the screen and onsite.
Gave a simple 90-minute interview with discussion afterwards. The question was easy, and the discussion was smooth. Have a good understanding of your code and be prepared to explain all of your design decisions.
This was a discussion about some algorithm. It was an open-ended question about how I would solve the problem, essentially a proxy for remembering graph algorithms. I didn't pass, primarily because I wasn't familiar with the specific technique for f