Who said it's accolades alone? I hold myself to the standard of knowing enough the problem space before I interview people that I can open an editor and come u

Who said it's accolades alone? I hold myself to the standard of knowing enough the problem space before I interview people that I can open an editor and come up with domain specific problems that anyone who's doing what they claim they're doing daily can work through (crazy bar I know...) > Outside of FAANGs I've routinely interacted with fairly senior engineers who just could not code, period, full stop My first thought was "You must be joking if you think there are no L5s in FAANG who can't write code",but then I realized you actually think of writing code as literally being able to write statements in a given order... but that's such an insanely low bar that people regularly meet it by repeating problems over and over for a few months. My bar for writing code at past a junior level is to be able to solve a problem with production grade code. LC almost precludes that between the time constraints and rigid solution set so people settle for "they wrote a guard statement against an empty list". I just want to know that a new hire isn't going to ignore things like cache locality or not know what a memory mapped file is and try to load gigabytes of data into memory and parse the whole thing just to run their O(N) solution across 4kb of data.