logoalt Hacker News

hobs02/20/20251 replyview on HN

Yep, I've done a lot of SQL interviews and it is always interesting to see the folks who've crash and burned at code review and killed it at writing individual queries and sometimes the unexpected, the opposite happened, the person would fly through a code review and do really subpar on writing it, a signal I usually took to mean that the person was nervous as hell in the interview.

The two folks who showed this behavior I hired anyway (they were contractors so nbd) and they were excellent hires, so I really love the code review approach for climbing up bloom's taxonomy.


Replies

lubujackson02/23/2025

I feel like identifying problems is the most important skill for success. Especially with AI, (but even before that) SEs are more often "editing" rather than "writing" code, and most of your time is either fixing odd states or anticipating them.