Thread regarding Charles Schwab Corp. layoffs

STS point of view

There were many modernization efforts since last 3 years to support the integration. With it coming to an end, the next year budget will be minimal to keep the lights on. Do not expect to be part of any modernization projects. Overall market condition and Schwab health is not that great to fund fancy work. With this, offshore IT presence will be limited to support work.

by
| 2301 views | | 19 replies (last September 28, 2023) | Reply
Post ID: @OP+1oOZ1Lq8

19 replies (most recent on top)

I am in STS for over a decade now and have worked as development lead. One thing I have noticed is that there is a notion modernization effort is somehow cool and let’s randomly start moving apps to modern stack. We are doing just that in our team with some domain architecture concept backing it.

by
| | Reply
Post ID: @1uie+1oOZ1Lq8

I wasn't trying to be rude. I agree with your comments about other teams. I feel it is due to the revolving door nature of CS and its appetite for "cheap labor" that ends up costing 2x more. My team somehow is still together. but, with multiple initiatives happening the workload can to be crazy. Now I am hearing there is no funding for those projects. I gave up on trying to make it make sense. We'll see.

by
| | Reply
Post ID: @1vlr+1oOZ1Lq8

@1ilc+1oOZ1Lq8 I am speaking for myself. do you work with any other teams? Do you believe they are all as tight as your squad?

by
| | Reply
Post ID: @1mne+1oOZ1Lq8

@1cdx+1oOZ1Lq8 speak for yourself, my crew is tight

by
| | Reply
Post ID: @1ilc+1oOZ1Lq8

@1cdx+1oOZ1Lq8 this is spot on. The firm could save a mind boggling amount of money and move faster by reevaluating the engineering staff. Be it through PIP, re-interviewing for fit or some other method. There is so much dead weight, sandbagging and waste. It will never happen but it would solve so many problems.

by
| | Reply
Post ID: @1cik+1oOZ1Lq8

The Tech Stack is pretty lame. Junior and Senior engineers who have absolutely no clue are checking in code left and right. Offshore support and low IQ Managers and Directors and VPs are the Cherry On Top. Project Managers are absolute garbage. They want someone to manually test stuff at odd time and do not understand CI / CD Systems and Automation. Architects don't know how a LoadBalancer works or Why Splunk doesn't show what they are looking for. I would get rid of 90% of IT folks including the VP and CIO and have folks who understand technology re-write everything from scratch. Mo--ns are building APIs and Maintaining Mainframes here. Just Sad...

by
| | Reply
Post ID: @1cdx+1oOZ1Lq8

Poster meant a standard at Schwab. Both C# and Java are approved, there is no requirement to use one over the other within STS. Maybe within an org but I haven't even heard that.

by
| | Reply
Post ID: @1jli+1oOZ1Lq8

@1xyg+1oOZ1Lq8
Yes, C# is a standard. An international standard in fact: ECMA-334 and ISO/IEC 23270.

by
| | Reply
Post ID: @1tuh+1oOZ1Lq8

C# is a standard? I know many brand new teams and projects starting with Java. Though I never understood why Schwab was a polyglot when it came to these two.

by
| | Reply
Post ID: @1xyg+1oOZ1Lq8

OP here and loving every bit of posts here!

by
| | Reply
Post ID: @1fqq+1oOZ1Lq8

We just updated Clarity a few months ago. LOL

by
| | Reply
Post ID: @1zqx+1oOZ1Lq8

Cool busy work bro

by
| | Reply
Post ID: @1wbx+1oOZ1Lq8

“What was accomplished from any of the modernization efforts... can anyone tell me?“

Well, let’s see…

We switched from NAS to SPOS with no migration path, no usage guidance (until the team started having performance/sizing issues), or consideration of existing infrastructure like the FTP gateway that couldn’t even write files to it…

We switched standards to Oracle… NO WAIT… to SQL Server… NO WAIT… to Postgres all within 2 years…

We directed projects to use Kafka instead of MQ with almost no guidance using an EMost library that was so poorly written that the team supporting it actually had to throw it away and write a new one from the ground up and then they forced the applications to migrate to it within the span of about a year…

We migrated a bunch of applications to a new datacenter while requiring them to adopt a bunch of new standards along the way that the existing apps couldn’t quickly adapt to so instead of simply migrating, they were forced to rewrite their applications during the migration effort, all the while people whining that it was taking too long…

We switched standards from Java to C# because we could…

You see? Lots of great progress! Silly doubters! 🤣

by
| | Reply
Post ID: @1riu+1oOZ1Lq8

What internal systems has STS modernized exactly? Between the bloated governance, inefficient org structure and lack of skills, STS is one of the poorest run departments in the org.

by
| | Reply
Post ID: @1yfd+1oOZ1Lq8

Adding to the list of major accomplishments:

by
| | Reply
Post ID: @1xid+1oOZ1Lq8

Here is the list of major accomplishments:

by
| | Reply
Post ID: @1olp+1oOZ1Lq8

What was accomplished from any of the modernization efforts... can anyone tell me?

by
| | Reply
Post ID: @1xdc+1oOZ1Lq8

Spot on. Expectation is STS will be cut heavily. Need to ramp down staff as integration ramps down. STS employees are also paid higher across the board, and will realize more cost savings.

by
| | Reply
Post ID: @bhd+1oOZ1Lq8

That’s fine, but stop burying me in all of these freaking patches and OS / agent upgrades then that are all marked as “urgent”.

by
| | Reply
Post ID: @enf+1oOZ1Lq8

Post a reply

: