Senior DevOps Engineer with 8.5+ years of experience. Otherwise an avid artist, reader, cinephile & football fan. Looking forward to connecting with everyone :)
While you mentioned some valid points but I can tell you that candidates who ace those programming challenges aren't necessarily a better fit than ones who fare averagely.
Because most people are under duress to perform in an interview so they might blank out there but if evaluated humanely, they're often great problem-solvers and can handle crisis situations equally well. For all one can prepare, even the slightest thing can derail an interview.
Also, I disagree with your statement that coding challenges are solely about approaches and not about solutions since I've had multiple experiences wherein I got feedback my scores were too low inspite of me writing working programs that were logically and syntactically correct.
We want them to be so but often they're taken as the only yardstick to judge people.
Senior DevOps Engineer with 8.5+ years of experience. Otherwise an avid artist, reader, cinephile & football fan. Looking forward to connecting with everyone :)
That's very correct but I'm doubtful if companies will shed the approach of NOT counting those code challenges as the only criteria along with accounting for stress & anxiety. The ones that actually care, will have a ready pool of diverse candidates almost all the time.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
While you mentioned some valid points but I can tell you that candidates who ace those programming challenges aren't necessarily a better fit than ones who fare averagely.
Because most people are under duress to perform in an interview so they might blank out there but if evaluated humanely, they're often great problem-solvers and can handle crisis situations equally well. For all one can prepare, even the slightest thing can derail an interview.
Also, I disagree with your statement that coding challenges are solely about approaches and not about solutions since I've had multiple experiences wherein I got feedback my scores were too low inspite of me writing working programs that were logically and syntactically correct.
We want them to be so but often they're taken as the only yardstick to judge people.
I think you misunderstood some of my points because I didn't make them clear enough:
Most coding challenges are done wrong, not the way I described.
Coding challenges should never be the only criterion for selecting an employee.
Stress and anxiety have to be taken into account.
That's very correct but I'm doubtful if companies will shed the approach of NOT counting those code challenges as the only criteria along with accounting for stress & anxiety. The ones that actually care, will have a ready pool of diverse candidates almost all the time.