r/Raytheon • • 1d ago

Pratt & Whitney Role realignment

It was recently announced that several teams in my department will be part of a realignment to “more accurately reflect the work they do.” Changing from Software Engineer to Project Engineer or System Engineer depending on the role.

Seems silly to spend the time and money to make this change. Supposedly there’s no impact on compensation. And that might be true in the short term but affects market analysis and the target band.

13 Upvotes

22 comments sorted by

18

u/Then-Chocolate-5191 Raytheon 1d ago

It’s balancing Engineering Centers, happens periodically.

0

u/Turbo_MechE 1d ago

What do you mean by balancing engineering centers? And why do they bother?

10

u/Then-Chocolate-5191 Raytheon 1d ago

Mostly a number of people per center. Years ago one of the reliability engineers I worked with got remapped to a packaging engineering group, in protest he stacked empty boxes on his desk.

0

u/Turbo_MechE 1d ago

But our centers stayed the same. It’s just the title in Workday

5

u/D_BrickashawFerguson Raytheon 1d ago

It’s the “engineering playbook.” My chief engineer group has been renamed from systems to project. We still report up the same management chain. Other hardware groups are seeing actual realignment, separating ECAD designers from hardware into the components engineering group as one example. Change is the only constant here.

4

u/Then-Chocolate-5191 Raytheon 1d ago

I don’t know then, but usually when they change titles like that they realign employees to another engineering center.

8

u/Interesting_News_830 1d ago

Its called rearranging the deck chairs. Thats what saved the Titanic.

4

u/feedyourheeeaaaddd 1d ago

There's no impact on compensation the moment it happens, but there could be implications come ACP and promo adjustment time due to changes in market penetration based on the aalary ranges of the new role

1

u/Turbo_MechE 1d ago

Yep, which is why everyone was very hesitant in the meeting. Someone called it an incomplete answer since folks are expecting an impact on ACP and bonus

4

u/ByteMyShinyMetalAss1 1d ago

I've been through it. My section was split in half, some went one way the rest went another. After the realignment some people in Section Head and Manager roles were looking for work elsewhere.

2

u/-AverageJoe- 1d ago

It is most likely an attempt to align titles with the work you do based on the job catalog. It won't effect your current compensation. Generally, there are small differences among the specific engineering disciplines but it shouldn't have a big impact on future compensation either.

2

u/Ewokhunters 17h ago

Get ready for even worse salary compression...

2

u/olderbutslower 13h ago edited 6h ago

Happened to me a little over a year ago (Collins). My title went from principal swe to manager, I have no direct reports and am in an “analyst” role. I attend a lot of meetings, offer information when I can, have trained on a bunch of new stuff I don’t use and my current project changes every couple of months. I’m honestly surprised I’m still employed by the company. If the forced move was a setup for being laid off, they forgot so far.

2

u/good-citizen2056 1d ago

Smells like layoff is coming

3

u/Turbo_MechE 1d ago

My guess is they’re about to market adjust the software engineers and wanted to remove eligibility

1

u/BarracudaEfficient16 1d ago

All three of those have different pay scales. For example a P4 scale you see is the min/max for all P4s, but for each role there is a specific sub scale that you’re likely never to see.

1

u/Turbo_MechE 1d ago

Yeah, that’s my concern

1

u/BarracudaEfficient16 1d ago

Doubt they’ll change anyone’s pay as part of the effort but it’d start to affect it in the future for raises.

2

u/Turbo_MechE 1d ago

Yep. Which is still an effect on compensation. Just a secondary effect which is why it felt shady saying there was no impact

1

u/BarracudaEfficient16 1d ago

Because the is no immediate impact. They are either careful choosing their words or are ignorant of second order third order effects that pop up down the line.

1

u/Dumb_Logic_01 1d ago

Working for a company now where role realignment is desperately needed. I’d just ask that you consider whether they are in part doing the right thing. I’m looking at some of the jr engineers I’m currently working with and career wise it’s going to be a major hurdle for them if/when they decide to go to a different company. Our scope of work doesn’t match the title nor the req that was advertised. It also puts the program at a severe disadvantage because you have people making decisions about things they don’t have the right experience for. I know RTX isn’t this bad but just a thought you may want to kick around.

1

u/Informal_Article3699 9h ago

It’s the engineering playbook. It’s so that everyone across RTX engineering who does a similar type of role has the same job role identified. Doesn’t change what you do - it’s to ensure consistency in job role identification across the company. Intent is to make it easier to identify who does what (and ultimately for you to move roles across RTX more easily). It’s not a bad thing.