Thread regarding Cisco Systems Inc. layoffs

The best way?

Many years ago when I heard some of my friends had landed jobs at Cisco I thought "wow Cisco is smart to hire them". I even considered buying the stock.

All of them got laid off.

So when Cisco bought the company I worked for I already knew what was coming. The day the deal was announced I should have updated my resume and left. But I stayed anyway. I lasted longer than I expected but those years were mostly wasted.

I watched good friends and talented people get cut. After about a year I made a decision. I was done working extra hours or giving my soul to the company. If someone asked where I worked I would say Cisco but I always added that it was not the company it used to be back in the 90s. These days I even wonder if it was ever really that great.

In the end I gave them way less than my best effort. Sometimes I felt guilty about it. Then I would see someone busting their a** working weekends and late nights only to get laid off anyway. That made the message pretty clear.

Now it is my turn to be let go and I am still not sure which path was better. Should you work hard on principle even when the system does not care? Or do you push back against a machine that punishes loyalty?

I used every bit of that unlimited PTO. I never worked extra hours. Part of me is glad I fought the system in my own small way.

The other part wonders if it would have been better to go down still believing in the mission like Old Major in Animal Farm.


by
| 3 views | | 3 replies (last 9 days ago) | Reply
Post ID: @OP+1kxfkea4h

3 replies (most recent on top)

Far too many people I've known (not just at Cisco) who hated their job slacked, losing existing skills, stopped building new ones and the drive they thought would come back at a better company was irreversibly damaged. Keep pushing and move on if you aren't growing because they people you'll be competing with for the next job already did.

For people going on about "the good old days," run static analysis on any code base from that time. It's all complete garbage and Cisco ultimately ended up spending the vast majority of its development budget on bug fixing. Cisco is the only company where I can point to even a single project which overran a budget by a factor of dozens, and I could point to many projects at Cisco that did exactly that. The saddest part is how many people thought they were doing a good job because they hadn't worked at a competent company to use as a baseline.

by
| | Reply
Post ID: @ec+1kxfkea4h

@cz Those were the good old days. Things were never the same, after that first major layoff.

by
| | Reply
Post ID: @dq+1kxfkea4h

I started at Cisco in July 1995 and can verify it was a very different company then. There were fewer than 5,000 employees, Chambers was CEO, morale was very high, we couldn't hire fast enough, the stock split every six months on average, and every single employee got stock options, including the mail room clerk. The company continued to grow exponentially until its first layoff in April 2001, and Chambers took a $1/year salary at that time.

by
| | Reply
Post ID: @cz+1kxfkea4h

Post a reply

: