Candidatei-me online. O processo levou 2 meses. Fiz uma entrevista na empresa Asana (San Francisco, CA).
Entrevista
It was a (pretty easy) coding challenge followed by a phone screen. I thought that I bombed part of the phone interview, so when I was invited for an onsite, I was super excited. I had an onsite that included two whiteboard type interviews (with both algorithms and OOP questions) and was also given some time to work on a coding assignment and then did a code review with two engineers.
The whole process was great -- I felt like more than any company I've ever interviewed at, Asana didn't just want to see me jump through hoops, but really cared about understanding me, what I was looking for, and tried to understand my abilities in a more holistic way. The whiteboard interviews were much more collaborative than anywhere else I've experienced -- it felt like I was working with the interviewer rather than against them. They also gave me a lot of chances to talk to engineers in a non-evaluative setting, which helped me ask a lot of important questions.
Perguntas de entrevista [1]
Pergunta 1
I don't believe in giving away interview questions
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