Pros: 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.

Cons: 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.

Pros: - A strong team from a technical perspective - Managers who listen to you - Benefits

Cons: At the moment, I haven't noticed.

Pros: - Outstanding compensation - Support of other engineers (personal mentor) - Friendly culture, chill atmosphere - Free food - Great hardware equipment - Nice office located in the city center

Cons: I did not fully understand the hiring process selection. I was rejected for another location first, but fortunately, after asking about Warsaw, I was accepted. Long onboarding: Took over a quarter of the internship (a lot of things to learn, internal frameworks). On the other hand, the bootcamp project helped me with technologies I had not used before, and people put a lot of effort into helping new hires. Included a bit of boring corporate training.