Asana is a fantastic place to work. When I first joined, I experienced thorough and thoughtful onboarding. This included a dedicated two-week "bootcamp" to learn all about Asana's engineering systems and practices. Because of the bootcamp, help from onboarding members, and widespread support from Asana's engineers, I was quickly able to contribute meaningfully to the Asana codebase.
Asana's engineering team is strong and values technical design, code quality, documentation, sharing learnings, and fixing problems, even if you weren't the one who caused them. Experienced engineers care about the learning of new hires and less experienced engineers. They will answer questions, pair program, and review code to ensure this happens.
Regarding career development, my manager is very interested in learning about my short-, medium-, and long-term goals and supporting me to reach them. At Asana, it's possible to try a lot of different roles outside of being an individual contributor. For example, you can help with recruiting or leading a project. You can quickly take on lots of responsibility if that's appealing to you.
Individual and group achievements are widely recognized and appreciated. All my coworkers are great communicators, and it makes them easy to work with.
Another huge plus of working at Asana is that you use the Asana app all the time as part of your job. You quickly appreciate its value and become even more motivated to improve it.
Other perks include:
Overall, I'm thrilled to be part of a company that cares so much about its employees' well-being and development. I find it incredibly motivating to work among people who believe in and care deeply about the product.
The work is highly collaborative, which might be a con for someone who likes to work more independently. I'm a pretty introverted person, though, and I'm finding that the support of my manager and shared goals with my coworkers make the collaboration useful and interesting instead of difficult or draining.
After the first round with the Hiring Manager, the second round was a quick technical interview. Both interviewers were very friendly. I was asked to explain a given piece of code and to approve it. The second question was about a jigsaw puzzle.
The initial HM screen was followed by a technical phone screen, which included a mix of LeetCode medium problems, object-oriented programming (OOP), and general problem-solving. The interviewer was pleasant, and I left thinking that this seemed like
Coding, behavior, and system design questions. Emphasis on cooperative communication. System design is a normal question. Preparation can help. Coding is from their own question pool. Remember to have good reference checks.
After the first round with the Hiring Manager, the second round was a quick technical interview. Both interviewers were very friendly. I was asked to explain a given piece of code and to approve it. The second question was about a jigsaw puzzle.
The initial HM screen was followed by a technical phone screen, which included a mix of LeetCode medium problems, object-oriented programming (OOP), and general problem-solving. The interviewer was pleasant, and I left thinking that this seemed like
Coding, behavior, and system design questions. Emphasis on cooperative communication. System design is a normal question. Preparation can help. Coding is from their own question pool. Remember to have good reference checks.