[WinLychee]

RE point 1: in the actual job these days, we're coding through so many layers of distributed madness that you end up doing YAML/JSON engineering and gluing systems together more than anything, for years on end. A lot of "software engineers" are not writing software, or engineering. Candidates will have to brush up on the basics, because it's been so long. An anecdote: explicit for loops were banned from a codebase I worked on, only interior iteration was allowed. I too, forgot how to use for loops. I spent quite some time writing in embedded YAML DSLs as well (complete with static analysis and compiler).

RE point 2: after sending out a lot of applications, you tend to forget the specifics of where you applied, sometimes companies reach out after weeks or months, and everyone wants 3-5 rounds of multi-hour interviews, so it all becomes a blur. Maybe spreadsheets or a CRM would help candidates here. There is no excuse on the candidate's part for not brushing up before the interview though.

RE point 3: very fair, candidates should jot down a few good questions to ask beforehand.

It's crazy on both sides, not sure how to fix tech hiring. Somehow the industry soldiers on.

[marstall]

totally. I can map reduce blind drunk and asleep but I'd have to google how to for loop in just about any language.