Re:Hiring technical talent: An exercise in clarity, patience...
by tech_tuna on Friday May 13, 2022 @09:22PM
(#31374231)
Just went through a round of interviewing. . . it's laughable how the coding interviews go. I did well on some, OK on others and bombed a few too.
Yet, in every case, the interviewers put so much weight and faith in the coding challenges. I'm like really people? Can you really tell how good or bad I am in a 35 minute live coding challenge? When I'm working I sometimes make mistakes, sometimes many mistakes and then other times, I crank out a lot of decent code with few mistakes.
Re:Hiring technical talent: An exercise in clarity, patience...
by lordnacho on Saturday May 14, 2022 @04:01AM
(#31375978)
In particular poor code is often only visible as unwieldy architecture. How someone does a little coding challenge does not tell you how they put the whole together, whether that's good or bad.
Re:Hiring technical talent: An exercise in clarity, patience...
by sicp-enjoyer on Friday May 13, 2022 @08:42PM
(#31374032)
I largely agree, although I have known a strange number of people who like talking about tech and programming, but then can't do basic programming tasks. I don't think it's the norm, so perhaps a good conversation is as good a filter as any.
Just a conversation is what I've always found worked. Just two people in the same business discussing some technical topic. What do you like about Rust? Why would you write this system in Java? Blah blah, and if the person doesn't actually know much they will run out of things to say. Sprinkle in some references to ordinary tools like git or gcc, and you can't avoid using industry jargon that will function like a shibboleth. If they know how to do stuff they will know the words you throw at them and throw back some of their own. If they read around their area they will know what the adjacent areas are and they'll have opinions and more keywords. It's not actually simple to make this up, for instance how would you pretend to be a surgeon or a pilot? There'd be a bunch of things you'd have to have heard of, and there isn't going to be a shortcut to knowing what they meant.
If they're a bullshitter and they somehow manage to blag themselves a job, they will get found out pretty quickly anyway, definitely before the probation period ends.
If they're someone who understands stuff, they'll appreciate talking to a technical peer and that will be part of the draw of working with me.