4 ms·
We don’t support h1b, of the last 3000 applicants we had only 1 was qualified. It’s super hard to hire strong swe.
by ivalm 2y ago
We don’t support h1b, of the last 3000 applicants we had only 1 was qualified. It’s super hard to hire strong swe.
- JSteph22 2y agoWhat kind of salaries are you offering though...
- ivalm 2y agoWe are seed stage startup, we post salary range 130-180k + competitive equity for mid to senior level fully remote.
- memtet 2y ago[dead]
- gedy 2y ago3000 applicants we had only 1 was qualified 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)
- bfung 2y agoNa, the 3000 sounds the like normal flood of LinkedIn type apply now button presses. The real number for them is probably the next few parts of the hiring pipeline after those resumes are scanned and filtered.
- ivalm 2y agoIt’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.
- arp242 2y agoMany competent developers are horrible at these live coding challenges. I suspect at least some people just "failed" out of anxiousness. That said, it's certainly true there's lots of spam in job applications.
- sensanaty 2y agoThis will be my eternal curse :( 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.
- mavelikara 2y agoI 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!
- 01100011 2y agoYep. 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.
- mianos 2y agoWhere "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.
- 01100011 2y agoNo it's more like failing to understand how to implement a basic memory allocator which is a very relevant task for a systems engineer.
- hackable_sand 2y agoI seriously doubt you and ivalm are having a hard time finding SWEs capable of memory management in C. Something is terribly wrong with your hiring practices. You just need to admit it's a "you" problem.
- mianos 2y agoOK, 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.
- Gollapalli 2y agoI am looking to transition into this sort of work from a more "general development" sort of background. Any resources you could recommend?