After an initial check-in call will a recruiter you get invited to take an exercise at home (writing a client for a fake API they provide). The good part is that there is no time limit for submitting the test, but the review process left me totally puzzled. After providing extensive unit and behavior test suite (especially on sad paths) with full test coverage, a perfectly working client, documentation and even a working example on how to use it all i got was a rejection with three reasons that didn’t make real sense if you take a look at the code. I spent 3 full days at reading over and over again those rejection reasons and well, they still just don’t make any sense since what they said it isn’t what’s inside the code. This is a very demanding test if you want to make it very well, and therefore it is unacceptable to get rejection on something that just doesn’t exists or is just pure personal and biased preference. I think that they use the test to see if you code like they want/expect, rather than understanding if you really can code or not and know what you are doing. At this point all I can say is that I should feel lucky I got rejected. Watch out candidates, huge risk of wasting your of time.

It was a pretty straightforward process. One screening interview, a take home exercise, and a technical interview. The technical interview has different levels of complexity, from discussing the exercise implementation to infrastructure decisions.