(1) The candidate was a criminal mastermind who somehow managed to fool everyone for 15 years.
(2) The candidate was just super nervous during the interview and experienced a kind of test anxiety.
I've personally been (2) several times.
(1) The candidate was a criminal mastermind who somehow managed to fool everyone for 15 years.
(2) The candidate was just super nervous during the interview and experienced a kind of test anxiety.
I've personally been (2) several times.
Not "criminal mastermind", but do enough hiring and you will run into a lot of people who are convincing conversationalists but clearly haven't written much code in a very long time.
In a couple cases I gave these people benefit of the doubt and gave them a backup take-home problem (super trivial, 5 minutes for experienced engineers). They always came back with a solution, but when you asked them to walk you through it they couldn't really tell you what they wrote.
I understand that test anxiety is real, but having to discuss your code with others on the spot is also part of the job. If someone can't discuss even the most basic fundamentals of programming in a conversation, you can't dismiss it all as anxiety every time.
IMO the key is really to investigate the candidates as much as possible before they even walk in the door. Nowadays, many candidates have a large public footprint.
(I also think employers interview way too many people. That's mostly a waste of time, better spent focusing on a relatively small number of the top candidates.)
I'm sure we all have stories about falling on our faces during a technical evaluation, it sucks but I wouldn't personally fault the interviewers passing on them.
Software developer hiring is very different from most other hiring, but it seems that many software developers don't even realize how eccentric they are, because they've never been outside their own industry.
Please note I'm not saying ask leetcode questions, I can't even solve LC. I've failed many interviews at Facebook and Amazon because of LC; but other jobs I've accepted all asked some basic coding questions.
If you want the government to start regulating all programming, then the shit's really going to hit the fan. ;-)
If anything big tech needs to not only be regulated more, they should be broken up.
You're thinking of the wrong thing. We're not talking about breaking up big tech, we're talking about every little hair stylist needing a cosmetology license.
- It's definitely possible to hold a tech job for 12-18 months without writing any working code and changing jobs that often isn't that big of a red flag. Also, people lie about their experience.
- The pool of people applying for a job has a very low intersection with the pool of people currently working at a job. In that intersection there is a very high subset of people who believe they may lose their job soon. Therefore the people applying to a job is largely people who either are not currently working, or will shortly be out of work. See also[1]
1: http://weblog.raganwald.com/2007/03/thank-you-for-writing-su...
Which big firms?
I find it curious that a BigCo on one's résumé brings cachet, because BigCos are able to hide incompetence, even at the executive level, to a vastly greater extent than a small company. If you find someone who for example has around a decade of experience at a company of around ten people, it's going to be almost impossible for that person to have done nothing of value.
> These kinds of candidates outnumbered the obviously anxious candidates by maybe 10 to 1.
Anxiousness is not necessarily obvious. My stomach could be churning and my mind racing, but a stranger probably wouldn't be able to tell.
As for which companies? Basically any large enterprise except absolute top-tier tech. I wouldn’t necessarily call such people incomponent though - I’m sure they were perfectly good button-pushers within the corporate machine. Low-skill high-specificity.
I'm not really sure what you mean. First, anxiety is on a continuum, so I wouldn't propose a dichotomy here. Second, lots of people have situational anxiety, which I wouldn't call a "disorder". For example, a great fear of public speaking is pretty common.
Of course poor performance at some specific task, e.g., an interview or a speech, is manifestly noticeable, but the cause of that poor performance isn't necessarily manifestly noticeable. In other words, you can't necessarily tell whether it was caused by a lack of skill or competence or just temporary anxiety. Or maybe lack of sleep the night before.
IME these people talk a lot of talk, but they don't deliver contributions. Like the simplest script could take a quarter? I don't endorse code metrics, but, e.g., 1 PR / quarter (of really simple stuff), unless that PR is blowing my socks off or had some complex amount of research or some reason behind it, is underperforming.
You expect negative returns for a new employee like the first 6–12 months. This is well after that, where it's clear that they're not putting in the effort to understand the systems around them, or they lack fundamental skills (like experience writing actual code), or more often, both.
I wouldn't call this "wreaking havoc", but I think only wisemang can explain what exactly they meant by that.
> You expect negative returns for a new employee like the first 6–12 months.
Wow, I wouldn't expect that. In my opinion, an experienced programmer should be able to start contributing something within weeks. If they can't, then "can" them.
Think about open source projects: nobody takes 6-12 months to "get up to speed" before contributing to a project. That would be ridiculous.
The havoc I was referring to was more due to the person’s political skills and ability to shift the blame for his own shortcomings to people on his team, while those on the team were unaware of how he’d throw them under the bus while managing up. The failure at “fizzbuzz” was a red flag that got ignored by management (yes there was some existing dysfunction in the org).
And so — figuratively speaking — someone who couldn’t even build a doghouse ended up being tasked with architecting a shopping mall, then attempted to deliver a skyscraper (and failed miserably at it).
> Think about open source projects: nobody takes 6-12 months to "get up to speed" before contributing to a project. That would be ridiculous.
I'm trying to be generous, and to say that the people under discussion in the comment are past the 6-12 mo timeframe to avoid needing to fend off "but maybe they just need more time/experience/etc."
But I also do think 6 mo is about the "productive" point. This doesn't contradict "start contributing something within weeks" — you should contribute something within your first week, ideally, if the company has their stuff together. But it's 6 mo, IMO, until one has got a good grasp on the architecture, and more importantly, the theory of the system at hand, and can make their own salient decisions about how to grow it that are going to fit well into the existing theory of it.
But again, I'm just putting it out that that we're well past the "initial onboarding" phase of an employee, and tried to pad the amount to avoid commentary.
This person had a very very niche job, at two orgs, with no work/growth outside of that very specific thing. This lack of doing anything else was a flag one of the high level managers saw.