Thread regarding Allstate Corp. layoffs

Allstates job titling

Why is it that in this company when people are called architects they're nothing more than admin assistants or when they're called engineers they're nothing more than non-technical analysts and why is it that these architects are performing administrative actions for these engineers while being denied access to provide valid implementation instructions?

Why are such efficiencies continuing to be the status quo and not replace by automation to remove these unnecessary administrative task items let alone the non-technical analysts who provide no value other than following steps on how to push buttons?

How is anyone supposed to be employed on this model for long periods of time let alone be considered a valid representative in their tradecraft?

This looks like a house of cards that's waiting to fall down due to a gust of wind or somebody walking by.


by
| 2 views | | 4 replies (last 15 days ago) | Reply
Post ID: @OP+1ksqmewgn

4 replies (most recent on top)

DPMs are just product managers. Many DPMs have no clue how their technology works. In my observation, the majority of architects at this company were people who just drew lines in Visio or were simply buzzword people. Only a handful of architects were truly technical and made good recommendations/desigs and gave good recommendations. What you have are VPs making technology decisions to look cool, pad their resumes, or get bonuses without consulting knowledgeable principal engineers or architects. I wouldn't trust many people at this company above ME to tell me anything useful about tech, let alone the clown at the top of this circus, esp when they say co-pilot is their best engineer.

by
| | Reply
Post ID: @154+1ksqmewgn

The Architect role is fading at Allstate. Digital Product Managers now own the full lifecycle as 'gods' of their domain. But who preserves application history, lessons learned, and objective technology evaluation? When architecture becomes merely a debating society, the enterprise loses strategic vision and cross-portfolio coherence. Product velocity is important - but not at the expense of architectural integrity."

by
| | Reply
Post ID: @14j+1ksqmewgn

Same record, different thread!

by
| | Reply
Post ID: @b9+1ksqmewgn

@OP was not perfect or great in the past always. There was always some struggle, odd titling, and inefficienes. However, things would normalize a bit between leadership changes. However, things are far worse now. When this iteration crashes, it will be far harder to fix/cleanup due to the amount of money sunk into the wrong leadership structure and technologies.

by
| | Reply
Post ID: @ay+1ksqmewgn

Post a reply

: