Amazing culture, challenging distribution of responsibility
Amazing culture, challenging distribution of responsibility
They say culture was the first thing the founders considered when starting Asana, and it shows. The company values are more present and alive at Asana than anywhere else I have worked.
The food perks are above-and-beyond. Asana's in-house culinary team provides delicious and healthy meals every day.
Lots of avenues for growth in engineering.
Super strong documentation culture.
Extremely capable teammates with high EQ.
Using Asana for everything internally is productive and good for centralizing knowledge, but it leads to internal usage patterns that are very different from those of the typical user. This, in turn, leads Asana to focus on different pain points than their users actually experience.
The company has the feel of being tech-first for many years, but it is trying to put more of a product-first process into place.
The tech stack is mostly homegrown and highly idiosyncratic. The usage of React does not follow common conventions.
The role of Technical Lead has historically been overloaded, resulting in burnout. However, eng leadership has demonstrated a strong focus in trying to mitigate this.
Additional Ratings
Was this helpful?
Asana Interview Questions
Asana Interview Experiences
Technical Lead
It was a phone interview, featuring behavioral and technical questions. Feedback during the interview was positive, and the interviewer confirmed that my answers were appropriate. A few days later, the recruiter rejected my application without expl
Software Engineer (Internship)
Very standard OA – phone – onsite process, except they dropped the ball a couple of times, which made me miss the opportunity to have the final round of interviews before roles were filled. Very disappointed.
Senior Software Engineer
Well-structured, in-person interview. It included a phone screen, followed by an onsite interview. The onsite was split into four interviews spanning five hours. This included system design, behavioral interviews, and two coding rounds of one and tw
Technical Lead
Warsaw, Masovian Voivodeship, PolandSeptember 1, 2024It was a phone interview, featuring behavioral and technical questions. Feedback during the interview was positive, and the interviewer confirmed that my answers were appropriate. A few days later, the recruiter rejected my application without expl
Software Engineer (Internship)
San Francisco, California, United StatesNovember 4, 2025Very standard OA – phone – onsite process, except they dropped the ball a couple of times, which made me miss the opportunity to have the final round of interviews before roles were filled. Very disappointed.
Senior Software Engineer
San Francisco, California, United StatesSeptember 16, 2025Well-structured, in-person interview. It included a phone screen, followed by an onsite interview. The onsite was split into four interviews spanning five hours. This included system design, behavioral interviews, and two coding rounds of one and tw
