Thread regarding U.S. Bank layoffs

@qs HR Talent Consultant Muslee Judge endorsed too. She is big follower of Head of Cloud (A.C) to execute unethical practices.

@mc What !! AC is from wealth management. There’s already lawsuits against wealth management CIO. https://www.hcamag.com/us/specialization/employment-law/employee-sues-us-bank-for-firing-her-months-after-hr-complaint/567107

Formally raise a complaint regarding actions taken by AC and PC that are unethical and inconsistent with the organization’s standards of integrity and accountability.

@mc PC has endorsed all decisions taken by AC.

GK needs to take a hard look at AC and his entire leadership layer. The reality is—EC, PC, and DV haven’t had the appetite to make these calls. PC was closely aligned with AC and approved these decisions. Now with EC stepping in and DV stretched thin, the problem remains untouched.

This is a textbook case of high compensation without corresponding delivery.

This isn’t a talent gap. It’s a structural failure.

The org is saturated with program managers and technical product managers operating in Principal Engineer and Director roles, while true engineering depth is minimal. Titles are inflated. Compensation is top-tier. Delivery? Questionable.

Look at AK’s org—a direct under AC. It’s filled with GL17+ roles, yet where is the engineering output? Where is the cloud delivery? An Amazon badge doesn’t substitute for execution.

Under AC, even Principal Engineers lack measurable outcomes tied to cloud transformation. In one case, a Principal Engineer was awarded “Legends”—approved at the highest levels—despite no clear delivery to back it up. That’s not recognition; that’s misalignment.

Then there are roles built on visibility and privilege rather than impact. Promotions—like JO moving from product manager to Director without an engineering foundation—only reinforce the pattern.

Meanwhile, EC, as CIO, is expected to deliver outcomes without full visibility into this reality. That’s the real risk. This structure won’t just underdeliver—it will drag the entire portfolio down.

At some point, the question becomes unavoidable:

Who is actually building, delivering, and moving the cloud forward?

Until that question is answered with evidence—not titles—this is nothing more than expensive theater.

PC recognized that AC was a bad hire and that the Cloud program is a complete failure that no one will take accountability for. That’s why it was moved. Also AC wasn’t retired, he worked on the CIO for Wealth and applied to the role. PC wasn’t retired either. He was head hunted for the job.

@kf A clear pattern: former Wells Fargo associates like A.S. and A.V. holding senior principal engineer title with GL18 now report directly to the Head of Cloud AC, earning ~$350K. Meanwhile, A.S. is celebrated as a “Legend” without tangible Amazon Web Services delivery—while the blame is conveniently handed off to Deloitte.

A select few in this organization enjoy constant travel perks, with costs largely covered through credit card point reimbursements . Take R.H , A.C’s direct reportee, for instance—frequent travel appears to be a privilege, with expenses effectively covered through credit card points.

I have heard both PC and AC were hired out of their retirement and worked together earlier as well. So makes sense on the comp as well as no accountability.

Isn’t he nearing retirement? That could explain some of this. Also, given he’s closely aligned with the Infrastructure CIO, it’s not surprising the support dynamics are playing out this way.

Could you use a senior client facing member on your team?