Interviewer: This person has 10 YOE split across Google, Netflix, and Meta Also interviewer: This person missed an edge case in his algorithmically optimal solution to my LeetCode Hard. He might not be able to code. I’d better play it safe and reject him.
Interviews have been broken forever. What a massive waste of time. I don’t know why anyone runs complex coding interviews for senior candidates. Either they can code and will figure it out from experience, or you fire them when it turns out they can’t a few weeks into the job. System design and relevant experience is way more important.
I think you answered your own question, it’s a big waste of time and money to have to fire them two weeks in when they can’t code. Especially with severance. Plus it’s unlikely you’ll realize they can’t code that quickly. These people are typically good bullshitters since they got to 10 YOE without being able to code, more likely it will take a few months to realize.
I don't get how one cannot code but has 10TOE at fangs?
Make sense
Sounds reasonable
World Conflicts
Yesterday
500
Is "From the River to the Sea" So Wrong?
Tech Industry
Yesterday
1520
Do people underestimate E6 role at meta?
Personal Finance
Yesterday
1097
Thank you AAPL and NVDA
World Conflicts
Yesterday
581
Israeli precision-guided munition likely killed group of children playing foosball in Gaza, weapons experts say
India
Yesterday
632
'Hindutva': The Radical Hindu Ideology That Seeks to 'Push Christianity Out of India’
It’s good practice to throw away the bottom half of your list of applicants so that you don’t accidentally hire an unlucky engineer
That would make sense if the bottom half is based on a ranking that evaluates the applicants experience and skills. Too bad it's not, and that bottom half you are referring to is almost as bad as picking a random half.
@microsoft woosh