When I interview (experienced) devs, I often ask way too generic questions. Something along the lines of "can you explain what a hash is?", without stating what kind of hash and in what context

The primary goal isn't really to explain it in detail, but to see if they get confused and ask for clarification. Way too many people just start assuming something, when a task is not defined properly. I need coworkers that push back on bullshit, and not blindly implement whatever runs along their desk, no matter how little sense it makes

If I don't hear at least one "it depends" during an interview, I don't have high hopes

[–] xianjam@programming.dev 9 points 2 days ago (6 children)

So, to start off, I'm someone who does not typically perform well during interviews because of anxiety (but through some miracle has had no issues with employment), so take this response with whatever bias that brings.

I believe this is bad too. You're still essentially asking a gotcha question, expecting one phrase in your answer and failing the candidate if you don't hear that phrase. And, in fact, I disagree with the premise. I think the question is defined quite well in the context of programming, given that someone answers with the possibility that there are many ways to hash something and many uses of hashing.

[–] Ruusunmarja@lemmy.blahaj.zone 1 points 2 days ago

Well, he did say ”push back on bullshit” soo congrats? 🤭

load more comments (5 replies)

load more comments (34 replies)