Candidatei-me de outra forma. O processo levou 1 dia. Fui entrevistado pela Asana em set. de 2019
Entrevista
Wasted my time.
Got the coding question correct and OOP design question correct. However, the interviewer didn't understand my OOP solution or it seemed he understood it at the end. All at the same time I was asking during the interview if he understood it and he didn't say no. So I assumed he understood it and started talking about other things. It is also difficult to display my ideas over a computer screen, so the question selected isn't appropriate for this space. I drew what I could, yet still failed on communication. This was over a third party interview platform. Interviewer was nice but didn't show any signs that he didn't understand something, he didn't ask clarifying questions to my solution or even tried to poke holes in it like a good interviewer would.
I eat interviews for breakfast, over 300+ leetcode questions and FANG on-sites. Very obvious this interviewer had a lot of learn. He even said this was his first time using the interview platform.
Perguntas de entrevista [1]
Pergunta 1
Check if a BST is valid.
How do you design a chess game?
Thank you for taking the time to interview at Asana. We apologize that your interview experience was not a positive one, and we appreciate you sharing your feedback.
Outras avaliações de entrevista de vagas de Software Engineer da empresa Asana
Fiz uma entrevista na empresa Asana (San Francisco, CA).
Entrevista
HR intro call was typical questions about resume, experience, and goal fit. I didn't get pass this round of the process unfortunately. Seemed like it was a formality call since I had a referral.
Candidatei-me online. Fui entrevistado pela Asana em mai. de 2026
Entrevista
Initial screening went well and I felt genuinely excited about the opportunity. The technical interview itself was different from what the preparation PDF described — less collaborative, minimal engagement from the interviewer's side. I didn't receive any feedback after the session; the interviewer went on sick leave and I waited several weeks before receiving a rejection email.
I'm fine with rejection — that's part of the process. What was harder was the uncertainty and the lack of feedback. The prep materials set clear expectations around collaboration and communication, and the actual experience didn't match that.
Overall, it was a good experience. There was one interviewer who acted standoff-ish and strange. But, for the most part, it was conducted very professionally.
What I didn't like was the Systems interview question, which is a very specific modelling problem and unless you've worked on building such a feature, it's unlikely that you'll recognize such a pattern and come up with a decent solution. And for a mid-level position, it's quite surprising. But I guess they gotta justify the high comps somehow. Also, infrastructure knowledge is not tested at all in this interview, which is atypical.
The coding interviews were great. Study typical LLD problems. Leetcode is minimal and simple. Focus on understanding patterns and not memorizing solutions.
The HM interview was great. He probed in ways typical EMs have never done before, and it gave me a really good impression of the company and his team, despite also not passing this interview, which I take full responsibility for.
Perguntas de entrevista [1]
Pergunta 1
Tell me about a time you experienced mentorship, as a mentor or a mentee