←back to thread

191 points foxfired | 2 comments | | HN request time: 0.001s | source
Show context
Esophagus4 ◴[] No.45112231[source]
Every few weeks, someone posts an article about how broken tech interviews are, and the articles always follow the same formula: but I’m really good at REAL engineering… it’s the INTERVIEWS that are wrong!

It sounds like the author may have faced a bad interviewer, but I’d be curious to see their feedback on the author so we get both sides.

As I comment each time: you’re not being asked to sort a million item array because it represents the job, you’re being asked to sort a million item array because I want to see how you think, how you solve problems, and how good your underlying CS fundamentals are.

Yes - that means regardless of seniority, I expect you to know CAP theorem. Sure, knowing CAP theorem does not imply you are a good engineer, but being a good engineer DOES imply you know CAP theorem.

The job will change from project to project, but the CS skills should carry through.

replies(5): >>45112350 #>>45115600 #>>45116569 #>>45118008 #>>45120775 #
1. ponector ◴[] No.45120775[source]
>>>Yes - that means regardless of seniority, I expect you to know CAP theorem

You can have the same result asking for a chess.com score. Anyone with score lower than 1400 is a bad engineer. I'm sure you'll have even better results than asking some CS theorems.

replies(1): >>45120855 #
2. Esophagus4 ◴[] No.45120855[source]
Why is expecting senior engineers to have an understanding of, frankly, basic fundamentals of how computers work is so upsetting to you?

If you want to hire and work with people who don’t know those, by all means, hire them… I certainly won’t stop you.