Thread regarding Wells Fargo & Co. layoffs

11 replies (most recent on top)

@a2 It’s BNY … and she’s been fired from every job she’s had. Smart move bringing her to WF - not. She’s laughing all the way to the bank (no pun intended) with making $22MM in 2024 for four months of work. Tech is toxic - no wonder Tech employees are pushing for a union. BE is a nightmare and truly disliked for good reason. She needs to go!!

by
| | Reply
Post ID: @13c+1k9zymbp1

@op Spot-on. WF buys the shiny tools (Jenkins, Ansible, Puppet, Apigee, Salesforce, Sensa, Pega, Fargo® on Gemini, Watson Lab, Vantage® microservices) but manages none of them. Coverage? yes Quantity? yes Quality? NO It’s not the tech—it’s the culture of fear. No psych safety = no ownership. One IC designs, 5 nod → contractor quits. 1 hr change, 8 hrs overhead → SNOW inquisition.
“No bandwidth” dodge → vendor gets blame, manager gets promo.
Wagile he-l: Waterfall orders + Jira ceremony + offshore chaos + QA in prod.

Result? Band-aid rollouts, $50M data-center flops, ISO 20022 wires in limbo, AI hype with zero integration. Bridget’s “engineering-first” sounds great on CNBC; on the ground it’s still C&C surveys asking if you trust your manager while he schedules your exit. Fix? Ki-l the fear first. Real teams, stable backlogs, leadership that eats its own dogfood (try a sprint retrospective, Charlie). Until then, every Gartner Magic Quadrant purchase is just shelf-ware with a depreciation schedule. P.S. Columbus “next-gen core” hub with ex-JPM talent is the only green shoot. If they ring-fence it from the Wagile virus, maybe we’ll see actual modernization. Otherwise? Yesterday’s tech, tomorrow—guaranteed garbage.

by
| | Reply
Post ID: @fa+1k9zymbp1

@dp unfortunately, it's been like that for 15-20 years. They used to prefer to throw bodies at something instead of investing in tech. And they never got rid of anyone when they weren't needed, until now.

by
| | Reply
Post ID: @e4+1k9zymbp1

@cs With the addition of the new Data Centers came many existing Data Centers that are no longer 24x7x7. We never had to be so careful when planning Week-end work. But hey, problems never pop up on the weekends or early morning ;)

by
| | Reply
Post ID: @dz+1k9zymbp1

Everything is getting rolled out with band-aids and they think this half a-s approach will be fixed by AI? Mo--nic.

by
| | Reply
Post ID: @dp+1k9zymbp1

Haha she is a Rockstar, she cost the company over 50 million with her mo--nic idea of new data centers.
Then Blamed people under her and forced them to resign.
This is typical of WF leadership.

by
| | Reply
Post ID: @cs+1k9zymbp1

So here's the thing. Back when I started in WF Network services, it was the tools that were unworkable. We'd do a change, which maybe took 2 hours, and then spend next 3 hours trying to get our devices under management. But, while we complained, that was the extent of the overhead.
Now, most of the work IS overhead. Spend 1 hour on a CHG, and then spend 5-10 hours on overhead, prepping for the change, documenting the change, explaining the change, and updating any requested info in SNOW for the change. Its unbelievable.
Oh and don't forget - if there is a problem with the change, oh man - let the inquisition begin!!!
It is almost impossible now to do any work, and most of my peer engineers go to meetings and talk. TALK - not work. Unless of course you think talking IS working. Perhaps at WF it now is.
What a far cry from when I started.

by
| | Reply
Post ID: @c9+1k9zymbp1

I’ll co sign 💯

by
| | Reply
Post ID: @aw+1k9zymbp1

WF Tech: "Delivering yesterday's technology, tomorrow."

by
| | Reply
Post ID: @at+1k9zymbp1

Couldn’t agree more. 50+ hour weeks are the new standard here with all the after hours work that is required since it’s a hard 8 hours in office now

by
| | Reply
Post ID: @af+1k9zymbp1

Why? Why can't you make it better? Didn't you hire a superstar from NYB? Bridget Engle?

by
| | Reply
Post ID: @a2+1k9zymbp1

Post a reply

: