Hi, I basically agree. But can you expand on this? What exactly do you (or anyone reading this) see as such a problem with regard to interviewing? Especially, anything you see that's gotten worse.
I've been out of tech for as long as OP, a single thing from my experience so far:
- Stronger requirements regarding specific frameworks and languages.
Generically, five years ago it felt like you could be an all around good engineer in some domain and be a good candidate in an adjacent domain. Today, it seems that you need to be completely up to date on the language in addition to all the best practices, build tools, and _all-in_ on a very specific set of libraries and frameworks. A candidate with any deviation is rejected.
Economics tells us it's because of a tighter labor market but in a way it says to me there's less room for learning and creativity.
If you were to ask me, I would say that middle managers are generally miserable and are trying to avoid risk and maintain job security by NOT hiring people as long as there is VC money to burn. But I'm a nihilist.
I know this is late, but a lot of us really want to hire people, but there are a lot of people out there that are overconfident in their skillset, and sometimes you have to do a quick sanity check to weed them out. I agree, though, that most you can tell before that point. I'd never make someone donate a day to a test, but 15 mins of whiteboarding can go a long way if someone doesnt have a lot of publically available code to go look at (and, a lot of devs don't, due to working on public repos)
1) All day interviews. Seriously, I've had an 8 hour interview. They served me breakfast, lunch and dinner. This was after several other rounds of interviews.
2) Expecting me to perform "free work". I have had several companies insist that I create and submit "sample" projects. This is NOT simple stuff like FizzBuzz. The projects realistically take 20+ hours and are solving non-trivial problems. This is before you even talk to anyone.
3) It can take weeks or months to go through the process and finally get an answer: one way or the other.
4) Companies straight up lie about everything, from working conditions to performance expectations.
- Stronger requirements regarding specific frameworks and languages.
Generically, five years ago it felt like you could be an all around good engineer in some domain and be a good candidate in an adjacent domain. Today, it seems that you need to be completely up to date on the language in addition to all the best practices, build tools, and _all-in_ on a very specific set of libraries and frameworks. A candidate with any deviation is rejected.
Economics tells us it's because of a tighter labor market but in a way it says to me there's less room for learning and creativity.