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 also had an

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 also had an interview stage on codility. solved 3 puzzles in 60 minutes. in next round of interview i was again given another puzzle via screensharing. i took 40 minutes to solve it. did't make it. point being it is probably not a good company to work at. Don't feel bad. Try somewhere else with a proper resume/portfolio showing your achievements. codility for code challenges once in a while, yes. if its used just to see how you approach a problem and try to solve it, its good as it have nice code replays for the interviewer. But some companies want you to solve some random hard codility puzzle in 30 minutes or else you are no good

seanwilson 11y ago
> 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. It's a decent enough way to filter out obviously bad candidates without eating up your time (which is a big deal for small teams). I've used Codility for interviewing and being interviewed before and thought it was fine. I would only reject a candidate if they got say less than 50% and the problems chosen weren't too difficult. If a company is going to be expecting 90% pass rates for super hard problems the rest of their interview process is probably faulty as well; that's not the fault of Codility.
- rubberstamp 11y ago
  > 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.

seanwilson 11y ago

> 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. It's a decent enough way to filter out obviously bad candidates without eating up your time (which is a big deal for small teams). I've used Codility for interviewing and being interviewed before and thought it was fine. I would only reject a candidate if they got say less than 50% and the problems chosen weren't too difficult. If a company is going to be expecting 90% pass rates for super hard problems the rest of their interview process is probably faulty as well; that's not the fault of Codility.

rubberstamp 11y ago
> 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.