I have seen people be very strongly influenced negatively or positively by a word or phrase on the resume that in the scheme of things wasn't that important. I am sure I do the same thing, but I am not aware of it.

I'd hope to have a similar 'audition' approach that included not only basic programming skills but also –and as a junior level programmer, more importantly– learning skills. For example, commenting or debugging internal framework code (something that all interviewees are experiencing for the first time).

In regard to the linked article's approach - I couldn't afford to take three weeks off of my current job, to learn a new language, even if the training gave me a slim chance of a new job (I still have bills to pay). That said, I do think wish there were more apprenticeship type approaches for junior devs.

Software development IS NOT meritocratic and neither are orchestras. There is just as much politics, networking, and problems with "value" in orchestras as in software development.

I recently completed a programming bootcamp and when I explained this to several of my classmates they made a point of highlighting what a great programmer I am (relatively to our peers) and that I'm a really great person to work with "once people get to know me". But, there's the crux of the matter for me - in an interview situation, if I'm ruled out in the first 30 seconds then nobody "gets to know me" or my programming potential. To add to the irony, about 2/3rds of my current co-workers know that I'm looking for a job and they regularly make comments to me about how much they don't want me to go, followed by comments about understanding my need to work in a less toxic environment.

But from a fellow introvert who has had success with interviews: an interview is a good example of a social situation that's fairly "hackable."

By hackable I mean an interview is something where, at least compared to an open-ended conversation with a stranger, there are certain... branching paths of conversation?... that you can practice ahead of time.

The inevitable questions about why you're leaving your current job are definitely a thing you can practice. I don't think it's necessarily bad to mention some negatives regarding your current position and why you want to get out of it. If it didn't suck in some way, why would you be looking for a new job?

I think a good answer to the "why are you looking to leave your current position?" question would involve:

1. What you like about the new company ("You guys seem to hire really good coders, you're growing as a company, and I like your approach to A, B, and C.")

2. What you want to achieve at the new company (ex: "I'm looking for an opportunity to do less support and more coding.")

3. Optionally, something about what's bad at your current company. Preferably in a positive context. (ex: "I'm really excited about building modern web applications, and I'm not able to achieve that at Company XYZ because we've committed to supporting IE6.0 until 2050 because it's what the owner's mom uses.")

Anyway, it's not easy, but it's.... hackable. Unless it's a really weird interview, most of the ground you'll cover is rehearseable. Good luck!!

In all of the interviews I've been to recently, the interviewers continue to press me if I focus on their company and don't say something about why I want to leave my current employer.

After a particularly bad interview, I did start practicing for these types of questions and I'm getting better, but that's still relative. Part of the problem is that I've been in the toxic workplace so long and I'm so desperate to get out of it, that thoughts of escaping push to the front of my brain while I'm in interviews and I either blurt out something I shouldn't [1] or I just freeze up (think deer in headlights), typically a combination of the two which is even worse.

[1] I don't blurt out anything quite as bad as "my current boss is an ass", rather things like "My boss doesn't believe in bug trackers and I think they're extremely important." So far so good, right? But then there's a pregnant pause and I catch myself blurting out, "At least a client threatened to take away our business if we didn't start keeping bug records, so now we have 3-ring binders and paper forms to record our bugs. But that doesn't do any good when the same bug is reported multiple times in every binder and the boss doesn't actually look at the bug reports or give anyone else access to the code." At which point the looks on the interviewers face tell me I've blown it again. (Very true scenarios about our bug reporting and my idiotic blurting out in an interview.)

Maybe it's how you're saying it, and not what you're saying? Is there somebody you could practice with? Somebody who could point out body language or tone of voice or other cues that could be giving interviewers the wrong impression about you?

One other possibility...

