Very little politics or unnecessary work. You really feel like your time is spent pursuing the mission to help teams become more effective.
People are really amazing. I work in software engineering and I'm impressed by how cool & thoughtful my co-workers are in addition to their engineering skills.
Tying into (2), the work environment is super collaborative, meaning that I get to work with engineers (and non-engineers) far removed from my core team, which is really awesome.
The culinary team is one of a kind. Food is amazing, healthy, and they put on a lot of fun, unique events.
At Asana, we use the Asana product daily, which is great because seeing yourself become more productive as a result of a feature you built feels really rewarding.
Using the Asana product also means that we benefit from having clarity about who's doing what by when. This really helps us get more out of our days while minimizing "status-update" type meetings that would otherwise drain a lot of time.
There is some large technical debt that the company is still working with. We've come a long way towards making this a lot better, but we still have a long way to go before this debt is fully addressed.
There are so many important things that we want to pursue all at once that it can sometimes feel like initiatives are understaffed, or we can't work on things we really need to work on.
Be more willing to make long-term bets and invest in initiatives with a longer time frame. Our efforts to improve performance were a clear example of when a long-term investment paid off, and I'd love to see more of that.
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