Whenever possible, I love to talk with a candidate about some concrete past source code they claim to have written. I've better luck putting the candidate at ease and then talking through their contributions to the code.

Of course, when I get enough candidates who shared source code, I don't even invite the ones who didn't share source code for an interview.

[–] undefined@lemmy.hogru.ch 5 points 9 hours ago

I thought my entrance test was far too easy, I only had to create a blog in my web framework and show doing the basics like validations, secure parameters, etc.

I learned later on that most couldn’t pass because they came from other languages and thought they could get by without knowing anything.

[–] Cano@lemm.ee 14 points 12 hours ago (1 children)

That's an instant ego boost

[–] mosiacmango@lemm.ee 17 points 12 hours ago (2 children)

Should working code even be part of an interview? Seems like a situation rife with abuse.

Need free contractors? Just put your code issues up as a 4hr take home interview test.

[–] Karyoplasma@discuss.tchncs.de 15 points 11 hours ago

Pseudocode/general thought process walkthrough should be the only thing imo. Oh no, the interviewee forgot a semicolon, so he is trash at coding and is a no-fit is complete bullshit.

[–] Dudewitbow@lemmy.zip 6 points 9 hours ago

how the applicant thinks breaks down problems and handles how to answer them matters more than if the code is actually functional on the spot

[–] BlackLaZoR@fedia.io 2 points 12 hours ago

One guy completed it, so it was just perfect