I love that we're building a product that people pay for and use on a daily basis. We use our own software at work a lot; it essentially replaces internal email for us. It's super rewarding to work on a tool that I love to use.
The culture at Asana is so respectful and cooperative, and I have always felt supported and encouraged by my manager. As engineers, we're given the resources needed to build things sustainably and according to best practices. We believe that engineering is a collaborative activity, not an individualistic one with "rockstar programmers" who are actually jerks.
I also love the way the company structures its initiatives. Everything I work on ladders up to a clear key result, which in turn ladders up to a measurable objective. I always know why the thing I'm working on is important.
Because roles are really flexible here, you're expected to have a bit of initiative and seek out responsibilities or projects that you're passionate about. You might find your growth here is limited if you're not interested in expanding your responsibilities beyond your immediate team.
Also, because Asana is so focused on collaboration, it might not be the best place for you if you don't like working closely with other people or mentoring others.
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