3 ms·

> passing or failing on codility means nothing. it just means the company trying to interview you through codility has no idea how to interview you. I didn't s

> passing or failing on codility means nothing. it just means the company trying to interview you through codility has no idea how to interview you. I didn't say it was a fault with codility. Some companies, like your's, use it in a sensible way. But I think there are many companies which use this tool the wrong way. Anything except the easy level takes more time for someone who doesn't practice these kind of challenges every day. Moreover correct algorithm only scores 50%. 100% score can only be achieved upon perfect optimizing, which is very hard to do within 30 minutes. And your can't know which edge cases tests are failing until the solution is submitted after which its not possible to edit/correct it.

seanwilson 11y ago
Yeah, I'd always take the points you mentioned into account when reviewing a solution. Along with saving time I did find reviewing Codility submissions quite revealing. I've seen cases where the candidate couldn't get code to even compile, another where they didn't know Java includes map data structures existed (asked them in the follow up interview) and another where the implementation for an easy task was super slow when the nearly fastest approach should have been obvious (again, asked about in interview). I'd say it's better for identifying really unsuitable candidates than it is for identifying who are the best ones.