Maybe round out that story by mentioning how you (or the team you were a part of, even if you weren't the lead person on the effort) tried to solve that problem in a constructive way. "We gave our boss a presentation on three popular, low-cost issue trackers that we tried and liked... to no avail." Surely your next employer will make some decisions you don't agree with - they're wondering how you will handle them!

I have to admit, I never considered trying to recover after I get the "look" from interviewers. In fact, I had provided multiple recommendations on bug-tracking software, to include setting up demo servers for several different packages (because of those demos and related discussions, our interns started using both bug-tracking software and GitHub for their projects - so that was a definite win).

  > I certainly think part of my problem is the how I'm saying it.

If you truly are coming off awkwardly, what's the real problem there? The problem is this: the interviewer is wondering, "How is this guy going to interface with the rest of the team here if he's this awkward? Does he even know he's awkward?"

So... you can address both of those unspoken questions head-on. Mention that you tend to get nervous in interviews and when meeting people for the first time and that it's something you overcome fairly quickly and that you tend to develop really good working relationships with coworkers. (Because that's certainly true from what you've said)

  > I wish I had somebody who could do this for me!

  > In fact, I had provided multiple recommendations on bug-tracking software, 
  > to include setting up demo servers for several different packages (because of 
  > those demos and related discussions, our interns started using both bug-tracking 
  > software and GitHub for their projects - so that was a definite win).

> ... you might not be coming across as awkwardly as you think you are ... I have no doubt that I am.

> ... you can address both of those unspoken questions head-on ... I honestly never considered this, but will in future interviews!

> If you live near Philadelphia... Unfortunately not.

> Is there anybody non-technical that might help you? Siblings, parents...?

Unfortunately I tend to have family and friends that are overly critical in a really bad way. The last time I asked my mother to look at my resume I was berated for 30 minutes for being so stupid, not using my god-given-skills, etc (i.e. nothing useful but lots of hurtful). I don't even bother asking the guys in my family, they're far worse than my mother. My friends really are great friends in many, many different ways, but tend to be truly lousy at giving constructive criticism. For example, I told one friend that I was going to be building an JavaScript application. She instantly went off on the evils of Java, how Apple won't run Java, and didn't let me get a word in. When she finally finished her anti-Java tirade, I tried to let her know some of the many differences between JavaScript and Java, but until a couple of other friends started quoting from wikipedia entries and intro tutorials, she wouldn't believe me that they really are two different languages. (I promise, she has been a really good friend in other ways!)

I do participate in a ton of meetups. Would it be appropriate to ask a peer from a meetup group to be a proxy for an interviewer?

Because you'll never convince me that no musicians have toxic attitudes. Even at the symphony orchestra level.

Do you prefer the most skilled person, or a very skilled person who gets along well with your team, understands your industry, and cares about your mission?

> your team, understands your industry, and cares about your mission

When teams are largely made up of a certain kind of person, using this as criteria for hiring is a sure fire bet to make sure your team stays homogenous and never grows outside of its little comfort zone.

So, yes, individually maybe they're not valuable, but in multiplicity they can become meaningful.

This is a good summary of some of the data:

http://www.cnn.com/2014/11/26/us/ferguson-racism-or-racial-b...

Professors at the University of Chicago and MIT sent 5,000 fictitious resumes in response to 1,300 help wanted ads. Each resume listed identical qualifications except for one variation -- some applicants had Anglo-sounding names such as "Brendan," while others had black-sounding names such as "Jamal." Applicants with Anglo-sounding names were 50% more likely to get calls for interviews than their black-sounding counterparts.

Most of the people who didn't call "Jamal" were probably unaware that their decision was motivated by racial bias, says Daniel L. Ames, a UCLA researcher who has studied and written about bias.

"If you ask someone on the hiring committee, none of them are going to say they're racially biased," Ames says. "They're not lying. They're just wrong."

The point is, "discrimination" is sometimes just applying statistics. Just because some statistical factors correlate with race doesn't mean one is being racist; they are just optimizing their selection process.

> One study conducted by a Brigham Young University economics professor showed that white NBA referees call more fouls on black layers, and black referees call more fouls on white players. Another study that was published in the American Journal of Sociology showed that newly released white felons experience better job hunting success than young black men with no criminal record, Ross says.

>"The overwhelming number of people will actually experience the black man as having the knife because we're more open to the notion of the black man having a knife than a white man, " Ross says. "This is one of the most insidious things about bias. People may absorb these things without knowing them."

Anyways, this kinda stuff has been shown to happen with plenty of different groups. Attractive vs ugly, fat vs normal weight, woman vs man, old vs young, tall vs short. We aren't as rational as we'd like to believe.

...And what the hell does someone coming from a poor neighborhood have anything to do with anything? I grew up poor, I don't see how that is relevant to my job skills. I'd love to knkw why I'd be optimized out of a selection process. Furthermore, your resume usually has your address on it, you don't have to guess.

No, I was just commenting on the logic of the quote in the parent comment, which I find faulty. I'm not saying people aren't racist, or subconsciously racist; I'm just saying that you can't reduce any statistical effect down to racist, while other explanations are just as possible.

> And what the hell does someone coming from a poor neighborhood have anything to do with anything?

I'm pretty sure that if you run statistics, you would find out that people from poor neighborhoods are more likely to be criminals, violent, less educated, less intelligent. Is it their fault? No, obviously not - they were never given a chance to excel (or rather, they had to overcome many more obstacles). But I think it's the responsibility of the government (or charities) to help such people, while it's the responsibility of a business to, well, do business, with the best employees it can hire.

Btw, I'm not saying that you should take the above into account. I just oppose the logic that it's always "racism". Because then you could equally say, it's racist to prefer people from Harvard, because Harvard discriminates against people from bad neighborhoods, because they have lower SAT scores.

> Furthermore, your resume usually has your address on it, you don't have to guess.

Oh, I didn't know. Mine doesn't.

I'd really encourage you to read it an other articles on implicit bias; they're really important issues that have disastrous impacts.

> I'm pretty sure that if you run statistics, you would find out that people from poor neighborhoods are more likely to be criminals, violent, less educated, less intelligent.

The problem I have with this is that it's a hunch that sounds reasonable, but there's no data to support the claim. I think we need to be especially careful in situations with implicit bias to vet all of our assumptions, because in aggregate, they have really negative impacts on large subgroups of people.

Here's a link to the source document for the linked article: http://www.povertyactionlab.org/publication/are-emily-and-gr...

That article references other journal articles that review exactly what you're talking about, varying only location. It appears that it helps, but helps whites more. I didn't read that article (I'm at work; only have time for so much research, which probably should be no time at all :P)

> I'm not from the US, but don't many American blacks have white-sounding names? And I assume those blacks are more likely to come from families that are wealthier and better educated.

The article says, "Each resume listed identical qualifications except for one variation... names"

I looked into the underlying source article and they list and control for the education of the applicants, which means there's no need to judge their education by their name, since you already have it.

I think the problem a lot of people have is that it feels a lot like we're saying everyone is racist, which feels a lot like an attack. To spin it a little differently, I'd personally say we're all biased. You could go through any long list of cognitive biases and implicit racial bias would just be one of the myriad everyone is subject to in some magnitude. It's a matter of being aware of it and really questioning your founding assumptions so you can reduce the bias where possible. The problem with racism is that it has real and lasting impacts right now on minorities, and is particularly insidious (if you ask me).

I really think it would be worth your time to read the article and follow some of the linked articles. It's really interesting information that's relevant.

And the article I linked to says that. Individuals don't MEAN to be racist (or sexist, etc.) but are, because culture gives us biases. Addressing unintended racism is hard, because it isn't visible. We aren't attacking individuals.

http://med.stanford.edu/diversity/FAQ_REDE.html

> The problem I have with this is that it's a hunch that sounds reasonable, but there's no data to support the claim.

I would bet that there is data to suggest that "people from poor neighborhoods are more likely to be criminals, violent, less educated, less intelligent", and even data to suggest the other inferences tomp brought up.

However, the vast majority of people are not "criminals", at least in the habitual sense, and the vast majority of people from the 'hood are also not "criminals".

"When the incidence, the proportion of those who [are criminals], is lower than the [proportion of people from the 'hood who are not criminals], even tests that have a very low chance of giving a false positive in an individual case will give more false than true positives overall."

The problem I have is with phrases like "I would bet there is" or "I assume those blacks [with white sounding names] are more likely to come from families that are wealthier and better educated."

It seems like an obvious correlation to make, but they're not based on data. I think it's in our best interest, intellectually, to take a few minutes and look for some information. The internet means it can take fifteen or twenty minutes to find a decent chunk of data to start working with. It won't make you an expert (and I'm by no means one either), but it can help highlight a lot of the nuance that exists in issues like this.

What you are describing is, specifically, racism.

http://en.wikipedia.org/wiki/False_positive_paradox

I'm pretty sure if you run statistics you would find that people from poor neighborhoods are more likely to have their activity be criminalized, cast as violent, denied access to education formally and informally, and have their intelligence devalued in comparison to a social norm that has implicit bias.

This only needs to be true for a higher percentage of the represented population to say that it is more likely. It doesn't make someone a bigot to talk about statistical measures. (i don't have the stats in front of me but i'm merely commenting on your accusation.)

  > The point is, "discrimination" is sometimes just 
  > applying statistics. Just because some statistical
  > factors correlate with race doesn't mean one is being
  > racist; they are just optimizing their selection process.

Even if you could 100% accurately determine a candidate's background from looking at their resume, and even if you could be sure that people from their background were more likely to be "bad" people[1] then couldn't you also look at "Jamal's" resume and conclude: "Obviously, Jamal must be a talented guy to rise above his background and pursue a technical career?"

In the end, it's all guesswork anyway. Companies would be much better served by sticking to the facts on "Jamal's" resume and checking themselves whenever they catch themselves inventing fictional histories for people based on a candidate's name and their own racist prejudices and stereotypes. _____ [1] To be clear: I don't agree that either of these things are true.

If your optimized selection process selects away from Black candidates it is by definition racist.

I don't think so. Correlation doesn't equal causation.

Edit: also, since more Asians and less blacks are accepted at good universities, if your company relies on the name of university when selecting candidates (e.g. a candidate from Harvard is more likely to have an interview than a candidate from an unknown state school), by your logic that's racist as well.

Racism is [dis]favouring a particular group based on race. If you choose the 10 highest scorers in a maths test in a group and the racial make-up doesn't match that of the group as a whole that's not racist.

One could manipulate your choice characteristics in order to achieve the racial profile that you want. That's serious conspiracy theory territory though.

Many people are consciously racist, not in a "I want them all lynched" way, but in a "meh, I'd rather not meet with a black guy, probably a waste of time" way.

Of course they aren't going to admit that sort of bias. And again, you're just guessing at what happened.

There is indeed subconscious bias, and it rears its ugly head when we're observing people's mannerisms, their speech, their attractiveness, and yes, their skin color. But just looking at names on a resume, I'd argue the decision of calling someone back, based on the stereotypical application of their first name, is just a conscious bias.

Huh? I never guessed that anything happened or guessing at any motives of anyone...?

The same resume experiment has been tested with male/female names as well.

Is that not guessing at motives (or the lack of a motive, I suppose)?

The point the above commenter made is that the CV example does not demonstrate subconscious bias. The researcher in question said they were "probably unaware", and said that "if you ask someone on the hiring committee", implying that they did not even try to measure whether or not this bias was conscious or not, but that they assume a lot of it was subconscious.

It's quite possible - even likely - they're right about that, but from the description it does not sound like that study is a good basis for demonstrating subconscious basis.

> The same resume experiment has been tested with male/female names as well.

Many people openly admit to biases against females in certain jobs, so that too is a bad example for establishing subconscious bias.

I agree with you that there is a lot of subconscious bias (and the article has much better examples, such as the knife example where there's no motive for people to pick the wrong person), but it's not clear that the CV example demonstrates subconscious bias. It certainly does demonstrate bias though.

[1] that being said we always, always try to give some constructive feedback if asked.

What's more important, is I don't understand how anyone could possibly improve their 30 second impression.

I guess it could be that you believe this to be the case, and are remembering wrong. Why don't you note this down after 30 seconds, and then check it only after you make a decision to see if you were correct?

Companies would like you to think this, too, and law makers would very much like to think that their rules regarding non discrimination have any effect. The real situation tells another story.

But it's OK, companies can just include a nice stock picture of an ethically diverse group of people in business attire working together, an all is well.

This is not actually very hard: start with good grooming, nice clothes, posture, confidence.

Of course, this doesn't change the fact that the hiring process seems... odd.

Appearance is important, and I've never been in an interview situation where it wasn't? Unless you're insinuating choice based on ethinicity (more aimed at _pmf_'s response to your comment). Which is completely irrelevant, as are accent/sex/other discriminatory factors that make zero difference to how someone is likely to work within a team.

As I've said in other comments, there is a serious element of external preselection based on geography and company sector, there's nothing particularly underhand going on.

This is just plain ignorant. Every single place I have worked has had its share of everyday sexism and racism, and that includes how current employees act in hiring interviews. You claim to not notice these things, but what you are saying is that you don't consider those things valid differences that may affect how someone perceives your team or work environment. How can you ever confront issues in your workplace by shoving your head in the sand?

Given the way you're talking about making a hire/no-hire in five seconds, I find it incredibly difficult to buy the idea that you're not taking that into account. You're glorifying the snap-judgment hire.

Because most people do, and a good hiring process takes that into account and counterbalances it.

Maybe your company sucks at interviewing? Maybe you're lucky and all of your candidates are good enough to do the work so you can cherry pick the ones that "fit"?

I've interviewed a reasonably large number of people, and I've worked with some folks who were good at interviewing, and there were many times where it took most of a day to figure out whether or not someone was worth hiring.

What I've found is that credentials, like a CS degree, are generally garbage and bear no relation to whether or not someone can code or problem solve. Experience and resumes can be misleading as well and rarely tell you for certain whether or not someone can actually do the work. Maybe something like half to 2/3 of the time it's obvious within the earliest portion of an interview that someone just doesn't have the skills. The remainder often takes a lot of work to suss out skill levels. Rarely someone will knock it out of the park and be an obvious hire. More often than not it'll take several interviewers concentrating on a few weak spots to see how weak they truly are and figure out if they're still a good hire. Not to mention the problems of trying to gauge someone's skill level in a high pressure environment where they will absolutely not be at their best.

Increasingly I get the impression that silicon valley is becoming like a giant frat house where companies just hire people they like and then bang out horrible code and fail to execute on projects until the VC money dries up or they get pity-acquihired.

1. The IT world in the [geographic] area of the UK I live/work in is small (this is critical, because experienced candidates have a high likelihood of being known). 2. The company I work at isn't a tech company. 3. The company operates in an unfashionable sector.

Shouldn't technical interviews be different? No, not really. In general the interviewer will give more hints to people he likes and more follow up questions to people he dislikes. After enough hints even the worst candidate will find the solution and get extra points for good collaborative skills. Similarly even the best candidate will stumble sooner or later and gets a mark for being argumentative if pressured enough.

Also notice how everyone says "We care about the thought process and not if the solution actually works!". This allows for their subjectivity to reign supreme. Things like "Your solution is wrong but I love your thought process!" or "Your solution is better than mine but you didn't think things through enough before implementing it" can be said about everything.

It is of course not that hard to do technical interviews correctly, you just need to have hard rules on what to accept and what to reject, what hints to give and when to give them etc. Any leeway for subjectivity will be abused by your subconscious.

So you just admitted that you make your hiring decisions based on a snap judgment. OK. But that doesn't mean you can tell in 30 seconds is whether someone is actually going to be good at the job.

It's usually not a conscious thing, and it's something we're all prone to doing.

But he's also right. There's been studies on this. Avoiding initial impression from dominating hiring decisions is incredibly hard and requires a ton of process that pretty much "nobody" does. Few places do much to handle even much more apparent biases.

It's interesting that you're allowing hiring decisions to be influenced by what you think is best for yourself. What's best for the company can and should be a secondary concern. I've also found it useful to do the following:

1 Telling HR that candidates are flaky. It's easy to convince HR that every single one will leave in a year or less, especially these hipster kids that are interested in the latest startup.

2 Telling HR that candidates will take forever to add value, even if we have a smaller component that needs working on. This is still easy to convince them, given the ramp up to some of the prototypes that we do.

3 If the candidate actually makes it to the interview stage, I just finish my questioning and tell HR that the candidate has an attitude problem. This works even if they get every question right, or if they go into detail. The latter works especially because they think they're showing value, but they actually make themselves easy to label instead as arrogant up-jumpers with a "behavioral problem"- and I can easily convince my HR of that.

4 Telling HR that candidates don't know a specific tech well enough. Even if that tech has a ramp-up of a week or less. Because again, HR will take my word for it.

You're also right about those thirty seconds. It is the best and only approximation that one can make. Forget the interview, forget allowing them to show value, and if they do, they have an attitude problem.

Good luck with your recruitment efforts and next quarter.

I find that phone interviews actually work differently - I've been able to turn around an unenthusiastic interviewer and I've been able to lose someone who liked me. For that reason, I think questions of actual code aptitude are best done on the phone, as that's the only place where you really can evaluate someone's thought process isolated from mitigating psychological barriers that occur during face-to-face interactions.

The icky reality is that face-to-face impressions are pretty much determined by how you smell. I think there are two reasons for this - first, there's the concept that people naturally want to be around winners and if you come in looking like a loser they'll be predisposed to dislike you in ways that escape their conscious thought. To work this one, try to chalk up a win before your interview (or get laid - again, hate that it works this way).

The second is that as people we unconsciously recognize whether or not the candidate believes that they're a good fit for the position. If you go in freaked out, you're going to set off a bad feel no matter how hard you try to cover it up. The feeling a recruiter responds to in the first thirty seconds is "this could work". You can't fake this, and this is why being as good as possible at what you do really does matter. It definitely rewards intrinsic overconfidence, but the more intrinsically underconfident people are generally smarter anyways and will eventually be so much better at what they do than their peers that they'll win in the long run. If you feel insecure in your ability to fill a position, get better at what you do and prove it to yourself by having other people evaluate your work - the feeling will go away eventually. Code review is scary for people insecure in their abilities, but it's easily the fastest way to wipe away pathological insecurity.

You know from the resume whether the person can do the job. It's whether you want to sit next to them for 8 hours a day while they do it.

30 seconds? Yep.

Do you? I remember reading a bunch of articles that asserted most people that come in for programming interviews (even if their resumes look solid) are useless.

It also helps that I live in Melbourne, Australia - the IT world here isn't massive, and if you haven't worked with the person the odds are you know someone who has. :-)

