marcgg

I'm sorry to hear that. This is of course not normal, could you please let me know where you sent it? We look at all applicants' tests sent via our job page, and if yours got lost then it's an error that I'd be happy to fix.

Mail: marc at drivy dot com

We saw some issues that seemed like a possible aws outage, but can't really confirm it

As I mentioned in the article, we don't expect the code presented to be "perfect" code. If you've managed to get a side project running very quickly thanks to tradeoffs you've made, it's also interesting. It's really just a way to have a place to discuss choices.

I completely agree, this was just an example of a common complain.

Yes it's true that it doesn't fit all use cases. However I would see looking at a few of the fixes you're talking about as an interesting technical interview.

From experience we saw that for most people doing the coding test was only taking ~an evening which seems reasonable as it removes the need for more on site discussions.

I guess that it's true that the take home assignment is not optimal if you interviews with more than 10 companies and in this case we must be loosing some candidates.

Sometimes we do discuss this code if the candidate prefers. But it's still a somewhat "fake" code made for the only purpose to apply at the company. Most people would find it more interesting to discuss code they spent weeks on.

Finally we are not looking for any specific profile, but so far almost every person found a piece of code to share from their career. We don't get thousands of applicants, so maybe we're not seeing the issue just yet. If it turns out to be a problem, we'll change the process :)

I never said our interview process was perfect, I mainly wanted to share it because I saw a lot of people complaining about whiteboard coding and so on... so I figured it could be interesting to some to see a less exhausting alternative.

Thanks! So far it's been also very interesting on our end to discuss "real life" problems

We accept any kind of code, be it a kata made during a workshop or a side project... really we just want to talk about code that the candidate wrote previously. It doesn't need to be large to have interesting tradeoffs made

If you sum it all up, it is less than a day. The phone screening is ~20 minutes, the assignment takes a couple of hours and so on.

I think it's fair to expect that a candidate is willing to invest at least 5-6 hours in an interview process. Compared to what I've seen before (full day interviews, freelance period etc) this seems fair to me. But like you comment proves, it might not be for everybody.

I don't think that there much one can learn by looking at a couple of classes. On our end we let the candidate decide based on their previous company's policies.