Fork me on GitHub
#jobs-discuss
<
2021-09-14
>
danielglauser14:09:19

There has been a lot of discussion here on how interviews aren't an effective way of determining if someone will be a good dev on your team. I wrote up my thoughts, feedback is welcome: https://medium.com/codex/how-to-interview-software-developers-87239ca494ab

👍 2
dima15:09:53

cc @UQP60F2B1 that’s pretty similar to what we’re doing, but still interesting read.

👀 2
2
dima15:09:56

Thanks for sharing!

2
2
Darrell15:09:56

Great article!

🎉 2
Bobbi Towers17:09:43

Surprisingly, in over 4 years of searching for Clojure jobs, I've only ever been asked to live code once. The approach you describe, also once. Usually it's take-home tests.

2
👍 2
marciol22:09:46

In this sense the best approach I have seen in the Clojure land is the way Nubank approaches the problem. They give a take home exercise, but a really simple one, without any trap, it’s pretty simple and something that is related to what they do day-to-day, and along with it, they also require a System Design interview, and that is it. Sad to still see a lot of companies demanding full working complex software to be made at home or also obligating people to think at loud in live code exercises

sova-soars-the-sora19:09:30

Hey that's a neat idea. One company I interviewed at had a "take home test" that you could skirt if you sent in a public github repo to talk about. Seems reasonable.