* taken a 'real' CS class * understand the choices that library implementations make * have probably had to deal with large dynamic data sets and runtime optimization.
Most of the questions are predictable, but not knowing anything about them is a huge red flag.
Congrats! You are selecting for people who 1) rote problems for interviews and 2) motivation to clear your interview.
If you can't be bothered to hire people, earn a profit, and not turn traitor on everyone, I do not want to bail you or your failing bank out.
Next market crash, burn m*f*er burn.
Indeed. And so much so that a whole industry has sprung up to teach people how to play the game. Pretend you've never heard the problem before despite having learned to solve it via Hackerrank or Leetcode. Ask lots of "clarifying questions" to the interviewer to show them how "you" think. Then in a feigned stroke of intuition produce the optimal solution on the whiteboard.
>"If you can't be bothered to prepare, study, and brush up coding skills for interviews, I do not want to hire you."
"coding skills for interviews"? As opposed to coding skills required for the actual role your company needs to fill? It never occurs to you that good candidates might be too busy making deadlines to spend their nights and weekends working through LeetCode problems? This is why hiring is broken.