4 ms·

Again - I fail to see how the second part is derived from the first. If I'm already engaging in a screening process, wouldn't it be better to ask the candidate

by maxk42 5y ago

Again - I fail to see how the second part is derived from the first. If I'm already engaging in a screening process, wouldn't it be better to ask the candidate to solve a problem that relates to their role than to ask them if they've done any blogging on the topic of tech?

azinman2 5y ago
Because it gives you a more rounded sense of the individual. Other passions. Other ideas. Areas they’ve worked in unrelated to your problem. Job/coding interviews are very difficult to do well, and many people such as myself tend to perform poorly due to the stress of the interview (so much that I’d rather stay in a mediocre position than go through the agony of interviewing — I hate it with every fiber of by being, and it correlates 0% to my in-job performance). It’s just more data, which is especially useful if you’re on the fence with someone. You can also see creativity which isn’t something you can test well for in an interview — especially technical interviews.
- EvilEy3 5y ago
  > it correlates 0% to my in-job performance False. It correlates directly to your job performance, unless you're YAML developer.
  - azinman2 5y ago
    My ability to solve an artificial problem on a whiteboard time limited with a gun to my head correlates directly to my job performance? Not only does it not in my case, I don’t know how you could even make such a claim without knowing me, my work, and how I perform in such interviews… and that’s just me. Much has been written on this subject with similar anecdotes as well as quantitative research done by Google’s HR department. Clearly 0% is an exaggeration at large, but it’s well documented to be a poor correlate.
simonw 5y ago
Being able to write and communicate clearly is an important skill for software engineers, especially in senior roles - and it's something that's difficult to evaluate in an interview setting. Interviews don't tend to include writing - and strong communicators who get nervous during interviewers may end up at a disadvantage.
wpietri 5y ago
I think you're missing the "stand out" part of this. I've done a lot of tech interviews lately, which is where I get at ability to do the work. But when a hiring team is trying to pick among the people who do approximately as well on that, then other factors can help. At that stage, I definitely like to see things that indicate people are excited about something enough to just make a thing (a library, a small project, a blog post). If that's related to our domain or tech stack, even better. But even without that it's a plus in that it's a sign I can just give them a user problem or a technical issue and trust they'll go off and do something good with it.
wyager 5y ago
By the time you've gotten someone in an interview you've already committed a huge amount of effort towards them. Seeing a cool project someone made is a very strong signal that interviewing them won't be a waste of time.

by maxk42 5y ago

azinman2 5y ago

Because it gives you a more rounded sense of the individual. Other passions. Other ideas. Areas they’ve worked in unrelated to your problem. Job/coding interviews are very difficult to do well, and many people such as myself tend to perform poorly due to the stress of the interview (so much that I’d rather stay in a mediocre position than go through the agony of interviewing — I hate it with every fiber of by being, and it correlates 0% to my in-job performance). It’s just more data, which is especially useful if you’re on the fence with someone. You can also see creativity which isn’t something you can test well for in an interview — especially technical interviews.

EvilEy3 5y ago
> it correlates 0% to my in-job performance False. It correlates directly to your job performance, unless you're YAML developer.
- azinman2 5y ago
  My ability to solve an artificial problem on a whiteboard time limited with a gun to my head correlates directly to my job performance? Not only does it not in my case, I don’t know how you could even make such a claim without knowing me, my work, and how I perform in such interviews… and that’s just me. Much has been written on this subject with similar anecdotes as well as quantitative research done by Google’s HR department. Clearly 0% is an exaggeration at large, but it’s well documented to be a poor correlate.

simonw 5y ago

Being able to write and communicate clearly is an important skill for software engineers, especially in senior roles - and it's something that's difficult to evaluate in an interview setting. Interviews don't tend to include writing - and strong communicators who get nervous during interviewers may end up at a disadvantage.

wpietri 5y ago

I think you're missing the "stand out" part of this. I've done a lot of tech interviews lately, which is where I get at ability to do the work. But when a hiring team is trying to pick among the people who do approximately as well on that, then other factors can help. At that stage, I definitely like to see things that indicate people are excited about something enough to just make a thing (a library, a small project, a blog post). If that's related to our domain or tech stack, even better. But even without that it's a plus in that it's a sign I can just give them a user problem or a technical issue and trust they'll go off and do something good with it.

wyager 5y ago

By the time you've gotten someone in an interview you've already committed a huge amount of effort towards them. Seeing a cool project someone made is a very strong signal that interviewing them won't be a waste of time.