Credentials are only as good as the trust other people put in them. And I'd guess that a good portion of interviewers are completely unaware that non-athletic Olympiad competitions exist.
And anecdotally, it seems like tech interviewers wouldn't believe you could code your way out of a paper bag even if you walked into the interview over rose petals thrown on the floor by Kernighan and the ghost of Ritchie. I've had plenty of them remark "you are the only candidate that has answered that question correctly" and then never speak to me again.
It really makes me wonder what the point of the technical portion of the interview really is. I have had only one interview where the interviewer actually cut short a technical screen because "clearly, you know your stuff". But no offer there, either.
Which of course isn't true but good luck convincing people otherwise. (Source: regular clean up jobs after all the money has been spent and the company is on the skids and I get called in at a very large multiple of what an 'A' player would have cost to clean up the mess. I don't mind, it keeps me employed and brings home the bacon but it certainly does not seem to be the most efficient way to run an IT department...)
Unfortunately, the only solution I found for this is "charge more", which seems to be psychologically difficult for programmers, with all of patio11's efforts :)
I think "A" players are the best bargain in the software world...
They are, but try explaining to your average PHB who doesn't even begin to understand the complexities of the 'simple' piece of software they intend to write that Charles here can do the job in 3 months and will cost 50K and that the five guys over there in the corner will take the job for 30K and will take a month longer (or so they think). Then, after 30K becomes 90K and the company is slowly sliding downhill that original 3 months and 50K estimate starts to look pretty good, but then the sunk cost fallacy kicks in and for an additional 10K (over the 90K) this time they'll get it right. And then finally the time will be up, the money will be gone and they'll have to shop for someone who will take on the task to fix it on a contingency basis in the next month or so.
This plays out over and over again for some strange reason.
So yes, A players are a bargain, but only after the money to pay for them has been pissed out the window.
1) The market has imperfect information. The expensive developer could be great or terrible, but the same is true for the inexpensive developer. Even if there is theoretically some way to tell the difference, most employers don't have the skills to do so.
2) Bad management is at least as likely to kill a project than bad developers, so even a developer who is 10x in theory will on average deliver much less than 10x in practice.
(2) Very true.
I have had the exact same experience. I will get comments like, "That's the best submission we've seen for that take-home test" followed by literally no response of any kind after that. I've had places say, "you are absolutely perfect for our needs on Team X and you will help us meet our deadlines by the end of the year" and then make a job offer with a salary less than 80% of my current salary, worse equity, and worse benefits.
Companies sometimes want on-paper credential, but they almost never care about actual productivity or talent.
Stop right there :-)
I think that's where you need to do some deep introspection.
There's A LOT more to a job than technical aptitude. It appears that you're excelling in one aspect of the evaluation but failing in another. There's a reason WHY they're not following up. Find out what it is.
Consider doing mock interviews with seasoned folks that you trust who are willing to give you honest feedback. You might discover a lot and improve your interview game.
Believe me, I have tried to find out why they vanished from the face of my planet. But there's only so much effort I can put into throwing politeness and courtesy into the void of unimaginable rudeness.
You have to do mock interviews to get real feedback. Real interviewers are so absolutely terrified of telling you even one thing that might help with your next interview that I have never heard anything, good or bad, about myself in the wake of a real interview.
This is not an occasional problem. This is epidemic in every city I have tried looking for full time employment, to the point where I am actually shocked--shocked--if someone follows up with me after an interview when they do not want to extend an offer.
The only reason I can think of for this is that someone out there is actively counseling companies and HR managers to conduct their interviews in this manner. Perhaps it is to cut costs. Perhaps it is to minimize liability exposure to workplace discrimination laws. Perhaps I am on some sort of blacklist. Maybe something on my credit report is bad. There is literally no way for me to find out, because I am already blackholed by the time I might get a chance to ask, and I have no expectation that they would answer honestly if they would even answer at all.
It is true that you can't expect actionable feedback in a real job interview. Mock interviews when done with the right person really help. Of course it means that you have to be open to criticism and handle it with grace. Some folks have reported success with a career coach for this stuff, but that will cost you.
There's also another way to get some feedback. If you develop some rapport with a 3rd party recruiter who sets up interviews with their client, you _might_ be able to get debrief on how it went and what your strengths/weaknesses were.
If he failed some other part of their interprocess -- that's fine, they can send a polite and professional rejection letter. Even a soulless form letter will do.
But to not follow up in any way with the candidate, after that? Unless the candidate vomits in the interviewer's lap, or something similar -- that's just pure rudeness, on the company's part.
It doesn't work as a credential unless it actually produces results.
I had therefore never heard of it before this thread, despite it being around for 27 years now.
At the time I was in high school, US Science Olympiad, Indiana Academic Super Bowl, and the Rose-Hulman Math Competition were about the only games in town. And it was a big school. We might have had a US Chemistry Olympiad team if the chemistry teacher wasn't a few moles short of a balanced reaction, if you know what I mean. The biology and physics teachers were the Science Olympiad sponsors.
I'd think that even just being on the IOI team would be enough to get you accepted anywhere, given that you would have to be one of the top 4 students in the US for that year (by the best screening process that several university professors can manage).
But for now, and the foreseeable future, it would appear that their decision has been validated. Although I'm not entirely certain whether that is because I am not actually good enough as a person to claw my way into the upper middle class on my own merits, or because my accumulated credentials are not prestigious enough for a gatekeeper to lower one of the ladders low enough for me to jump for it.
Like it or not, there may be people out there blackholing my resume just because it doesn't have the right university name on it, or because the year I graduated is in the wrong millennium, or because it doesn't have the right company names on it.
There's nothing that any of us can do about it individually. Stopping that kind of useless credentialism by employers is squarely in the domain of a cartel enforcer--union, professional association, or government--and even then it might not stick.
I prefer whiteboarding systems design/architectural concepts, which is definitely something I do in the course of my regular work.
"Must l-o-v-e solving hyperidealized problems with clearcut answers, under gratuitous time pressure, while being watched with others (who already know the answer). For hours on end. Because that's what we do all day here. Serial olympiadists, hackerrank aficciandos, and other competition coders only need apply."
It's really quite simple to do, and will (by drastically narrowing your candidate pool) make your filtering process much easier, I'm sure.
I'll be honest, I did rate coding interviews as very important, but I changed my mind after working with some really great people who do really badly at them.
He did suggest that some of the problems one gets asked to solve are gratuitously hard, which correlates with my own experience. He also fairly acknowledged that he was getting a lot of rejection for other, e.g. cultural reasons.
So it would seem that it's getting rejected, not "demonstrating coding in interviews" that he doesn't like.
Reply: baseline social comfort is not a generic personality type.
It's not that their anxiety is crippling; it's that for various reasons, the hiring process is typically conducted in a way that is at best often careless and inconsiderate to the candidate -- and quite often needlessly stressful and confrontational.
In other words, the people who sometimes get tripped by such processes aren't demonstrating "crippling anxiety"; they're demonstrating perfectly normal, human traits.
Seems like you just want one generic personality type on your team to make your life easier.
You should really give anxiety sufferers a shot. There are some real gems there which you are dismissing out of hand.
Plus you literally just came out and admitted that it's not actually about measuring technical skill, it's some run-you-through-the-gauntlet "attitude" bullshit. Gimme a break.
Whiteboard sessions are typically done standing (an unusual posture for most people), in a non-interactive environment and importantly, in front of other people (which is quite different from coding, alone, in a development environment, in the sitting or standing posture of one's choice). Who also expect you to explain to them what you're thinking as you're coding, interrupt you with questions or hints, etc. An entirely different workflow from just sitting down and writing code.
Even so -- traditional whiteboard sessions might sort of be OK, if they kept it to a single hour. The thing is, these days, the sessions (whether using a whiteboard per se, or some tool like hackerrank) can typically go on for multiple hours, like 4-6, being stared at by 5-10 people throughout. And are sometimes very poorly coordinated (either the problem isn't properly stated... or it seems no one bothered to check that you've already done the first 2-3 hours of "idiot testing", and make you do it all over again when you get referred to another team, etc).
And this sometimes on other pointless exercises (like a full hour of solving pure logic puzzles, being administered to you by a fresh graduate).
At some point it just gets to be unnecessarily exhausting and humiliating. And no, it's not a symptom of an "attitude problem" if one starts to feel less than enthusiastic about the way some companies conduct these sessions.
That entire process many only produce one or two sheets of paper, with many more sheets ending up in the bin, but I find it is time well spent as it makes the coding step much easier.
Oh yeah? I've interviewed my fair share of self-righteous prima-donna "I shouldn't have to deal with you plebes" sorts before to know you'd better put them through MORE of this whiteboard nonsense rather than less.
And if they get all huffy, you know that when they make a pile of shit, they'll be the quickest out the door to run away from it leaving those of us with work ethic behind to clean it up.
Credentials mean precisely jack and shit to me. I want someone bright and humble.
Think their issue might be with you? ;)
I've been to 20 interviews or so in the past two months and the common pattern with the worst companies is a near complete lack of reciprocal respect and almost hazing (like GP does). The best listen to what's said and evaluate the content and the character at the same time without the need to do "extra whiteboarding" to prove some...thI'm not sure what it actually proves. What does it prove? I'm really at a loss there.
Another thing about those nonreciprocal interviews is that they they tend to be led by significantly less talented folk in comparison. My friend Peter might know why.... ;)
In other words, exactly the "bright and humble" type you're looking for.
I’ve always been passionate about coding, starting from my early days at Olympiad teams in high school and ACM teams in college.
Anyone who's made it onto an Olympiad team[1] of any significant geographical scale, in any category, shouldn't have to deal with this whiteboard nonsense. Maybe a few lightweight-to-medium rounds to verify that they are what they say they are. But that's about it.
[1] We don't know if that's the case with Alibek; the article didn't drill down into that aspect of his background. I'm just talking to the fact that generally, there are plenty of easy ways -- albeit somewhat subjective, and in any case not uniformly applicable to all candidates -- to be at least 87% sure that the candidate isn't a a self-deluded poser, or outright liar about their coding skills (which seems to be the default stance many interview teams take).
And the due diligence one should do to remove that 13% of uncertainty can be made far less time-consuming and grueling than it generally is. Really, if you know how to read the signals, you can much more -- and much more easily, for all concerned -- about someone's coding skills by giving them a single medium-hard, but short-and-sweet exercise... than rounds and rounds (and more rounds) of progressively harder ones, as seems to be the current craze.
EDIT: Overall this is a very heartwarming piece; if a company like Booking -- known for having had several exceptionally talented programers on its staff over the years -- can not only take on someone like Alibek, but apparently consider him to be something of a find -- then that's a pretty damning indictment of the filtering processes used by the 38 of 39 companies that rejected him.