4 ms·

in general software engineering has no barriers to entry officially, and it pays well, so you get an influx of people who are all about the $$$ but without any

in general software engineering has no barriers to entry officially, and it pays well, so you get an influx of people who are all about the $$$ but without any of the requisite skill. I've done my fair share of interviews on the interviewer side to know that there are definitely qualified applicants out there but you have to wade through many not so qualified applicants. People complain about leetcode style interviews but when you get a lot of applicants for a position who are unqualified, you have to filter them out some how.

qes 6y ago
In my experience, albeit limited, you don't need anything approaching leetcode challenges to weed out the unqualified, even the good talkers. FizzBuzz became a thing for a reason. Would you consider FizzBuzz leetcode? Would you consider a 5 minute discussion about how a linked list works leetcode, or whiteboarding pseudocode for a node structure and Add/Remove methods? (and for what it's worth, I almost never find a need to go even that far) Parlay that 5 min theoretical discussion into 10 minutes of conversational discussion on application in practice and for anything less than a lead position I already know if you're "qualified" to be a potential hire or not. I work at a small company with very low turnover so it's not like I've hired bunches of people, but in 10 years I've never hired a bad developer. Doubt I've passed on many good ones, either, though they might get passed on for other reasons.
- _qulr 6y ago
  > Doubt I've passed on many good ones, either How would you even know? Do you do any follow up with candidates you rejected?