6y
This is pretty rough to read because it doesn't reflect the team's perception of the interview and my own either. Reading your review, I can see that this was a very painful experience for you and that is not at all how I or anyone here wants the interview process to be even for interviews that don't go well.
I was called in to switch gears because none of the questions up until that point were completed successfully and the team did not know how to proceed. The Trello exercise is not generally a part of our interviews but I introduced it because I wanted to see if we could start from first principles of how you break down a task, ask questions to define requirements and then tackle a common workflow we deal with -- taking a design and figuring out how to organize the UI components necessary to build it. Sometimes interviews get caught in a rut and it seems like this is the case because this exercise also did not ultimately go well.
Perhaps where this might have gone wrong is when I tried to nudge you towards the right answer because I appreciated getting hints when I hit a wall in interviews. It is clear that this was not well received and I will definitely not be doing that in future junior interviews to avoid anyone feeling like it was controlling. I tried to explain what we were looking for at the end of the interview because that is what I would have appreciated but it seems that this too was not the right move.
Overall, I am sorry that you had a negative experience interviewing here. As I mentioned, that is absolutely not what we want. We want a challenging, fun experience that stretches your capabilities and is an accurate reflection of the type of work that we do here on a day to day basis. Based on the feedback from this as well as positive interview experiences we are redesigning our interview process and I hope that it will better showcase candidates' interests, skills and general awesomeness.