2 ms·
If interviews measure your actual skills, why do working practitioners study for them? Interviews measure a shibboleth with a glancing relationship to relevant
by closeparen 9y ago
If interviews measure your actual skills, why do working practitioners study for them?
Interviews measure a shibboleth with a glancing relationship to relevant skills, which is more based on expedient and clever solving of the toy algorithms problems you'll find in college than the actual quality of a developer's output. Different companies' interviews attempt to measure the same skills in different and subjective ways, yielding different results.
Centralization on an evidence-based standardized test for the "prove your skills" part of the interview process is one of the best outcomes we can hope for. Ideally it would be open to non-degree-holders. Include per-component scores so companies can choose which areas they care about more, avoid grade inflation so similar candidates are distinguishable, etc.
- orthoganol 9y agoPeople always claim this but it's not true for the majority of companies. Yes some, including a small number of big brands, ask leetcode algorithm whiteboard questions, but most interviews I've ever had are more practical, prove you can build things. That said, I have no problem with leetcode algo questions, as long as the interviewer is only checking for your ability to think, communicate, and hands on experience with a few basic programming approaches (using hashes, recursion, structuring code etc.), which they are in fact excellent gauges for. If balanced with other types of interview challenges, it's not a bad way to assess. (but yes, it crosses the line if they care about the perfection of your leetcode algo; again, most do not)