Thread regarding State Farm Insurance layoffs

To itkv, you are applying logic to a situation which is a mistake. Leadership has been completely interchangeable and therefore assumes you are too. They dont care that it took six months to learn to support your critical system. I work in an area with those too and our most knowledgeable and experienced developer who was a teleworker who was cut loose without so much as a goodbye. Anyone who thinks theu sre sate hastheir head in the samd. This is about expemse mgmt not customer service.

Three = their

What does "not third new assignments" mean in @S0Q6bgk-1mct post?

The last two posts have the ring of truth. So I take back what I said about developer's being safe. What a damned mess.

Managers hear the analysts plan on Monday.

Exec will share the high level plan via Skype to the analysts on Tuesday.

Managers and Directors execute the plan (reductions). Managers that made the cut have been told to lead their prior teams through the change, not third new assignments.

Rumor is voluntary severance is going to be offered. Not sure if it's gonna be all SET analysts, or just overstaffed roles.

Developers are not safe. Reductions in that role as well. 25% in some areas. They expect this to be implemented by July but some areas have asked for a longer time until end of year to knowledge transfer to new employees before they kick the experience out the door. They are looking to hire all new in some roles (areas) and want current employees to stay as productive as possible until they are released. Each area was GIVEN a number they were supposed to hit. No consideration for skills etc. So smart directors had to have managers explain impacts of those planned reductions in order to negotiate numbers. It’s a numbers reduction game and Tipsord is delegating his dirty work to a vendor. We can thank our senior leadership for hopping from vendor to vendor for their next flavor of the day that has gotten us where we are today. Any of you who think your experience and loyalty will save you....you are in for a rude awakening. If we are allowed to ask questions on Tuesday I would encourage everyone to ask about the data (since we are a data driven organization) what data was used to hit their magical numbers. What was the algorithm they used? Who determined the numbers? Who approved those numbers? I’m pulling my policies and taking them elsewhere regardless of my personal impact.

I heard developers are being reduce

HIghly unlikely, especially for OO/Web technologies. I'm pretty sure those roles are all on the grow list. And the last time I checked, there were like 90 Java openings, far more than for any other role. And with the new model, I think you're going to find teams constructed of like 90% developers. That's already started to happen in some areas.

I heard developers are being reduce

Good luck to everyone I’m looking at hub paying for something

All analysts from my team who support critical tools that require a minimum of 6 months learning were invited. So unless they plan on contracting out the entire group, we all will not receive QTD's.

The fact that developers are invited makes me think this is much ado about nothing. Developers have a near-zero risk of being in any impacted group. I'd be shocked if they even gave out hard numbers at this meeting.

Time will tell.

.

I'm pretty sure everyone in Systems got it. Every developer I know got the invite.

Could you say more about how it went down?

I'm a Systems Remote Worker. We were let go en masse, every one of us. They invited us into a meeting where HR basically said, "Seeya later."

It works a little differently for those who are in groups who get a combination of voluntary and voluntary. And for those who are in groups that are being parted out as opposed to eliminated wholesale. Still, when it comes time to the QTD meetings, they won't invite anyone who isn't in the effected group (ie being eliminated). At least, that has been my experience.

So if they are invited a large group, as yourself if it's feasible that ALL of them will be let go. If it's not, then it's not a QTD meeting. It's probably more along the lines of "Here are the numbers of people we're going to let go and the process for how we're doing it and what your options are at this point."

I'll got out on a limb and say whatever it is will be transparent and confusing, lacking any kind of common sense.

“I was let go in the last round. The only people at my meeting with me were other people being let go at the same time.”

What area was this?

Could you say more about how it went down?

I think it’s going to be a generic type meeting with more info to come later. Everyone on my team got the invite and that includes BA’s, SA’s, and web developers. One group is overstaffed, one is maintain, and one is overstaffed so I have to believe this is a generic with more info to come later. Architects are also included in the invite.

Are all analysts invited? If so, I highly doubt they'll be handing out QTDs. However, if it's only certain types of analysts being invited (for example, ISD or architecture or whatever), it's much more likely to be a "Congrats, you're fired" type of meeting.

I was let go in the last round. The only people at my meeting with me were other people being let go at the same time.

Heard 850 will be in the next round.

In systems, mgrs meet Monday with leadership. All analysts are invited for Tuesday. No idea whether a specific plan will be shared or if this will be their BS “tell you later” garbage.

I’m sorry, but don’t know. I had heard it was going to be an executives meeting. Based on recent events, the managers were told to skype, on a Tuesday, decisions had been made and each would receive a call by Friday about job status.

Good luck