The Last Technical Interview

As for imposter syndrome: Yegge graduated from high school at 14 and studied nuclear reactor engineering with the US Navy in addition to his roles at prominent Silicon Valley companies. He is not my pick for somebody with imposter syndrome.

I am a fan of his because I've been reading his blog since the Stevie's Drunken Blog Rants days, and he was quite active in the Emacs community for some time. I also worked at Amazon and so his experience there became particularly interesting to me during that time.

i've seen a few interview types in my time:

1. technical interviews run by nontechnical or junior engineers who can't judge technical talent. this typically produces sub-par hires. imagine you are made the director of UX design and you have to hire someone but know little about the industry. what type of hires are you going to get?

2. technical interviews that focus on CS skills. can you write a red-black tree in Java? can you write a bubble sort in haskell? The problems here is that this has bias towards new CS grads that dont have much industry experience but just took tests on stuff like this in their degree. google pioneered this style of interview and it's taken off as leetcode. the problem is that experienced devs dont typically write bubblesort algorithms. this type of interview is biased toward younger out of college hires and codecamp hires that have little experience but gring on leetcode sites.

3. technical interviews that have too many opinions for a hire recommendation. this seems to be a new trend where you need 3 or 5 or 7 thumbs up to get hired and any negatives sink the candidate. this does raise the bar, but typically what i see is someone on this panel has a high opinion of his/her abilities and gives everyone they seem a thumbs down.

What i've found is that soft skills and team dynamics are > the technical accumen. I can teach you how to write go(lang) but its much harder to teach you how to influence your peers or to communicate effectively.

Experienced devs probably dont know how to ace your leetcode interview, but they do know how to influence and communicate and when to stay away from bad ideas. You dont get tested on these things. It's analogous to a being combat veteran. You've been there, you've done that you know how to survive. You might not know the new tech, but that can be taught. I have never seen an dev not be able to pickup a new platform/language/skill within 6 months of hire - anywhere.

Here's hoping this will get better one day but i'm not holding by breath.

If they give a reason, it had better be a legal reason. “Because you’re Mexican” - not legal. “Because we don’t like you/you don’t fit in” - are you in any way different than management? Differently gendered? Differently skin toned? Different faith? Pregnant? Likely not legal.

They are not required to give a reason. You can be fired without reason.

There’s also mitigating circumstances. If the employee can show retaliation by the employer (say the employee participates in protected activities, like espousing unionization or questioning managerial decisions), they stand a chance of recovering damages from the company.

I think this is a response to inexperienced, immature, or thin-skinned managers. The company doesn’t want to be on the hook for some manager’s attempt to fire someone and have it be an illegal firing. Since there’s typically no day-to-day log of behavior, HR has to begin documenting things. The only thing they can be certain is “safe” for the company is to fire for underperforming. So let’s begin the paper trail…