Very friendly and helpful peers and managers.
Excellent experience learning to do software engineering work at a place with good engineering standards.
Really talented engineers.
Customers love the product.
Decently interesting technical challenges.
Work-life balance is good, although not as good as places where there just isn’t enough work to do (e.g., LinkedIn or some teams at Google).
Compensation is way below market, especially for experienced engineers. They have an unrealistic view of market comp, which means you will get limited raises and no refreshers until your initial grant finishes vesting.
Product-oriented org means there is a lot of red tape for engineers to ship new features unless they have already been approved by the product people.
Lots of tech debt.
Although the culture is above average, the constant patting on the back about how great the Asana culture is tends to get grating. We don’t need to keep hearing how awesome our culture is – let’s work on making it better.
Lack of clarity regarding advancement due to lack of levels, and regarding getting approval due to lack of clear hierarchy.
Dramatically increase compensation, at least for engineers, probably by giving out large refreshers.
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