Me postulé en línea. Acudí a una entrevista en Asana (Vancouver, BC) en sep 2023
Entrevista
The interview was supposed to be for an hour but after waiting for the shadow interviewer and introductions, had only 45 minutes. My advice to you, don't waste time on introduction(about yourself). I had 45 minutes to solve two problems. One was a leet code easy to medium and the other was a code design pattern question.
- I was given 15 min to solve the leet code question. It was more of a conversation and I was asked to write in pseudocode but I wasn't really sure what pseudocode format they were expecting.
- The second question was more of a code design question based on a game. If you have never played the game or don't have context, I don't think you will be able to solve the problem. Understanding the rules, then coming up with a solution. Too many things in play here. I have 11 years of experience and I have taken a lot of interviews in my career, this was way too rushed. Luck has more play here.
But overall, I am thankful for the unique experience, will definitely help with future interviews.
Preguntas de entrevista [1]
Pregunta 1
- On leet code easy to medium based on array - One code design pattern, method signatures etc based on a game
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.
