Me postulé en línea. El proceso tomó 4 semanas. Acudí a una entrevista en Asana en ene 2022
Entrevista
First round was OA from CodeSignal.
Second round was conducted on Codesignal. Expect to read some code snippets and tell their complexity. Try to finish this part quickly as you will have an oop design question. The interviewer will try to keep you from straying away from the right solution. Pretty much like collaboration.
Onsite includes 3 rounds. 1x2-hour coding session, 2x45-minute system and design. For the 2-hour coding, the interviewer lets you ask questions and then logs out so you can work alone for 70 minutes. After that, he comes back to go over your implementation and asks questions. For the system round, expect some lc coding and oop design. For the design, be ready to communicate clearly and think out loud. I actually had a lot of fun and learned something new in this round. This round was very practical.
Overall, people were really engaging and smart.
The onsite has built-in 15-minute breaks between rounds. Also, they give you a 45-minute session to talk to an engineer to learn more about the company.
My recruiter was willing to give me some high-level feedback, which is something not many companies do.
I would say that I had a pretty good experience with Asana.
5
Otras evaluaciones sobre las entrevistas para el cargo de Software Engineer en Asana
Me postulé en línea. Acudí a una entrevista en Asana en may 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.
Preguntas de entrevista [1]
Pregunta 1
Tell me about a time you experienced mentorship, as a mentor or a mentee
classic lc style medium question, and some basic intro be havioral in technical. good inter viewers. made sure the ex perience is pleasant for interviewee. did not get offer tho.
