|
by Rafiki 05/07/2018, 9:05pm PDT |
|
|
|
|
|
Ice Cream Jonsey wrote:
I am against the current trend of giving developers 8 hours of homework to complete because if the spot you're hiring for is THAT critical that you absolutely cannot afford anyone but a top notch developer then you should bring someone on from your goddamn network who you know is good
We wouldn't do this if it weren't depressingly obvious it was necessary :( We give 3 questions that I seriously think even a CS undergrad should be able to finish in no more than 2 hours, and we give them 2-3 days to submit their code because we understand people have lives and families and other things going on. None if it is intended to be super complicated or require hours of problem solving, it's just to see if they understand core concepts and see how they write and structure code. Knowledge gaps are annoying because you want everyone who sets foot in the door to magically know everything, but you can get most people up to speed on things they haven't worked with inside half an hour and then review their work once in awhile to make sure they're on track. But if they don't understand basic concepts in the field, then we don't have time to reteach a CS degree and wait for months of practice for it to sink in.
I guess the theory is that if there is a time constraint then it, I dunno, simulates being able to do it quickly?
I don't know about that test in particular, but I figure a lot of time limits are because they believe if you give people too much time they can get someone else to answer for them or ask a bunch of questions on stackoverflow or something.
You can interview for some things and screen out the ones lying on a resume but you can't interview for drive. You can't interview for someone who when a couple people are stuck that are in a critical path, unsticks them. You can't interview for the person that gets every one of their features done and tests it first. I feel you can only interview up to a certain point of competence. After that, it's all personal ethics and drive.
We haven't even gotten to the point of reaching the limits of interviewing for competence. This is in the Midwest, so nobody wants to work here, and the 3 people we did get apparently only know how to make the red squiggles go away like Koba said. I don't want to be an overly-judgmental douche (which is why I made that poll, not to shit on some random stranger), because despite me talking out my big fat mouth like I Know Shit *grabs belt, triumphantly adjusts pants*, I know I'm not a top-notch developer so I can't hold people to that standard. I want to be reasonable, but these "people," IF YOU CAN EVEN CALL THEM THAT, make it hard. They don't even have the decency to be hot and slutty or hot and gay. Literally nothing to offer. |
|
|
|
|
|
|
|
Adventures in Hiring by Rafiki 04/24/2018, 8:20pm PDT
Re: Adventures in Hiring by Fullofkittens 04/25/2018, 7:26am PDT
Yeah, GPAs and degrees are worthless. Only consider if they have <3 years' xp. NT by The Happiness Engine 04/25/2018, 12:21pm PDT
This thread is helpful for making the jump from freelance to white collar work. NT by saltlord 04/25/2018, 12:45pm PDT
Next you’ll tell me I shouldn’t disqualify people that don’t play D&D or L by Rafiki 04/25/2018, 1:49pm PDT
Ha. So very, very true. Candidates are so bad. by blackwater 04/25/2018, 1:20pm PDT
A poll for programmers by Rafiki 05/04/2018, 3:15pm PDT
Re: A poll for programmers by E. L. Koba 05/04/2018, 5:50pm PDT
They use String after being explicitly told not to. NT by DQ 05/05/2018, 8:40am PDT
Yeah, tough to defend this one. NT by Ice Cream Jonsey 05/06/2018, 10:19am PDT
Re: A poll for programmers by Ice Cream Jonsey 05/05/2018, 1:20pm PDT
Re: A poll for programmers by Rafiki 05/07/2018, 9:05pm PDT
Re: A poll for programmers by Ice Cream Jonsey 05/08/2018, 5:51am PDT
"Automator" is a cool-sounding job title NT by blackwater 05/08/2018, 12:06am PDT
My first cheater! by Rafiki 06/11/2018, 8:32am PDT
|
|