2 ms·

I say the same thing on many of these threads. Most people rejected a at BigCos aren't rejected for failing to pass the technical bar(s); those people get filte

I say the same thing on many of these threads. Most people rejected a at BigCos aren't rejected for failing to pass the technical bar(s); those people get filtered out in the phone screens. The by far most common reasons interviewers offer for low scores are: didn't listen/didn't acknowledge when they reached the end of their knowledge/didn't test when they got off the rails/just didn't seem like a cooperative coworker. These are all filters that may not matter at ye olde startup; but in a stable long lived team, these are red flags that seem corellated in my experience with lowering the morale of a dozen other people. So, even if you're a rock star, you might get rejected.

hobls 10y ago
This is a great comment. Totally agree. > didn't acknowledge when they reached the end of their knowledge Oh man, this one. How hard is "I don't know?" You're not supposed to have the entirety of computer science and software engineering knowledge jammed into your head. Let's talk about what you know and what you don't and figure out whether you're a good fit. We hire lots of people without direct experience in what we do because they seem great to work with and we think they'll learn quickly. Just please don't try to bullshit; it doesn't usually work.