Maybe I should get my tinfoil hat checked out, but every time I see a giant tech company with one of those "everyone can learn to code!" pushes, all I see are executives hoping to play the long game and reduce the cost of engineering talent.
Maybe I should get my tinfoil hat checked out, but every time I see a giant tech company with one of those "everyone can learn to code!" pushes, all I see are executives hoping to play the long game and reduce the cost of engineering talent.
Most of the candidates you see either can't pass fizz buzz (no joke), are very junior (have no practical experience building real services), have severe behavioral problems (need to be told exactly what to do, can't be trusted to own a service, etc.), or are washed up enterprise technicians who need someone to build all their scaffolding for them and can't solve simple problems if there isn't an IDE for it (.NET/etc. lifer).
The "smart" version of those archetypes often do OK at places like amazon, which provides scaffolding and oversite, but they will absolutely gut a small startup dev team.
(source: personal experience regretting startup hires who seemed "ok" when we were desperate, who subsequently left a trail of sadness and surprises in their wake through inattention, stupidity, and general failure to care)
I think this is particularly difficult for companies with non-technical founders that might lack strong technical leadership out the gate.
If that conspiracy theory had any bearing in reality then we wouldn't see a) tech workers receiving elite athlete-level salaries, or b) candidates with no formal education being paid handsomely to work in entry level/low complexity positions.
"...elite athletes..."
(any elite soccer player plays in Europe)
In this industry there seems to be no place for someone experienced who thinks that working 50-60 hours a week is bullshit, and would like to work half that. That tells me there's no "talent" shortage, since the employers aren't flexible at all when it comes to working part time and receiving proportionally lower pay. The moment you ask to work less than 40 hours a week the employer immediately assumes that either there's something wrong with you or you're willing to work for peanuts.
Once you start interviewing people, you will realize how utterly incompetent most of them are. I am talking about people with multiple years of full-time experience in the field and a relevant degree who cannot even implement a basic FizzBuzz. And I am not exaggerating it for comedic value, I legitimately met many people like that by now. Prior to seeing this myself, I could've sworn this was just a joke people used to describe incompetent people, but this is real. And being able to pass FizzBuzz doesn't even scratch the surface of being competent, but a lot of people cannot manage to get past that stage.
People with experience have more dignity than to perform a dog-and-pony show for some startup on a whiteboard. Remember, in this market you need them more than they need you.
Every single engineer who was or is employed at any big tech company has went through whiteboard interviews. If you are trying to imply that big tech companies cannot manage to attract experienced people, then I question the validity of that.
Have you considered the possibility that you're asking the wrong questions? Or perhaps your organization isn't good at identifying candidates with low skills but high potential?
Why waste time interviewing incompetent people?
Just ask for code samples (github, stackoverflow, anything else) and make a 5-minute screening call via Skype to filter out incompetent people.
I'm sure all of them can implement FizzBuzz, just not on the interview under pressure. It has absolutely nothing to do with competence, but understanding that requires just a little bit of background in human psychology.
All of these things matter more the older you get since older engineers tend to already have a home and don't want to move to California, have a more involved personal life, and expect things like medical benefits. You might be discriminating on age without consciously knowing it.
1. Increasing wages.
2. Increasing benefits. (More vacation time, paying for employee education, shorter work-weeks.)
3. Lowering the hiring bar, and spending more effort on mentoring and educating new employees.
4. Hiring remotely.
These all, of course, come with costs, and trade-offs.
If you don't mind me asking, are you looking for FAANG-level talent? If so, are you paying FAANG-level wages, or providing MicroFaceGoog[1]-level work-life balance?
[1] Yes, there are obviously teams at all of those companies that work on death march schedules. They are, generally speaking, the exception.
And lets be honest, looking at most job postings, most people have absolute ridiculous expectations of candidates. Most things you can and should be able to train to some extent on the job.
You're reading too much into those requirements. Nice-to-haves are not must-haves. I've been involved in hiring processes for a front-end position that listed non-trivial experience with React and among the half dozen candidates who applied the company even considered a high-schools dropout who only had to show a 50-hour HTML online course.
That would be the case if we had too many applicants! It seems we need to use a recruiter or something, everyone here seems to think its ridiculous that we can't find people.
I'm not. I'm an engineer on the team and I wrote my comment (passive-aggressively) because my workload is ridiculous. As I understand it, we're having a very difficult time finding people.
Another possibility is that they don't have enough money to hire another developer, but don't want to admit it to you. Start-up life can be harsh.
Don't burn yourself out. I can tell you from experience that it gets harder and harder to come back from burnout each time it happens. If your workload is ridiculous, it may be talk to your boss about adjusting timelines/expectations to something more realistic, or even time to start looking for another job.
Generally I’ve just gone by industry reputation, for where to go. But I wonder if there are any hidden gems out there.
Companies in the US don't advertise pay ranges, but they are easily Google-able, people have friends, Glassdoor is a thing, etc.
A junior at Facebook will make ~160k/year, someone good with ~5 years experience (at FB) will make ~300k/year.
Most startups want to hire the latter person for the salary of the former, while getting them to work harder, for fewer benefits, and fewer vacation days, all in exchange for...
An equity carrot, that has a 1/500 chance of materializing into anything more than lunch money?
A chance to 'change the world' - as if writing an app for ordering dogsitters on demand is the moral equal to providing clean drinking water to poor villages - or curing cancer.
A chance to be a big fish in a tiny pond? You'll still probably be second fiddle to the CTO, and employees 2 through 5...
Meh, glassdoor is off by a factor of 3x when checking in with a few of the companies I just interviewed with. They seem to require an account, but it’s similar to reports like this which are comically wrong:
https://www.indeed.com/salaries/Software-Engineer-Salaries-a...
Sure, you can reach through your network, but price discovery seems pretty bad if you have to do word of mouth.
You are posting in probably one of the most fertile places to find talent...and there is no link in your bio to your company or personal email.
No wonder why you can't find talent.
Sorry for the snarky tone, but it should be evident by now that the real shortage is for "highly talented souls willing to work for peanuts"--which is kind of oxymoronic. People want to hire "highly talented" and smart individuals, but expect them to be dumb enough to sell themselves short?
The startup offers I've seen in the bay area for SWE a couple years out of school are pretty high, $150k - $185k which is pretty good cash comp from a startup.
Higher than that is probably not a realistic expectation for most startups that are not flush with cash. They'd probably be happy to pay it or more for John Carmack, but you're probably not John Carmack.
For the same reason it's easier to hire an actor in LA.
I agree that is pretty good for a Bay Area startup, but it is far below the total compensation a FAANG company offers today.
After several years, the RSUs at a FAANG could pay out more every year than the salary, and they are immediately sellable on the open market. Startup options are likely to be worthless.
This is why startups have a hard time hiring. A lot of engineers would rather work for FAANG or similar large companies, where they will make a lot more money with much less risk.
OP seemed to suggest that startups have trouble hiring because they don't pay enough and I think that's not entirely true from what I've seen. They don't pay more than FAANG which is expected, but they're not underpaying for that trade-off.
I do agree though that FAANG salaries have gotten extreme so it's a harder opportunity cost than it used to be. If you can swing $350k at Netflix or $200-400k+ total comp at the others and you work there for 5-10 years that's basically a small startup exit. I think it used to be less dramatic.
I think the misery of the technical interview process is actually the thing that limits mobility most. Some of my extremely capable friends (that do work at FAANGs) don't optimize on moving around or income as much as they could because the process is so painful and anxiety inducing.
> Higher than that is probably not a realistic expectation for most startups that are not flush with cash.
Then isn't this an admission that there is no talent shortage? Again, that just means there is a shortage of talents who are willing to take the offer and work for $150k.
If you imagine there is only one employable tech worker, it'd be strange to claim that there is no shortage because you can hire away the one worker for a 20million dollar salary (or whatever the highest salary is to outbid all of the others).
Not everyone is good at being an investor, but it's not entirely luck, there is skill in determining what companies are good and what companies are not.
> We can't find anyone worth interviewing right now
How can both statements be simultaneously true.
Why not post a link to your job?
1: The definition also includes the fact that employers are more reluctant to lower wages than they are to increase them, all else equal.
If you are willing to deal with a bit of hassle, hire Canadians. Same timezones, same CS educations, same language, probably a little cheaper (sorry, fellow Canadians), lots of interest in US startups.
There is enough research in job markets showing that companies get more picky and advertise more demanding and complicated job requirements as more candidates are available. So your claim is empty, since this is how companies behave regardless of supply. And if you were to measure it, how big artificial barriers or filters are for someone to get hired could be the measure of oversupply, not shortage. With shortage there would be no barriers, everyone applying would be interviewed and likely hired. But given current hazing hours long interview practices it's pretty clear that companies are drowning in oversupply.
shortage is real. We can't find anyone worth interviewing
That's an odd statement. Unless you are flying somebody in, the cost of an interview is trivial compared to broader onboarding costs.Perhaps a mention of your specialty and location is in order. Your HN public profile is blank.
didn't twitter ban people for saying this at one point :D
That depends on what level of experience you are looking at. In particular, based on my experiences, your premise is the reverse of what is happening:
> to increase the supply with younger, less expensive workers who are more easily exploited for long hours and poor conditions
In the U.S. this does not match what I see. Instead, there are a ton of positions for "senior" positions that are filtering on specific amounts of experiences in such a way that there just aren't enough people that match. Likewise, the field is VERY CROWDED with newer devs that lack experience - they fight over a relative handful of positions that have truly absurd entrance requirements.
This also results in some layers -
- The layer of places that abuse their newer developers and get away with it because that initial field is so crowded. This would seem to support your premise, except they aren't the ones pushing the "tech shortage" narrative - they are just profiting from it. Devs that can claw their way of out of this layer are well-positioned for "time", but likely lacking in the specific experiences and breadth that the other layers want.
- The layer of "top" places that want devs with enough experience and mix of skills that they have a hard time hiring for them. These places pay top dollar and work on their reps to help attract talent - they also are trying to resolve their shortages by getting new grads as interns. This layer is the primary cause of the problems, as I'll note below.
- The layer of "middle" places that are trying to use devs to help generate or streamline profits. They want people with enough experience and independence that they are drawing on the same pool as the "top" places. Because they have to compete with the marketing and budgets of the top places, they never have enough people, so they try to make up for it by getting more "senior" people, which only helps feed the scarcity for the "top" and the lack of jobs for the newer devs in the "lower" layers.
What you end up with is a weird divide - the top jobs pay great, but demand you have things like a degree (it's rapidly becoming a requirement DESPITE so many successful pros that either don't have a degree or have an unrelated degree), that you solve increasingly complex algorithm problems despite that rarely being a demand of the job, and wanting a breadth of depth of experience that few jobs will prepare you for. They face a tech shortage and feed it. Meanwhile the lower jobs have lots of supply, so they can abuse their devs, but rarely provide the necessary qualifications for people to advance to the other tiers. And in the middle you have companies doubling down on their chase after the same smaller pool of devs that the top layer has rather than taking in from the huge supply of less experienced devs and growing their own talent.
In the 3 companies I've worked for in the last 10 years (prior to that I had no input/visibility into hiring decisions), each one ramped up their entrance requirements to the point where I almost certainly wouldn't qualify despite being a successful and apparently valued employee at each of them.
> executives hoping to play the long game
This is contrary to my experiences with executives both personally and in most companies. Indeed, the "long game" seems to be invoked in words far more often than in actual consideration. YMMV.
Are you in SV? It's almost exactly the opposite in the metropolitan area I live in (one of the markets on this list [1]). There are many hundreds of hiring junior dev jobs open at any time, and constant emails about junior or what are essentially junior jobs.
But there are only a very small handful of senior jobs.
I'm very happy where I'm at right now, but it makes me uneasy. Based on my experience with applying to jobs for which I was "overqualified" as a recent college grad in the 1990s, I wouldn't be able to snag any of these junior jobs regardless of the salary I was willing to accept.
1. https://www.aitp.org/blog/aitp-blog/2018/10/23/tech-town-usa...
While the ratio of junior:senior jobs isn't as low as it is in SV, it's not nearly as bad as I made it out to be. There are still more non-junior jobs here, my previous statement notwithstanding.
The reality of most 'talent shortages', and this goes for people outside of tech, is the people with capital don't want to adjust their business model to deal with changing market conditions.
Tech companies complain about 'talent shortages' in a time... when you could literally hire any programmer anywhere in the world to work remotely! It's insane.
So it's obvious there isn't a shortage of talent, but a shortage of local talent. But why do they need local talent?
It's like the US military complaining they can't get tech people. But if you work for them you can't smoke weed (even with a medical rec), you have to be in on time, wear a tie, punch in, sit in a horrible cubicle with horrible lighting and comply with a million bureaucratic minutia. So they don't get good candidates.
Somehow the responsibility of of BOTH sides (labor and capital) to adapt to an ever changing environment seems lost on some people. They can see why one side should adapt, but not the other. The right sees that labor should adjust, and they are right, but likewise capital should also adjust when market forces push them, and not cry foul.
I'll believe there are labor shortages when labor is paid the same percentage of GDP as it was in the 1960s, and when compensation packages include greater variety. After all, truly competitive markets will offer greatly different options. For labor, that could include working remotely, offering more days off, more vacation time, the CHOICE of private offices and/or open office, better indoor lighting, etc.
Note: I'm a realistic capitalist who has actually read Adam Smith's Wealth of Nations.
you have to be in on time, wear a tie, punch in, sit in a horrible cubicle with horrible lighting
I worked as a software engineer in defense (mumble) years ago, and even then nobody punched in and nobody (except management) wore a tie.We did have cubicles, though... which I prefer immensely to open desk plans. And I'd be happy to bring in my own adjustable-spectrum light if they haven't upgraded lighting in (mumble) years.