It certainly takes longer than thirty seconds (or a few minutes) to determine that someone who looks good on the surface, who is clean and neat and who sounds like someone who would fit in the team fine, should be avoided like the plague because they can't actually do the job.

I must say I'm not advocating snap judgement at all. I just think it is very common (as Kahnemann states). What he states as an ideal doesn't necessarily make an awful lot of difference in many situations; the snap judgement can very often be the same as the careful one (though external factors that partly force/aid preselection bias things greatly in this respect).

Do you have any evidence at all to back this up? In general, people think they are much better at making decisions than they are, and unless you actually measure things empirically and track false positives/negatives, you are likely to fool yourself.

In short, possessing such a mentality is dangerous and likely to keep your mind shut.

I don't doubt that you might happen upon some pathetically incompetent interviewers. But if you treat every "no" response in this same manner it's awful.

I like interviews to be like secret ballots:

* write down what you think about the person without any external influence

* then share the information with the other people who interviewed the same person

You are right on this - bias can interfere with decision making. A single gatekeeper who makes the wrong decision could be turning away someone fantastic.

The hardest thing is saying no to someone you know is great, or is going to be great. It isn't personal - it might be that one of the candidates had 5 more years experience on something that we were really looking for. In this case, if I am working with a recruiter, I always let them know how great the candidate was.

