It's been over a year since Uber laid off about 20% of it's engineering organization. In my observation, the layoffs - and how they were done - were one of the biggest mistake the company did: and something other tech companies should learn from.

Thread with my observations.
(Note that most of this thread is my take, but I've talked with several Uber engineering leaders who were there at the layoffs at the time)

1. The plan, as I understand was simple and finance-driven. Cut the cost of engineering by X%. This mandate was passed down to each eng org
2. Alarm bells were rang early at each level on what this would mean. Leaders warned that by cutting 20% (even if it's the "bottom" 20%) this would have terrible consequences:
- Top performers would leave
- Hiring would become difficult, if not impossible

People said their part.
3. One eng org that did not have any cuts was India. It was clear enough to anyone paying attention: much of the US engineering efforts would be moved over, eventually, some starting with the layoffs. Cost was the driver here.
4. The layoffs happened. They were swift and efficient, and over with (except for in Amsterdam, where local regulations dragged this out for 1-2 painful months).

And then the exact thing that people warned in #2 started to happen:
5. A few top performers in the US started to quit. This put pressure on hiring more in India, and faster. US teams were asked to help with this effort.

If the direction was unclear to anyone, this made it very clear. People in the US started to quit in droves. Surprise?
6. This was the folks in #2 warned about/predicted. Now leadership reacted with retention bonuses, and allocating bonuses early.

The damage was done.

This was when I also decided to leave: it was clear Amsterdam would get no investment in the near future. Also, my time was up.
7. The eng hiring funnel and branding built up over years suddenly collapsed. Hiring in the US became expensive: and given a choice, would you join a company that laid off 1/5th of engineering?

In India, hiring was tough, and (predictably) slower than planned.
8. How did other companies handle layoffs?

I rarely use Booking .com as an example, but they are a good one. Their revenue collapsed, similar to Uber. They, however, knew that laying off engineers would be hard to recover from. So they laid off...

no one in tech (eng/PM).
9. As it's predictable, Uber is hiring back all the headcount they let go a year ago, and then some more.

Decisions will be nuanced at the C-level, but I could not find anyone who agreed within engineering leadership on the layoff strategy: exactly because most predicted this.
10. What's there to learn?

If you're a tech company, don't treat engineering as a cost center, including at layoffs. Yes, it's much simpler to do so: but you'll pay a hefty price for it.

Just like Uber paid the price by cutting the bottom X% and losing their top X% as a result.
11. One thing that I honestly believe Uber leadership did not expect was the hot job/investor market for engineers.

Most tech folks left Uber for a *lot* better opportunities. May got a fat raise. Others started a company with huge (pre-) seed rounds.

Layoffs were the trigger.
12. The effect of layoffs did not stop in a few months.

Many long-tenured folks eventually came around to leaving: the layoff trauma was usually the trigger.

Layoffs made everyone realize the "mission" is great, but profits come ahead of job security.

Layoffs shape culture.
13. With every layoff come the "told-you-so" stories.

E.g. complete teams were laid off owning key prod services. The next day was a manic scramble to even get credentials to operate them.

These just added to the feeling that leadership either doesn't know or doesn't care.
I can only share this since I left Uber: I left Uber with an official HR warning triggered by layoffs.

I sought advice from fellow engineering managers on the Rands leadership Slack who went through similar layoffs.

Someone at Uber reported me -> HR investigation -> warning.
(I got the warning the day after I handed in my resignation, but it amplified the notion that process was more important than Uber than doing layoffs right.

The advice I got in private helped me navigate layoffs - but HR and the anonymous Uber employee reporting me disagreed.)

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Gergely Orosz

Gergely Orosz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @GergelyOrosz

15 Sep
Uber's CTO, Sukumar Rathnam stepped down just 12 months after joining the company.

I left Uber shortly after he joined as CTO, and here are my thoughts on this departure, from the sidelines. A thread
1. This was never meant to be an easy job. SK joined after the 2020 Uber engineering layoffs, low morale, and sinking stock price.

By the time he was in, attrition was high, and he had large shoes to fill that Thuan Pham, Uber's CTO of 7-years left behind.
2. Uber was also without a CPO at this time: Dara stepped in to fill this role. One more challenge.

3. The tension with what engineering wanted (build for the long-term) and Uber's business needs (get to profitability the short- or medium-term) were always at odds.
Read 9 tweets
14 Sep
The tech hiring market has never been this hot: not even during the Dotcom Boom. I talked with dozens of tech hiring managers (from managers to CTOs), swarms of people switching jobs to answer:

Why this is happening, and what are companies doing who keep growing?

A thread:
1. Covid-19 being the tipping point of companies going all-in on digital. Not just e-commerce, but all industries are investing *big* money to move to digital.

No industry is absent. E.g. look at Best Buy tech spending 📈(screenshot from my report newsletter.pragmaticengineer.com/p/perfect-stor…)
2. Capital markets, Big Tech, New Big Tech. Flush with money and pushing the top of the market. Enough said.

3. Pent-up demand from 2020. Covid-19 made business very cautious in 2020. Projects were halted. They're back in 2021, with a budget to get it done.
Read 8 tweets
8 Sep
What are Platform teams, why are they important, and why do (almost) all high-growth companies and big tech have them? A thread.

1. The easiest way to visualize Platform teams is blocks of specific types. Other teams (called Product/Program) use these "blocks" to build.
2. Platforms are focused on a technical mission, rarely have cross-functional engineers (e.g. mobile & backend folks) on the same team, and customers are (usually) internal engineering teams.

Examples include infra-like Platform teams and Product Platform teams.
3. Why even have a Platform? Could we not just... do what we do?

Platforms own very specific goals, often tied to non-functional capabilities like performance, reliability, compliance, security etc.

Yes, you could do without them: and every single team would need to own these.
Read 6 tweets
8 Sep
A daunting thing about mobile development is just how poor the tooling landscape is in 2021.

I suspect Apple's decision in 2010 to basically ban code generators - bankrupting dozens of startups overnight - is a huge reason.

It could happen again. It's a risk to be priced in.
This is true for backend-driven mobile apps as well: the App Store Guidelines are very vague.

It's why e.g. hot reload on RN is something any sensible company steers clear of in prod. Yes, it works: but it *could* get your app banned. For good.

It holds back the ecosystem.
I do wish that Windows Phone would have succeeded in staying relevant because it would have led to *much* more competition.

Microsoft was dev-first in their mobile approach. Their A-team was building the dev tools.

Apple - let's be honest - is consumer-first, developer-last.
Read 7 tweets
7 Sep
Interesting responses so far.

- Big tech & high-growth unicorns tend to give autonomy on project management. Eng usually runs projects. Scrum absent, kanban sometimes used.

- Startups mandating Scrum with dedicated project managers seem to have the lowest satisfaction ratings.
Please feel free to share how projects are run at your company (including anonymously). docs.google.com/forms/d/e/1FAI…

I'll share the draft write-up with those indicating interest.
The most unexpected result is how the *only* places where people rated satisfaction with a 1 or a 2 was... places where dedicated project managers or product owners ran the projects.

Places where engineers, tech leads, or EMs did so showed higher satisfaction.

Food for thought.
Read 4 tweets
22 Aug
Sw engineering is one of the few industries where just by having ~8-10 years experience in the field+some demonstrated leadership (eg projects) opens up engineering manager opportunities.

All because of the very high growth: most places can’t keep up just hiring EMs externally.
Internally “promoting” engineers to managers is a great thing: *when* these new managers have the right support during this transition.

Some of the very best line-managers I’ve known have been internal promotions. They often became the manager they wish they had.
I became a manager this way (leading projects/teams and we made it official later). I also tried to empower people on my team to lead, being transparent about what managers do, advocating for engineers in my org to become managers. Many have done so: I’m glad they did.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(