6 ms·

> Always ask the candidate to walk you through the repo line by line! That seems a bit much, you're liable to scare away good talent that way.

Gustomaximus 8y ago
Coudnt that be easily managed by saying: "Sorry about this but we've had some candidates passing others code as their own. So we've been asked to take all candidates through some code line by line. Such a pain but we have to do it unfortunately. Ill try and get through quickly. You dont mind do you?"
- reitanqild 8y ago
  And if there is a need for follow up, some variation of "we quite clearly are interested in you and value your time since we spend actual engineer hours walking through your code. What would be disrespectful was if we ignored all your hard work and hired someone not half as good as you because they had more glowing reviews or more stars on their repos." Obviously I'm no hiring manager, but often a bit of honesty goes a long way.
- AJ007 8y ago
  A bad employee in a small company (or organization of any type) can do a lot of damage. It is negligent to hire someone who hasn't proven they can do what they claim, and negligent for a manager to not verify they aren't doing the work they claim to be doing.
stingraycharles 8y ago
I do try to talk a lot about their own projects during interviews, though, since I can only assume they like to talk about it. And it can lead to very interesting discussions, you learn a lot about a candidate that way.
- deleted 8y ago
  [deleted]
anonymous5133 8y ago
Good talent will enjoy walking you through their hard work!
- jl2718 8y ago
  I agree. Like gramma talking about her babies.
gaius 8y ago
you're liable to scare away good talent that way People, in general, like to talk about themselves, and engineers like to talk about their own code. "See this if statement, well there's a funny story behind that...". A few years ago I interviewed a candidate who mentioned Github on her CV but no actual URL. What's your username on there, I asked, let's look at some of your code. She refused and said she didn't want me to look at it. Then why did you mention it on your CV I asked? Because she was told she had to, she said. All in all a weird experience, probably for both of us.
anonnyj 8y ago
Really? That sounds super stress free for me. Maybe it's just that I'm super confident about my own code and know it inside out? A white board test on the other hand would literally cause me to run away... Of course I've never coded in a professional capacity, so don't mind me if I said something stupid.

Gustomaximus 8y ago

Coudnt that be easily managed by saying: "Sorry about this but we've had some candidates passing others code as their own. So we've been asked to take all candidates through some code line by line. Such a pain but we have to do it unfortunately. Ill try and get through quickly. You dont mind do you?"

reitanqild 8y ago
And if there is a need for follow up, some variation of "we quite clearly are interested in you and value your time since we spend actual engineer hours walking through your code. What would be disrespectful was if we ignored all your hard work and hired someone not half as good as you because they had more glowing reviews or more stars on their repos." Obviously I'm no hiring manager, but often a bit of honesty goes a long way.
AJ007 8y ago
A bad employee in a small company (or organization of any type) can do a lot of damage. It is negligent to hire someone who hasn't proven they can do what they claim, and negligent for a manager to not verify they aren't doing the work they claim to be doing.

stingraycharles 8y ago

I do try to talk a lot about their own projects during interviews, though, since I can only assume they like to talk about it. And it can lead to very interesting discussions, you learn a lot about a candidate that way.

deleted 8y ago
[deleted]

anonymous5133 8y ago

Good talent will enjoy walking you through their hard work!

jl2718 8y ago
I agree. Like gramma talking about her babies.

gaius 8y ago

you're liable to scare away good talent that way People, in general, like to talk about themselves, and engineers like to talk about their own code. "See this if statement, well there's a funny story behind that...". A few years ago I interviewed a candidate who mentioned Github on her CV but no actual URL. What's your username on there, I asked, let's look at some of your code. She refused and said she didn't want me to look at it. Then why did you mention it on your CV I asked? Because she was told she had to, she said. All in all a weird experience, probably for both of us.

anonnyj 8y ago

Really? That sounds super stress free for me. Maybe it's just that I'm super confident about my own code and know it inside out? A white board test on the other hand would literally cause me to run away... Of course I've never coded in a professional capacity, so don't mind me if I said something stupid.