Earlier quoted context omitted.
> To play devil's advocate, having a standardized process for all candidates has some benefits. I've witnessed otherwise stellar candidates with amazing open source contributions absolutely bomb coding interviews. Real "write a function that does X" in whatever language you're comfortable with and whatever tools or resources you want. Simple stuff. I'm not sure if you're playing devil's advocate very well here, becau…
> I'm not sure if you're playing devil's advocate very well here, because this suggests to me that the interview process did not work well. Do you want to hire someone who can write a binary tree insertion in 30 minutes, or someone who can make amazing contributions to real software projects? Most companies want malleable, fungible engineers. Most companies are not stable, something is usually in flux -- projects, te…
They're hired to change glorified forms. If they need to invert a binary tree, they will google it in 30s.
My friend (40+) prepared for a couple of months and got hired at FB a few months ago after a career spent in smaller companies. Great comp, mindlessly boring job (the usual, change this form button, change this endpoint) but hey, now that FANGs are remote and you don't need to commute to an office, they're worth a shot. He's already thinking of quitting but unfortunately he already forgot the algorithms exercises and he doesn't want to do the same interview dance again at Google with the hope that things will be better over there.
Whenever I've been in the hiring manager roles, I skimmed over people not knowing theory well and I read with interest their CVs and their personal project (and asked them about it!). Your behaviour is exactly why I didn't want to work for a FANG and I pursued starting a business instead of growing my career as a IC.