Engineers cost twice what they cost here in Stockholm. Then the Sponsorships in the Valley - Berkeley AmpLab. IMO, much of that is wasted. They want to build a halo effect, but are failing miserably. You can survive (and even thrive) outside the valley.
It turns out that unless you're one of the big tech giants, or a super cool startup, you will not be hiring the best in SV. And you'll be paying for the privilege.
Most of these companies are now learning that Midwest based employees are just as good as their SV counterparts, and cost a whole lot less.
And in that scenario, you're extremely vulnerable to that senior employee getting burnt out from spending most of their time doing code reviews and putting out fires rather than building things themselves. You're also vulnerable to that person getting an enticing offer from a big-name company in the valley or an exciting-sounding startup in SF. Many of these opportunities are even remote, so this can happen even when your best employees don't have any desire to move.
So yeah, it's possible to find good talent in other locales. But there's a lot more competition for that talent, it's hard to build a critical mass of it when the best employees are constantly moving away, and there are a ton of challenges you have to deal with as a result.
Smart engineers evaluate opportunities based on hard facts rather than "oh cool its a cool startup with ping pong in the office!" etc. I don't know why this image is so common when so many of the smartest people I've worked with have not been swayed by it as much as objectively assessing the cold, hard facts as to: what they would be doing, who would they be working with, what sort of impact can they have, etc.
Ericsson has to find it's own way through these troubled and quickly changing times. There are many areas such as Virtual Network Functions, Internet of Things, Hyperscale Datacenter System and many others which are being heavily worked upon and I think will give some good results.
I can see in my own case 8 years back there were 12 people in team and now just 2. Slowly product got stable and people left for other opportunities and positions were filled for short time or never filled. But from business perspective this application is working just fine with few fixes here and there. There is no brand new next-gen replacement that would need scores of developers.
Most products go through a cycle where you need a lot of people to develop them at first, then they stabilize and require fewer people, and the other people move on to different products.
You can't just look at one product or team in isolation -- as long as there are new products to be built, there will be a need for those workers.
New products will be built always but with multilayered designs, more and more functionality is going in libraries/frameworks in lower layers. So a new product started today will not need as many developers. Again I am not arguing about the general quality of such product but new developments are using fewer developers than past.
A lot of the workers in India, for one example, worked on things you would hardly call programming. e.g. creating charts from data, manually moving data from db to db etc. These kinds of tasks should have (IMO) been automated in the first place, and should not require full time employees to handle them. As the automation become more mature, stable and well adopted, the bigger vendors start using them and don't require fleets of humans to manage them anymore. For a concrete example, I think ansible (and related tools) probably "destroyed" thousands of jobs as you didn't need to manage bash scripts manually etc.
There is another fleet of people who are hired simply for maintaining, developing on legacy systems, people you wouldn't find in the US. e.g. COBOL programmers.
[1]Well, we do, but nothing that's implemented on a large scale yet.