TopTal, Codility, and skill testing
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
I've walked out of interviews for less.
If it's not broken, fix it until it is. Everything makes sense in someone's mind. Ya can't fix stupid.
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
I blame you for that cause that you made for yourself. Don't believe what you read and see from Internet. Shouldn't you remember it. Now that you disappointed me.
The best way to make your dreams come true is to wake up. Paul Valery
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
Marc Clifton wrote:
I got an email rejecting me because my score was low.
If you would have 1mln points on CP (and not lousy 500k) you probably would get the job :laugh:
No more Mister Nice Guy... >: |
-
I blame you for that cause that you made for yourself. Don't believe what you read and see from Internet. Shouldn't you remember it. Now that you disappointed me.
The best way to make your dreams come true is to wake up. Paul Valery
Stephen Gonzalez wrote:
Now that you disappointed me.
Given I'm reading this on the Internet, I don't believe you. ;) Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
-
Stephen Gonzalez wrote:
Now that you disappointed me.
Given I'm reading this on the Internet, I don't believe you. ;) Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
I was really disappointed. But you beat me with my own post. Well played. :)
The best way to make your dreams come true is to wake up. Paul Valery
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
Actually had 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) in a class forty years ago. Did not get it then either. :-O
Mongo: Mongo only pawn... in game of life.
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
Maybe TopTal is looking for people to work on their chess app for (very low memory) embedded systems. Knowing how to play chess with the least amount of moves and bits is really important in such solutions! :D That's really the only logical explanation I have for such screening processes anyway. That and "company policy states we screen at least x candidates every month."
Read my (free) ebook Object-Oriented Programming in C# Succinctly. Visit my blog at Sander's bits - Writing the code you need. Or read my articles here on CodeProject.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
My last coding test was done via codility that had 3 problems too. I solved the first one, and Codility reported it couldn't be bettered (performance, correctness). Solved the second one as well, but it nitpicked on some edge cases (wouldn't tell me what the test cases are) and as a result the score was a little less. I simply didn't have enough time to do anything with the third one. I sent a detailed email to the hiring manager (who is a developer as well), and included my code in it. I was asked to come for a face to face interview and coding test later in the week, which was a very well structured code interview with two top nerds. I was offered after the interview, and I now work here. But I do understand there may be companies who use sites like codility as their sole interview (or coding test) tool, which is rather sad. I have interviewed with a few such companies, and was told by one of them that I simply didn't make the cut. A year later, the same recruiter called me up to check if I was looking for a job change (I told him off) because they still haven't "filled that position". No wonder.
-
My last coding test was done via codility that had 3 problems too. I solved the first one, and Codility reported it couldn't be bettered (performance, correctness). Solved the second one as well, but it nitpicked on some edge cases (wouldn't tell me what the test cases are) and as a result the score was a little less. I simply didn't have enough time to do anything with the third one. I sent a detailed email to the hiring manager (who is a developer as well), and included my code in it. I was asked to come for a face to face interview and coding test later in the week, which was a very well structured code interview with two top nerds. I was offered after the interview, and I now work here. But I do understand there may be companies who use sites like codility as their sole interview (or coding test) tool, which is rather sad. I have interviewed with a few such companies, and was told by one of them that I simply didn't make the cut. A year later, the same recruiter called me up to check if I was looking for a job change (I told him off) because they still haven't "filled that position". No wonder.
years ago I ran a group for telcomm. We did a lot of bit twiddling. Q1) what is the largest unsigned number in a byte? Many a candidate with a masters degree in Comp Sci just stared at me. After 60 seconds, I walked them through 2^8-1, etc. Oh, their faces brightened. spoiler: 255 for all you java and vb dudes out there ;) Q2) what is the largest unsigned in a word? clarification: yes, 16 bits, 2 bytes. anyone want to guess how many times candidates said 510? :wtf: Algorithms knowledge should show some basic understanding of the tools available to you. But I've dealt with enough bullshit magic code from really smart people over the last 5 years I want to take that algorithm book and shove it some place... If you're looking for a job, you need a network. I hope Marc learned his lesson. These questions are just stupid crap. Go look at the way Windows 7 does recursive dependency evaluation for patch updates. There's a guy that knows his algorithms - very useful for polishing a turd.
Charlie Gilley Stuck in a dysfunctional matrix from which I must escape... "Where liberty dwells, there is my country." B. Franklin, 1783 “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
Remember our discussion on how developers are like players on a sports team? Here we go again! Haven't yet found an objective way to measure a developer's abilities so the whole exercise of trying to test candidates is pointless. Developers respond to different problems in different ways. There isn't always the 'right' answer. Developers have good days and bad days; their programming form comes and goes. Some are really good at parsing strings. Others are really good at implementing user interfaces. Some developers do well in a particular team. Others crash and burn because of a personality clash. Some enjoy being under pressure, or turning out a solution quickly. Others want to take the time to get the best solution possible. Some are good at testing. Others at finding and fixing obscure faults. Most are crap at writing good documentation. Nearly every one has their own interpretation of what requirements mean. Or what makes good UI design .... The most corrosive aspect of testing, or trying to compare developers, is that it can erode a developer's confidence in their own skills. Just like a striker on a soccer team, confidence is a major component of success. You can't measure that.
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
I agree that TopTal sucks. I thought they had some kind of system or process of their own for evaluating the skill level of programmers, but relying on one automated test with no human oversight is pretty stupid. However I see no problem regarding Codility. There are multiple things you would want to look for in a programmer. The things you mentioned, such as OOP practices, DB architecture and similar technical abilities are usually evaluated thoroughly in the technical interview. I believe TestDome may have some more technical questions than Codility, but then again both platforms have lots of test questions so they may have both kinds. But for some programming positions, evaluating the ability to think algorithmically and figure out the "trick" can be crucial. This can be necessary in AI programming for example. The problem here is not the tests themselves, but the way they are administered, and to whom. A test and it's questions may be useful for some candidates applying to certain positions but may be useless in other contexts. Another important factor is to not rely solely on the automatically evaluated results of these tests, but to have an actual developer look at the code. Not to mention that these tests are not meant to be the sole proof of someone's skill, but are generally intended to be one part of the screening process, where the technical interview usually follows.
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
I took the toptal test as well and ended up failing due to "additional" requirements not shown on the test. Of course the test itself is, as you point out, really just a series of questions that have no meaning related to programming. It's too bad that companies fall into these traps of thinking that tricky math questions can show whether you can program or not. I myself tried this in the past with people I hired, and found out the hard way that you end up with people who show off well, but do not have good coding skills. mvarey
-
Remember our discussion on how developers are like players on a sports team? Here we go again! Haven't yet found an objective way to measure a developer's abilities so the whole exercise of trying to test candidates is pointless. Developers respond to different problems in different ways. There isn't always the 'right' answer. Developers have good days and bad days; their programming form comes and goes. Some are really good at parsing strings. Others are really good at implementing user interfaces. Some developers do well in a particular team. Others crash and burn because of a personality clash. Some enjoy being under pressure, or turning out a solution quickly. Others want to take the time to get the best solution possible. Some are good at testing. Others at finding and fixing obscure faults. Most are crap at writing good documentation. Nearly every one has their own interpretation of what requirements mean. Or what makes good UI design .... The most corrosive aspect of testing, or trying to compare developers, is that it can erode a developer's confidence in their own skills. Just like a striker on a soccer team, confidence is a major component of success. You can't measure that.
-
Marc Clifton wrote:
How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?"
This is a great question. Is there any way for a site to determine your level of ability without having some human intervention? Can a test be given which is graded by a computer and accurately tests someone's skills?
There are only 10 types of people in the world, those who understand binary and those who don't.
(Automated) Function Point Analysis as a measure of the "scope" / magnitude of the applications one has designed and / or developed. Is designing and building entire mission-critical "systems" "better" than being good at (just) algorithms? Who needs who?
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
Marc Clifton wrote:
the point in which in an array, the count of X from the left != count of X from the right.
Count of X as in the number of times X appears?
Regards, Nish
Website: www.voidnish.com Blog: voidnish.wordpress.com
-
Just to get this out of the way, I failed the TopTal[^] application. How did I even find TopTal? In the CP newsletter! TopTal's primary screening process is to use Codility[^] to see how good your skills are. Now, the 90 minute timed test at Codility asked me to solve three problems: 1. the point in which in an array, the count of X from the left != count of X from the right. 2. given some bit encoding scheme, convert N to -N with the least number of bits. 3. the optimum number of moves a chess knight must make to get from (0, 0) to (m, n) Regarding the last, someone here at posted about that idiocy of that actually testing coding skills. In fact, they all are extremely poor tests of skill. Each (particularly #2 and #3) probably involve a simple trick to figure it out, and if you don't know the trick (like me) you're spending a lot of time just thinking about the problem. At least I was. :) How exactly does solving an arbitrary algorithm test coding skills? How does it demonstrate good OOP practices, or DB architecture skills, or an understanding of Linq, or really much else other than "getting the trick?" After working hard at #1, writing assertions, commenting the code, testing edge cases, optimizing the algorithm for O(1) performance, I realized I had spent an hour on one stupid problem. That left 30 minutes for the remaining two. Riiiight. Now, Codility says something like "don't worry if you don't complete all three tests, just show your best work, even if you only complete one test." And then the test results are amusing. The requirements don't state what to do with incorrect inputs into the "solution" method, and they clearly can't handle exceptions being thrown -- I noticed my score in their example test dropped dramatically when I used exceptions. Now to TopTal. I got an email rejecting me because my score was low. It was pretty darn obvious that no one had even bothered to look at my code! That REALLY :mad: me. TopTal: :thumbsdown: Codility: :thumbsdown: Anyone that uses Codility: :thumbsdown: Sadly, this sort of crap testing methods is probably going to be used more and more. Oh, and Codility has an "honor system" where you won't talk about their tests. F*** them. They should come up with better tests! Mar
I hire online developers (in a small way). My teenage son (a keen developer), a couple years back, tried to get me to hire people from TopTal. "No way", I said, "they are all pose".
