Not snarking, but you either have a needlessly arbitrary bar, or you've left the applicant pool up to people unqualified to gather applicants (non technical young HR, etc)
It’s LinkedIn jobs board + HN who is hiring. Everyone who applies tends to have some development experience. We interviewed maybe 30 best resumes out of the 3k applicants. Lots of people fail relatively basic python or typescript coding challenge, a few fail basic “designs an api” round. We did filter a few people in culture match but thats rare, most fail the technical rounds.
During the actual job I've never once had issues of any kind, but my brain just shuts down in interview environments. I'll forget the simplest of things that I do literally daily, and it all just ends up spiraling out of control from there. It's like there's 2 people in my brain, the regular, competent me, and then interview me who's a bumbling buffoon that I myself wouldn't hire. It's not even a pressure thing, I do fine in high stress environments, it's just specifically during interviews where things go wrong.
I hear you. I was that person once. I was able to overcome this with deliberate practice. When I was doing that, ~20 years ago, this problem was far less understood. But these days, there are many more resources to help you. Best wishes!
Yep. We pay a lot. We are a company you've heard of and we're doing well. For our systems engineering roles, we've had a hell of a time finding good people. Plenty of interviews with folks who turn out not to know basic C programming or systems level algorithms.
It seems like systems level programmers are either firmly employed somewhere else or have switch roles to an easier domain. I know I've considered going back to Python programming where I can make the same money with a lot less work.
Where "turn out not to know basic C programming or systems level algorithms" is failing some leetcode puzzle they have not touched in the last 20 years while they have been full time writing C and C++? So hell of a time not finding your definition of 'good people' would be kinda expected.
OK, yep I get that. Excuse my cynicism. True, most of us system programmers could describe, in detail, malloc and free from scratch and write a basic malloc from scratch and then know why the basic K&RT whipped up malloc would actually be quite crappy when faced with real world use.
Not snarking, but you either have a needlessly arbitrary bar, or you've left the applicant pool up to people unqualified to gather applicants (non technical young HR, etc)