I failed a C++ test that was a requirement to get a job (30 minutes timed, multiple choice). I had written a C++ application that I had sold to thousands of customers (Fortune 100s in there too). I had mistakenly thought I could be a programmer at a real job.
Later, I sold $20,000 worth of source code that took me 60 hours to produce. The client thought it was easy to read.
I still don't think I'm a real programmer. The test sure seemed to prove that. But, people still buy my software today (I have other apps).
From my perspective, it seems the current technical interviews are looking for something in particular, from which you don't later actually do that for the real job. Kinda like seeing if you can survive a skydive, but you'll actually only be packing chutes after hire.
I wish there was a way to say, up front, that there are different types of programmers, vs the catch all "programmer" job title. Because it sure seems like I'm typing out code. The computer has always accepted it.
I would not get too hung up on those multiple choice tests.
I've been programming professionally now for over 25+ years and ran into my first multiple choice test about 4 years ago.
In a very short space of time I managed to failed three (two C# and one C++) in quick succession.
Now days, if I come across a role that requires such a test I just politely refuse and move on.
FWIW why I think these test are a waste of time and why I did so badly is because they don't actually test day to day programming skills.
The three test I did where all very similar with a lot of gotcha type of questions.
They asked questions like spot the obscure error in a very poorly written piece of spaghetti code, or tell me exactly what exception this code will throw exception etc.
As a programmer you never have to directly deal with these types of issues only because your compiler finds the errors and the documentation gives you exception details.
And in a way the tests knew this as well, because all three warned you could not switch out of the test window while doing the test.
In other words the test would have been a trivial exercise if you where actually allowed to use your day to day work tools.
I wouldn't take it personally. Language-specific tests sometimes focus on memorizable trivia instead of problem solving. Like, "How many generations does the garbage collector have?"
Later, I sold $20,000 worth of source code that took me 60 hours to produce. The client thought it was easy to read.
I still don't think I'm a real programmer. The test sure seemed to prove that. But, people still buy my software today (I have other apps).
From my perspective, it seems the current technical interviews are looking for something in particular, from which you don't later actually do that for the real job. Kinda like seeing if you can survive a skydive, but you'll actually only be packing chutes after hire.
I wish there was a way to say, up front, that there are different types of programmers, vs the catch all "programmer" job title. Because it sure seems like I'm typing out code. The computer has always accepted it.