Thread regarding Cisco Systems Inc. layoffs

Teams hit a second time after initial November LR round!

Interesting! Couple of teams reported that they have been hit a second time since the initial November 2022 round! Is this a sneaky clean up round to help meet Q4 numbers?

by
| 3671 views | | 11 replies (last July 26, 2023) | Reply
Post ID: @OP+1nL7SGXZ

11 replies (most recent on top)

Break off a piece. Paint to match.

by
| | Reply
Post ID: @2php+1nL7SGXZ

And we can expect another round this coming November. It just never ends. But hey join the next Beat to see the ELT's pathetic attempt at celebrating while jobs are getting chopped! Oh and expect Fran to join from Honolulu this time.

by
| | Reply
Post ID: @2yny+1nL7SGXZ

I was LRd last year after 12 yrs at Cisco. Found a new job in 2 wks as an SE. After working with other vendors for small mid size businesses, and deployed MS Teams, Fortinet FWs HP Aruba, Unifi APs, etc.., big difference in ease of use. Much cheaper and reliable. Just no added value or any reason whatsoever to use Cisco gears anymore.

by
| | Reply
Post ID: @1yeh+1nL7SGXZ

Not gullible just working with the facts. Confirmed that COLLAB had taken ‘additional steps’ last week towards further rebalancing teams. Especially tough since teams already hit in FYQ1.

by
| | Reply
Post ID: @1bsk+1nL7SGXZ

My team got hit 3 times.

by
| | Reply
Post ID: @1ylu+1nL7SGXZ

Why would that surprise you ? I mean, are you so gullible to beleive that this was a continuation from the november one ?
In general in cisco we execute stuff poorly, however one thing we are good at is layoff and executing them, so why would we want to wait 7 months.. and then say.. this is round 2.
About the worst marketing I have seen in a long time. But as we are an AI company apparently, we have nothing to worry about..

by
| | Reply
Post ID: @1nlf+1nL7SGXZ

Can confirm my team impacted 2 times since nov 2022

by
| | Reply
Post ID: @1ajm+1nL7SGXZ

Can confirm that my team got hit twice.
And they targeted higher grade this time.

by
| | Reply
Post ID: @1voo+1nL7SGXZ

Fran said last week that it was the final part of the 5% cut announced back in Nov '22 because some BU's couldn't get their sh-t together to come up with their lists early in the year.

Since the "savings" were accounted for back in Nov, they don't count towards Q4.

But, the BS about it being a last resort, that it's not about cost cutting or making Q4 numbers look good is too much to swallow. This is one of the standard copy-n-paste answers they put in the Q&A at the most recent check-in.

As we announced then, this is not about cost savings, given we have roughly the same number of employees as we did before the process began. This rebalancing is about prioritizing investments in our transformation, to meet and exceed our customer' expectations in the chaining technology landscape.

I like that someone had the ba--s to call the ELT out in a Q stating:

Looking at the answer...saying in March (or thereabouts) "no more layoffs planned", then laying off a significant number of people, and saying "oh, it's a continuation of the layoff we announced 9 months ago...is disingenuous and not reflective of Cisco's culture of transparency and honesty, IMO.

They're 100% correct. The ELT should have been reminding us that the Nov '22 LR was not finished, and which BU's needed more time rather than letting people think it was over and start worrying about the Aug '23 announcement as to whether or not there'd be a large LR and suddenly hitting a large number of people in July with no notice since they let everyone think the Nov' 22 LR was done.

by
| | Reply
Post ID: @1kxq+1nL7SGXZ

Which teams? Lots of teams in Cisco. At least provide the BU.

by
| | Reply
Post ID: @mff+1nL7SGXZ

Yes, just to meet the numbers. The CFO would like you to know that it was done as a "last resort".

by
| | Reply
Post ID: @mdx+1nL7SGXZ

Post a reply

: