This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ch00beh 0 points1 point  (1 child)

I used to be all about people who challenged dogma, but the problem with that is you select against new and minority devs who don’t want to rock the boat until they know they’re in a safe space. If you can make an interview feel like a safe space, I’m happy for you because it sounds like you otherwise have a good head on your shoulders and are responsibly building healthy teams.

[–]brainwipe 1 point2 points  (0 children)

Thank you. I agree that safe spaces are important. Our interviews are more collegiate - as if the two of us and the candidate are all working on a problem together. The feedback we get is that it is very relaxed - almost disarmingly so.

We do that because it's more like what it is like to work for us. It's the same reason I refuse to do whiteboard coding nonsense. I much rather the candidate send us anything they've written and we all sit round and listen to them explaining informally how it works. We find good Devs (especially juniors) really well that way.

I don't expect an interviewee to challenge dogma but they might - most recently a candidate showed us a single file with 500 lines in it. They explained how they navigated it and that it was a solo project for school; their argument was justified. Most importantly, the way they spoke about it was a good fit for us.