Sounds like higher ups intend to layoff at a scale similar to when the company did layoffs in 2016. Belt tightening has been holding off the inevitable but now does not seem enough. Everyone should be asking their managers for more information so that pressure can be put to have more communication from higher ups
13 replies (most recent on top)
It's not just people under Rajat. Client Services has laid off a lot of people as well as other orgs in Visa. Everyone is a target.
@2khp+1t1CU5oE I was part of a group that tried to turn everyone into standard developers and it was a mess. Most of the veteran devs refused to do any testing beyond unit tests and dumped extra testing on the ex-automation testers turned devs. Most of the veteran devs that tried automation were worse at it than our original automation testers and often forgot about documentation. The dev managers just wanted code out the door fast, then scratched their heads when bug reports spiked or audits went badly. After a year we scrapped the whole idea and went back to separate roles.
Your idea might work elsewhere, but Visa would need to seriously boost pay, leadership, and hiring practices plus provide ample training. None of that seems likely to happen anytime soon.
Good to see layoffs. Visa didn’t do any during the pandemic when they should’ve to raised the bottom line. Bullish on Visa stocks now once this hits the markets ☺️
@2pac+1t1CU5oE where I am SE outnumber QA, however it is not clear to many why we need dedicated “test engineers” when SE are more skilled at writing automated tests (code) than QA AND can also write production code and handle production support.
I’m against engineers testing their own code, but no reason why another SE can’t be pulled in perform that role, and indeed that is normally what happens.
I’d be all for a standard engineering role that handles code and test.
In some departments QA is outnumbered dev engineers. Functional, Automation, Manual...
Any one knows Singapore situation?
It’s clear the commenter below me is not a programmer.
Code can no more be automated via AI today than a car can be driven by it.
All sounds good on paper until you factor in fuzzy requirements and human experience.
I do agree that the roles affected with redundancy were those that could be automated - what do RM do all day except schedule releases and think up ever more process tape to justify their existence? I know of good engineers who have left the company specifically because of the red tape RM keep inventing and it’s good to see management have caught on.
PRE is another team ripe for reform - all those guys seem to do on a release is manually click buttons and are woefully under skilled at problem solving outside of that, rarely knowing what the buttons actually do.
Give the dev teams the power to run their own deployments and they will do a better and more efficient job.
These cost cutting measures were already in the works it was just a matter of time. AI technology in some ways is here to automate redundant work prone to human mistakes. Software engineers were the first career choice to earn TOP salary. No more, coding can now be automated, everything is replaceable cost cutting measures. Cashiers are now replaced by machines. You can order online, pay, get a number and pick up your order no need to wait in line or have human interaction as an example.
They also may NOT last for months, scaremongering is not helpful
I wonder if engineering will be affected
The ratio of interns to college grads is not where it should be.
Today, the senior engineers are spending their time hand holding juniors instead of contributing themselves.
From what I heard the drive is to focus on hiring more engineers, so I don’t think that group will be affected.
Even for Manish no timeline was given. Language implies changes are still going. Orgs outside of VAS and CMS have not heard anything other
Were different orgs under Rajat given different timelines for layoffs? Manish's org seems to be done.