> I would make sure your CS fundamentals are solid as a lot of companies are using leetcode/hackerrank problems as a filter. Is this a thing in silicon valley

> I would make sure your CS fundamentals are solid as a lot of companies are using leetcode/hackerrank problems as a filter. Is this a thing in silicon valley or something? I've never seen this done in practice and would hate it if I had to do this in an interview. Mostly because it doesn't seem like it tells you how good of a programmer someone is, but how much they cared to study for your job interview (how desperate) they are. I have to say, I mostly disagree with the notion that CS skills are deeply important for a first job. That isn't to say that they aren't important more broadly, but I actually had a very wrong idea about programming due to my comp sci major. My first job (internship) I had to learn some tough lessons about pair programming, code review, clean code, messy code, _overly_ clean code, unit testing, etc. Almost none of my computer science skills were useful. That didn't come until about 8 years later in my career.