Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en Asana (San Francisco, CA) en oct 2018
Entrevista
1. Coding Challenge. Asana cares more about the approach and design choices here as the platform they want you to code in does not allow you to compile and run tests.
2. Technical Phone Screen. This was done via Google Docs. Again, the interviewer cares more about the thought process then the code itself.
3. Remote Onsite Interview. This round consists of 3 different rounds. The first round was very much like the technical phone screen. The second round was an individual coding challenge. The third round was going over the individual coding challenge. Unfortunately, this round is where the code actually matters. If you cannot code out a valid solution, then it does not really matter if you're able to solve it together with the interviewer for the third round.
Acudí a una entrevista en Asana (San Francisco, CA)
Entrevista
very standard oa - phone - onsite process except they dropped the ball a couple of times that made me miss the opportunity to have the final round of interview before roles were filled. Very disappointed
Preguntas de entrevista [1]
Pregunta 1
leetcode style question, very standard. but I heard they have SD for final round which is both ridiculous and funny
Me postulé en línea. Acudí a una entrevista en Asana (San Francisco, CA) en feb 2025
Entrevista
Very straightforward process with a codesignal followed by a coding round, then an onsite with a system design then behavioral interview. Questions were leetcode focused but generally easy to find online
Preguntas de entrevista [1]
Pregunta 1
There was a question about a very hungry rabbit, I'm sure you can find this one online
several interviews and all super difficult for an internship level. The expectations is that you are a very seasoned junior, not a student. Friendly interviewers but the technical components is quite challenging.
Preguntas de entrevista [1]
Pregunta 1
usual algorithm questions you'd find on hackerrank
