Seems to be a trend, my boss was telling me that the VP’s in our org think we need more lead devs and less solutions architects, though they would functionally be doing largely the same role, meetings, planning, design, interfacing with teams they are dependent on, annual technology reviews etc. I think it’s going to bite them in the end
Yep, they talked about it a bit during my hiring what I wanted my title to be since they are paid the same and do the same tasks(in addition to some coding expectations). I’m glad I chose architect, but ultimately they squeezed me out of that with RTO mandates for architects and above.
Seems to be a trend, my boss was telling me that the VP’s in our org think we need more lead devs and less solutions architects, though they would functionally be doing largely the same role, meetings, planning, design, interfacing with teams they are dependent on, annual technology reviews etc. I think it’s going to bite them in the end
I imagine hiring will be an issue. Devs want to dev, and naming an architect role a “dev” role doesn’t communicate the role properly.
Yep, they talked about it a bit during my hiring what I wanted my title to be since they are paid the same and do the same tasks(in addition to some coding expectations). I’m glad I chose architect, but ultimately they squeezed me out of that with RTO mandates for architects and above.