Taro Logo

Software Engineer Apprentice Interview Experience - United States

August 1, 2020
Positive ExperienceNo Offer

Process

Code Challenge - GCA on CodeSignal.

I was only able to complete 2 out of 4 questions during the allotted time (70 minutes), but I was still asked to continue.

Technical Phone Interview -

A 60-minute phone call involving collaboration over CodeSignal with an engineer, discussing two whiteboard problems. These were probably LeetCode medium difficulty and were all done with pseudocode.

Final Onsite Interview (remote due to COVID) -

This consisted of four different rounds, each with one interviewer:

  • System Design
  • Object-Oriented Design
  • Algo/Data Structures
  • 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 returned for a discussion about my implementation and opportunities for optimization.

Every single person I talked to along the way seemed genuinely excited to talk to me and collaborate. If I got stuck, they were empathetic and willing to support me.

I received a call from the recruiter about a week after my final interview. She informed me that I did not receive the position and walked me through each question with feedback from the interviewers. She provided very great and detailed feedback.

Questions

binary search tree

object-oriented game design

app design

matrix manipulation

Was this helpful?

Interview Statistics

The following metrics were computed from 5 interview experiences for the Asana Software Engineer Apprentice role in United States.

Success Rate

0%
Pass Rate

Asana's interview process for their Software Engineer Apprentice roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive80%
Neutral0%
Negative20%

Candidates reported having very good feelings for Asana's Software Engineer Apprentice interview process in United States.

Asana Work Experiences