Earlier quoted context omitted.
Managers at Amazon are expected to put 5 to 10% on a PIP or manage them out every review cycle. No matter if your team is amazing or not, 5% getting cut.
> Managers at Amazon are expected to put 5 to 10% on a PIP or manage them out every review cycle. A slight correction: An organizational unit larger than a 2 pizza team -- think 50 engineers, is expected to cut 5-10%. A team within that unit may lose 0 engineers, which is how high performing teams that meet all their goals stay intact.
Amazon confirms corporate staff cuts that could hit 10k employees
101–110 of 292 posts
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#102Re: Amazon confirms corporate staff cuts that could hit 10k employees
#103Earlier quoted context omitted.
Alexa does seem like it has fantastic potential. To throw so many resources at it with so little result seems like an incredibly massive failure of management.
Alexa was Jeff’s pet project. Management failure, indeed.
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#104And how much is Bezos worth? If your company is posting profits and executives are rolling in unprecedented piles of money there's no excuse for layoffs.
And perhaps you’ve forgotten, Bezos isn’t CEO any more and doesn’t have anything to do with day to day Amazon.
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#105And how much is Bezos worth? If your company is posting profits and executives are rolling in unprecedented piles of money there's no excuse for layoffs.
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#106And how much is Bezos worth? If your company is posting profits and executives are rolling in unprecedented piles of money there's no excuse for layoffs.
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#107Earlier quoted context omitted.
So it's "bad micro-service architecture imposes a heavy penalty on team co-ordination", then. ...which is a fairly obvious observation. "Bad imposes a heavy penalty on team co-ordination" is generalizable.
There is no bad vs good micro-service architecture. It is just that micro-service architecture imposes a different kind of penalty on co-ordination and debugging. Instead of intra-component dependency, it moves it to inter-service dependency. Each service might look simple, but the complexity is moved to service communications. It is not that obvious, imho.
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#108And how much is Bezos worth? If your company is posting profits and executives are rolling in unprecedented piles of money there's no excuse for layoffs.
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#1093% is 6 months of unregretted attrition for Amazon.
Re: Amazon confirms corporate staff cuts that could hit 10k employees
#110Earlier quoted context omitted.
The biggest bloat I've found in big companies is duplicate teams. You have one problem needing to be solved and a couple VP's running a program trying to make it happen under their domain. I generally see this play out as, one team trying to tackle the problem with a prototype and demonstration of tech. The other team just acquires as many people as possible and writes a bunch of documents. Then it gets run up the fl…
I used to see this occasionally and always see it as wasteful. However, there is another angle here. Imagine your a C-Suite or senior level manager and you have lots of resources at your disposal. Now you have identified a strategic widget you need to get to within some timeframe, say 2 years to lay into your grand strategic vision. Scenario A: Task a single team, staff them and let them do their thing. Cross your fi…
What actually happens is Scenario C - it doesn't arise from a top-down planner mandating it, it arises from middle managers (or their subordinates) further down the food chain each trying to grow their own kingdom, who all get the same idea at roughly the same time, and each build their own solution to the same problem.
During times of plenty, or if the top-level planner is only absent-mindedly managing that part of their org, the firm will be willing to tolerate these competing implementations, but during lean times, they cut, cut and cut and consolidate down to one winning solution.
A lot of corporate politics and strategy makes a lot more sense when you start looking at the personal motivations of the participants in it.