There's a lot of hard and interesting work to do, largely driven by our growth and the fact that the problem still isn't solved.
Company leadership is competent and open, and this trickles down to the company having a high degree of trust throughout. This means that my day-to-day work at Asana feels very collaborative, whether I'm working with people directly on my team or elsewhere in the company. Even in the strongest disagreements I have with colleagues, it's quite clear that everyone is trying to do what's best for Asana and our customers, and we're just disagreeing about the best way to do this.
On top of all this, I really enjoy working at a company whose business model is to build a great product and sell it, rather than being advertising-based.
There have been a number of times when we've been too clever, doing either engineering or planning in an "Asana" way, only to have to learn the hard way why things are normally done differently. We say that one of our engineering principles is simplicity, but this is something that doesn't come naturally, and we still need to work on it.
I applied online. There were 8 interviews including the recruiter screen. The experience was neutral. The process was slow, and the recruiter didn't seem very invested. It was heavy on behavioral questions, focusing on non-trivial examples from expe
There are a total of seven interviews. The focus is on coaching reports (be prepared to talk about your history in doing that) and some technical competency. I was asked to design a simple dTa model to support a single function.
The process consisted of a first round with the head of engineering, followed by a virtual on-site with several different stakeholders. Though on the lengthy side, impressions of the culture were very positive. I’m still waiting to hear back on thei
I applied online. There were 8 interviews including the recruiter screen. The experience was neutral. The process was slow, and the recruiter didn't seem very invested. It was heavy on behavioral questions, focusing on non-trivial examples from expe
There are a total of seven interviews. The focus is on coaching reports (be prepared to talk about your history in doing that) and some technical competency. I was asked to design a simple dTa model to support a single function.
The process consisted of a first round with the head of engineering, followed by a virtual on-site with several different stakeholders. Though on the lengthy side, impressions of the culture were very positive. I’m still waiting to hear back on thei