Ericsson is reportedly planning to cut 25,000 jobs in response to crisis
nordic.businessinsider.com
nordic.businessinsider.com
At least this cut seems to mostly affect Managed Services. That is the division that basically manages telcos networks for them. It was a big growth area a couple of years ago, but turned out to be very low margin.
Ericssons fundamental problem is that their only customers are the telecom operators, and the telcos aren't going to invest in infrastructure unless they have to. 4G rollout is mostly done in developed nations, and 5G is just a buzzword at the moment. Even if Ericsson invents some amazing technology that improves the end users experience, it doesn't mean they will make much money from it.
Of course the price pressure from Chinese competitors has not helped, even if Ericsson has held on to its marketshare.
Is it possible these telcoms will hire some of these Ericsson Managed Services folks to run their networks? I mean, someone has to manage the network.
Otherwise whatever country has the most lax regulation and labor laws wins.
Tariffs can be used for this purpose, but they traditionally weren't used to "level the playing field". They were traditionally used to benefit local goods over imported goods. The history of the US and England are rife with counterexamples of "level playing field" tariffs.
Patent law is far overreaching in both breadth and length. Anything that undercuts it is a good thing.
In any case, I think right now Ericsson definitely needs to assume that Chinese will use their technology at some point and plan for that contingency.
China has WTO trade laws that protect them until a court case makes the connection between intentional IP violations and the unfair trade competition. Even after that is established (which can take many years), China can assert a counter-action using WTO rules to find whatever trade laws those same western+developed countries are violating.
Steve Bannon just talked about this in an unscripted interview for a newspaper. If it happens, pain will ratchet up for everyone involved. It will take a decade or more for all of the ripples of this type of trade war to calm. Until then, ratcheting up of tariffs will make it far more expensive to live in any country involved.
1) Market & Competition: As mentioned in another thread below, Chinese competitors were severely undercutting us (there was constant threat from Huawei). One customer in middle east that I worked with comes to mind. We were developing a complex feature for them (Bridge Virtual Interface [BVI] over VRRP and few more protocols). 2-4 engineers in San Jose and 1-2 at customer site. Huawei had close to 200 engineers on site to address any issue. We just didn't stand a chance.
Chinese companies have huge advantage over West/European companies. Relatively inexpensive, high quality labor.
2) Commoditizing of IP Networking: Ericsson's investment in IP networking was a huge sunk cost. Traditional networking industry is getting commoditized. It's very inexpensive to make a whitebox switch covering good 90% use cases. Therefore, * Cisco's revenue of core networking products is on steady decline * Brocade is being broken up on to pieces and being sold * Juniper has been on market for sale (at least rumors) * Ericsson laid off pretty much everyone in Redback last year and partnered with Cisco in 2015. * Only Arista Networks is doing well.
It's very hard for networking companies to survive any more on core, edge or campus switching products alone.
3) Engineering vs Management: Ericsson brought management heavy style to workplace. It was very different to SV culture. In 2007, from concept to delivering a feature required writing 3 documents. By 2015, we had to write 6 documents. Feature velocity came to a crawl. Engineers clearly felt pulled back. Brilliant engineers, industry stalwarts, started leaving one by one.
3) Compensation: Ericsson's benefits was employee friendly, particularly for engineers with families. Decent work-life balance, good vacation policy, generous health insurance and 401K policy. The base pay was horrible. This is one of the reasons attracting young talent became hard. New college grads were getting offers in $120K-$140K range at other companies (heck, the summer intern I mentored got an offer more than my base pay :))
4) Culture: Slow to pivot. Cisco innovated the idea of spin-in/off to quickly develop products. But Ericsson (and others) took too long to change course. We were always playing catch up.
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.
[1]Well, we do, but nothing that's implemented on a large scale yet.
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.
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.
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.
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.
[0]: https://github.com/erlang/otp/compare/OTP-20.0...master
and a whole sub-community in elixir. erlang is gonna be just fine.
This is something I have seen at prior companies. Still hiring to fix issues from previous overly-ambitious cutbacks. Seems like execs could learn from this...