Interviews are also in a pretty unique position to be quite honest with you. They have no real incentive to lie or even to be nice to you. Which isn't to say they always will be honest, but your odds are higher than they would be if you were asking say... your current boss about why you were passed over for a promotion.

2. Heck yeah to that.

3. There's nothing wrong with politely asking (not "pressing") for more information. If one interviewer out of ten gives you the information or feedback you asked for, that's a pretty good time investment - how long does it take you to write ten short, polite emails?

I can pretty much debunk 1 and 3 personally. Good companies and people take hiring very seriously.

E.g. woman buys new shoes on pure impulse. At home she finds they go really well with a certain purple dress. Why that's precisely why she got them, of course. Eight months later, that's all she remembers: I had that dress in mind when I saw those shoes.

(There's at least one study on people with severed brain stems that is fascinating in this respect, but I can't remember where I read about it, and don't have time to track it down)

I know that very few employers would take the risk to be so frank but I personally wish they were. It would be helpful to the candidates who actually care about improving their knowledge and skills while potentially offending those who are trying to fake it.

I've told candidates variants on that theme before.

"This position requires knowledge of programming, particularly in (C, Python, insert details here)."

Dancing around that point is not a "politeness".

That was, incidentally, sekasi's point #3, several parent references up:

"3. Always respond to requests for more information"

No. :)

"3. Within reason, always respond to requests for more information."

Many communication "rules" require the ability to moderate one's interpretation of the rule. I don't think this is any different. It's a good thing to give candidates feedback and if they're confused, the feedback did no good so you should be willing to help them understand. But if they're just unwilling to see the world or themselves for what they are, it's out of your hands and you should leave it well enough alone.

Following up on some references before calling people in for an interview isn't a bad idea.

Man, I have seen some blatantly incompetent ones. You'd give them a white board and ask them to show a linked list with boxes and arrows. They just couldn't do it.

One case I remember couldn't demonstrate pseudo code for a circular buffer operation based on an array with a head and tail index.

Hash tables might be a better filter, because IMHO you're a lot more likely to find those in real use these days than linked lists.

(The job area was embedded development, involving C and C++, so asking for C code related to linked lists would have been fair game!)

And (hopefully) how well they did in the phone screen...?

(These werr people who couldn't program FizzBuzz)

Plus anyone can just make shit up on their resume.