Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fui entrevistado pela Asana em abr. de 2018
Entrevista
A recruiter reached out to me on LinkedIn asking if I were interested in applying to Asana's Software Engineering Apprenticeship. She then sent me a coding challenge that allowed 1-hour to answer. The next week the recruiter asked to schedule a technical phone interview with a software engineer. That interview took about 1 hour and the interviewer did a great job and made it a fun experience even though I struggled through it. Two days later I got an email from the recruiter saying that they would not move forward with me and gave me some general feedback about my performance.
Perguntas de entrevista [1]
Pergunta 1
How would you check if a binary tree is a binary search tree?
Thank you for your review. We're happy to hear you had a fun interview experience!
Candidatei-me online.
O processo levou 2 meses.
Entrevista
I applied to Asana as soon as the process opened. Then I got a CodeSignal take home with 4 coding challenges. I solved 3 out of the 4 questions. Usually people that solves 1/4-2/4 gets to the next step. So I was excited about it. A week later I sent a follow up to the recruiter and she said she’d get back to me by the end of the week. Over a month later she sent me an e-mail saying that the role was filled and the process was closed. I asked her for a feedback since I did very well on my take home, I wanted to understand why I didn’t move forward. She said that it was more because of the volume of applications than my performance. So is this process a lottery? If the company can’t deal with that amount of applications why on earth they don’t close the application process before? Is it to show off how many people want to work for the company?
I hope a recruiter don’t bother to answer my review with “I’m sorry you had a bad experience, we’re working hard to make it better.” , since they didn’t bother to see my application and the results of my take home challenge. The most disrespectful process I’ve been through.
Perguntas de entrevista [1]
Pergunta 1
It’s been so long that I don’t even remember. I know it was 2 easy problems, 1 medium matrix problem and 1 hard problem. Just do leetcode and you’ll be fine.
Candidatei-me online. Fui entrevistado pela Asana em ago. de 2020
Entrevista
Code challenge - GCA on CodeSignal. I was only able to complete 2/4 of the questions during the allotted time (70 minutes) but I was still asked to continue.
Technical phone interview - 60 minute phone call collaborating over Code Signal with an engineer discussing two whiteboard problems. Probably Leetcode medium difficulty. All done with pseudocode.
Final Onsite Interview (remote due to COVID) - 4 different rounds each with one interviewer discussing system design, object oriented design, algo/data structures, and an informal chat with an engineer. The last round was a 2 hour session where the interviewer left me alone to code for 70 minutes then came back for a discussion about my implementation / opportunities for optimization.
Every single person I talked to along the way seemed to be genuinely excited talk to me and collaborate. If I got stuck, they were empathetic and willing to support me.
I got a call from the recruiter ~ 1 week after my final interview. She let me know that I didn't receive the position and walked me through each question with my feedback from the interviewers. She gave very great and detailed feedback.
Candidatei-me online. Fui entrevistado pela Asana (San Francisco, CA) em ago. de 2020
Entrevista
Leetcode type interview, followed by a more critical thinking game building scenario. Interviewer was helpful and they are looking for you to ask questions if you get stuck. Make sure you practice explaining your steps outloud.
