If you can sit back and pick and choose like this, then how does that square with the mythical "shortage of engineers" everyone complains about?
If you can sit back and pick and choose like this, then how does that square with the mythical "shortage of engineers" everyone complains about?
American companies front-end static pickiness for rando applicants. A snapshot a month ago by a non-technical HR associate indicates the ideal applicant would be experienced with the following list of 25 emacs extensions, prefer while loops over until loops, have memorized everything in Knuth but use none of it on the job, and wear a size 10.5 shoe preferably eee width.
The real world dynamic work experience over the past couple decades is someone comes to with some sob story about "one of our execs went golfing with one of their execs and I know you've never used freetds or mssql but you need it up and running and integrated with out stuff by the end of the week" "what is it?" "I don't know but just get it connected as best you can". Another classic was being on rotating pager duty and getting midnight calls about a product I literally did not know existed, I mean I'm used to handling problems with no training or documentation, that's to be expected, but I didn't even know we were selling this thing. Both stories are true and honestly not very surprising. This is pretty much how "real world" IT works AFTER you're hired. And I'm extremely good at that, its like a giant self solved puzzle, so I don't mind, but I assure you, no one interviews rando applicants for that, even though its the most important part of keeping the job.
Mostly I get work from old coworkers and the first month is just like six months of normal change rate rolled into one, its not really a big deal. Its a forklift upgrade. I've worked thru several of those, a new job is just a forklift upgrade along with a new chair. I could walk into any dev job on the planet and be productive in a month and stay productive there as long as I want. I know three people that experienced up front picky because I got my current gig because I know some folks and HR had to go thru the motions, so they sat thru insane tier interviews that I skipped. Hours of HR style "You reach down and flip the tortoise over on its back, Leon." and it goes on and on.
Not sure about the 95%. Maybe that's people who can do it without bugs nor expressing that this is a very dumb question unworthy of them xD
What I do see and hear about are people that simply do not know how to program. FizzBuzz generally cuts out 50% or something out of the pool right? So that's 200 of those 400 resumes out the window already.
If you can't pass FizzBuzz then I think it's safe to call you incompetent, right? From the POV of paying you to code, obviously.
At least in Berlin there's a lot of competition for "talent" (perhaps we should call them skilled developers rather) and if one can already cut the number of applicants in half before even defining the job description... well then it's not hard to see how there might be a shortage.
However I think if you're looking for entry level developers there are way more options.
I think it's fair to want someone who's experienced or at least has a fair bit of knowledge in either Angular/Ember/React if you're looking for a web dev. The companies I talked to were at least reasonable enough to know that general knowledge transcends whatever's the current hot framework.
I briefly ran hiring for a team with a core skillset that I thought was pretty general (python/web), but a lot of the python resumes I got turned out to be 'I used it in college', 'haven't used it recently', or django-focused devs who were uncomfortable with anything non-django.
I'm not sure what that means other than that I'm bad at sourcing. Seems like 'aiming at my stack' was the wrong way into this, but I'm not sure how else to filter resumes.