Companies typically complain about "lack of talent" so the government will let them import more low-paid developers from abroad.
There is ample proof that the tech industry fails to tap into many existing talent pools.
For example, SV couldn't afford to be openly ageist if talent shortage was really its top concern.
You are right that if companies were really so desperate for talent, you'd see a lot more willingness to compensate developers in various ways.
Much of agism is actuulay moeny related too.
While allot comes from the belief that "young people are just smarter" (as opposed to whites or men as was the "common sense" in the past).
Much of the discrimination is because it is assumed that after a few years, technologists actually know how much they're worth while the fresh college graduate etc is awestruck by a wage that is barely over bay-area poverty line: There's an assumption you can't get a bargain hiring the over 35 set.
I think this was a key part of the racket:
Faced with the need for engineers, employers offered very high entry-level wages for engineering positions. For most of the past 20 years, entry-level SWE pay was among the best you could hope for as a fresh graduate.
However, once an engineer got into "the system", they became "captive audience", so wages could be frozen. Imagine a typical 35 year old engineer with 13 years of full-time programming experience. What's he going to do about his frozen wage? Go to medical school and become a physician instead?
So engineers started at or close to $100k, but then got stuck in the narrow $100-150k band for the rest of their career.
Like most unfair practices, this one worked... for a short time. Longer term, it was destructive and self-defeating: the smartest, most far-thinking college students did their research, saw that the entry level wages were appealing, but then they become stagnant. It's a bait-and-switch. Looks good from the outside, but after a few years, you start lagging far behind your peers who went to finance, medicine, business, etc.
So they went into those fields instead.
These are exactly the type of smart, capable, senior software engineer that all these clever employers wish they had right now.
Congrats, you played yourselves.
Most of the world’s developers aren’t doing anything that complicated. Yes I am a developer, and I command a slight market premium because of my architecture experience, but I am not the force multiplier that I was as a dev lead previously. I self demoted for a lot of reasons (for the same pay) but I know that my work isn’t as impactful.
So you recognize even a single simple project like a single SAAS CRUD app requires at least one smart, capable, senior engineer (your architect).
Also, I'd say you're overestimating my definition of "senior engineers". A senior engineer is someone who actually completed a project or two. Someone you can entrust with big chunks of development work and be reasonably sure they won't mess it up.
Your "mid level developers" are likely senior by this standard, especially since the alternative, "a junior", typically means someone fresh out of college (or boot camp) with about 0 real world experience.
In that case would I have been considered a “senior developer” straight out of college since I was entrusted to create a fairly large system by myself in the mid 90s? I had spent close to 10 years by then as a hobbyist.
If a person who has just completed a project or two and doesn’t know anything about designing large, scalable, maintainable, systems and doesn’t know anything about infrastructure is a “senior developer”, we really either have a horrible level of title inflation in the industry or we just call everyone senior but some are just more senior than others.
I’ve been a software developer officially for over 20 years, but I know I really only have the last 10 years of experience and the first 10 or so were only worth about 2.
That being said, I agree that any real experience as an individual contributor over 10 years, isn’t worth much for most corporations. On one hand, your salary does peak, but on the other hand, so does your value to the company. As an individual contributor, you only contribute X number of hours worth of semi-commoditized value to the company. As a team lead or technical manager, your knowledge can easily be multiplied across the organization.
Is it really stuck if you're making more than 70% of America? I'm sorry you can't afford a summer house in the Keys, but you have to accept different careers have maximum limits, and ours tops out a bit above rocket scientist.
> technologists actually know how much they're worth
If they can't find a job because they want more money than the market is willing to give them then they clearly don't know how much they're worth.
The truth is that there's no shortage of competent people who'd like to be airline pilots. There's arguably not even a shortage of competent people who already possess the training and credentials. There is a shortage of people who are willing to put their expensive training to use at the near-starvation wages offered for entry-level positions with US airlines. So people either don't bother learning to fly, or if they do, they go sign with Asian or middle-eastern airlines, which have been expanding and are willing to pay good salaries for US-trained pilots.
Would you argue that pilots who demand more money than a US airline is willing to pay "don't understand how much they're worth"?
It's not (fundamentally) about money and not (fundamentally) about skillset.
It's about tossing out any resume of a 40+ year old because tech is "a young man's game".
Why is it "a young man's game"? Because that's the current perception and that's it.
People become managers, generally, because they want to be managers. Why do they want to be managers? Well some are just assholes who like to boss people around but for most it's because their definition of career success is "becoming a manager".
Those people look at people who have similar years of experience but aren't managers as "losers", and don't care about or don't understand the reasons, i.e. many people actually prefer to remain ICs.
More broadly, I would not want to be the over-40 guy trying to interview for any team where hardly anyone is even close to 30.
Such teams are quite common, especially in startups everywhere, and not just in SV, unfortunately.
I'm not affected by ageism myself (yet), but even if it was only in SV, which is the biggest tech hub in the US, then it would be a huge problem.
But ageism is rampant outside of SV as well.
After staying at one company way too long and becoming an “expert beginner” in my mid 30s, I had to basically start over and work my way back up to an architect level position. By “Architect level” I mean either officially by title or by responsibility and respect over the last 10 years. I had no problem getting development jobs. The issue I found isn’t ageism with people over 40, it is that they haven’t kept their skills current, are stuck in thier ways, and/or don’t respect thier younger team leads.
I'm not affected by ageism myself (yet), but even if it was only in SV, which is the biggest tech hub in the US, then it would be a huge problem. But ageism is rampant outside of SV as well.
Despite the common perception on HN, there are plenty of places outside of SV where a software developer can make a high enough salary to live an upper middle class lifestyle in a lower cost of living part of the country. $135K-160K goes a long way in most of the country and there are literally millions of jobs out there for software developers at profitable companies not looking to be part of the “bro culture”.
I'm now wiser. Startup culture is toxic and I prefer to stay away ...
I do not claim they ask for more, I claim they are perceived as being savvy: They are perceived as costing too much whatever the price.
But either way, if there's a shortage of technologists it's because the market isn't paying enough not that the candidate is asking to much.
That would be my assumption as well. Young kids are willing to work hard and smart while all the credits from their work go to whoever hired them. They still believe that just by being (technically) good they can thrive and become successful. Whereas their opponents, not other developers but mid-level management are not trying to be "good" they are trying to profit from others' work.
An older more experienced person realizes that much of the value of the software is because of what they put into it. They can also easily explain why that is to the senior management and therefore they are a threat to the mid-level management who are getting older themselves and don't want to fall off the shelf.
It's a game, people hiring developers are not looking for smart developers, they are looking for developers they can profit from and who they don't perceive as a threat to themselves.
Because probably only larger companies (very difficult for startups to innovate here!) can actually afford individual offices, and it's not exactly trivial to re-arrange, I think it just takes a long time for the conventional wisdom to change.
I agree, I just don't think it's as much about cost as you might think (or as I used to think). Profitable companies can afford office space.
I feel like at some point (around the turn of the century ~2000) it was cool to be open office, if you weren't you were uncool, and the latest hipster generation didn't want to work for you.
I think things are changing though, and people are seeing past the latest fad of what people today call "open office." It just takes a while for the general-pop wisdom to change. Nobody's ever been fired for building open office, during this latest phase.
We were already open-floor, and they modified the plan to pack us tighter. Nobody ever thought that was "cool", in any way.
After just a month I was able to convince my manager to allow me working fully remotely and I only showed up in the office about once in a quarter while working 350km away. I could not have been happier but apparently once I reach tenure I would have to be hired and could no longer work remotely.
In the words of another: "Remote means you aren't interested in advancing inside the organization"
Do they really want the work done, or do they want to actively encourage inter-office politicking? Not everyone wants to advance, and even in places I've worked where I've wanted to advance, it was made pretty clear that nothing was going to be happening on my time schedule (too many other people who'd "paid their dues" ahead of me already). So... wow - I was interested in 'advancing' but they weren't interested in me advancing. Would have been easier if we'd just... focused on the work, no?
It turns out that being able to spend every moment in the office promoting yourself as a "10x rockstar" was more important than ever delivering a single impactful project.
Wouldn’t it be an upside to a mediocre manager to have underlings not trying to escape their team nor gunning for the manager’s position?
It's more like nobody believes he is needed if he is the only person in the office.
Most people really need the “structure” of an office to actually get work done... for some reason.
But... the savings won't be that much. I mean, for normal people it would be, but imagine you have a bonus tied to a % of cost savings. Do you propose something which might bring about a 20% cost savings? Or a 75% savings? Of course, I just pulled those numbers out of thin air, but the cost of, say, mid-level developers in SF isn't going to drop significantly, moving to a reasonably-high-tech hub. The base salary cost may go down < 20%, but any other attendant benefits (insurance, retirement, etc) don't go away, just might be shifted a few % - or might even go up(?)
I hear the complaint about not finding local engineers in those places. Thing is, we don't find any local engineers in SF either. Maybe 2-3 people out of 100. Everyone else is a <5 year transplant, relocated either by us or their previous employer. We have more people from the same random Chinese high school than from California.
You probably wouldn't, though. You're probably not going to relocate to Tulsa or St. Louis or wherever, because once you start looking at the decision seriously, you're going to realize that even if this one particular company has attractive jobs there, if you ever want to leave or get laid off or whatnot, the rest of the job market there ain't so great.
It's the kind of thing that sounds great initially, but starts to fall apart upon deeper analysis.
I live in Colorado and over the past couple of years have seen a lot of Bay area companies coming to Denver. Not sure if they are moving SF engineers over, but they are definitely building teams in these lower cost areas.
It's not just about number of tech jobs, but the quality thereof.
These days, programming is such a needed skill that coders are almost like accountants, practically every business above a certain size needs at least a few for internal tools. But that kind of work makes you a cost center, with the attendant technical and cultural problems.
What the major tech hubs offer is an abundance of even high quality programming jobs, in a wide variety of fields.
Only people I know who can make that work have either doctors or other software engineers for spouses.
So if you move, start a family because you can now afford it, and then lose your job 5 years later, you're going to be less mobile and also limited by job options.
At least that's my impression given how many of my senior coworkers have absurd commutes as they continue to live in the same house they had before joining.
I agree it’s weird to invoke the word senior so early in the job ladder... I would expect 3-4 more rungs where Eng II currently sits.
In another comment you suggest that you'd pay $350k, but at $700k you would suspect their loyalty. I'm in Portland and not interested in moving to SF, and if you're offering $350 - $700k comp I'd be happy to talk with you. :-)
Honestly, comp numbers are past the point on Maslow’s pyramid where they can get someone to care. If you’re not going to get a guy for $350k but you can get him for $700k, he’s not planning on sticking around and he can’t produce $1.5m of value in his one year that he’ll stay for the payout. Few people are like that. It doesn’t make sense to optimize for that.
Seriously, I’ve had people move from here to Texas or Washington, and they keep the straight bump in wages that comes from not paying state tax. But that’s a single digit number out of a 100+ team. It isn’t helping expand the team.
The high-cost markets have too much momentum/desirability (other than the expense). Harder to find and recruit in them, I'd imagine.
Office space is probably hard to get/expensive in those high cost markets, so harder to do stuff other than open. Still would love to see it though.
When everyone is onsite except for a few team members, that's a recipe for disaster. Everyone needs to go remote.
I am the hiring manager for my group, and it is very challenging to find people in the US market.
These are all amazing cities and for some reason tech companies choose to locate in San Francisco over these places... It honestly boggles my mind.
Southern US - Raleigh < Atlanta = Austin
Those of us who are very much not developers in that 'community' are not screaming and are actually finding the jobs that satisfy our needs. That's a lot more effective than screaming at companies who don't actually want to work the way you do; and they're fully entitled to shaping their own culture and prioritising their own values. Values that may include: working face to face, physical collaboration, etc.
So how about looking for companies who share values instead of screaming at those who don't?
B: Have you tried offering what they say they want?
A: How dare you? Stop whining and get back to work.
A: Now, as I was saying about that developer shortage...
Yes, people who are satisfied with what’s currently on offer are satisfied. What exactly are you saying?
Face to face conversations work just as well wherever you are, and research indicates they are actually more prevalent when both private and collaborative spaces are available vs. one room for everything.
- Go full remote
- Locate offices in reasonable COL US markets (my company has overwhelmingly rejected this one and skipped from NY/SF/Seattle to the developing world).
- Provide private offices, cubes, team rooms... any kind of workspace other than the in-vogue open floorplan barn.
Companies are not in their wildest dreams going to touch any of those things with a 10-foot pole at scale. Do they not know? Do they think we're lying? Or would they just rather complain than actually solve the problem?