Rigid roles are a reflection of a human desire to put people in tidy boxes, that doesn't mean those boxes map to reality in a useful way.
It's a sharp contrast, and a weird contrast, and in the latter case, you're constantly challenged, constantly finding yourself outside your comfort zone, learning your limitations, what you like, what you dislike. I'm really really glad I didn't end up landing at a large company like I used to work (Symantec). Some people like that structure. I can't stand it.
If your use case is very ordinary it does work that way. It's only at the bleeding edge or in a weird edge case that performance or optimization stops being a problem you can solve by paying for a bigger box. The performance rarely matters for a SaaS CRUD app until you hit a scale where you've got a team of experienced devs, so most people vibing their next 'unicorn app' don't care.
I did not like that very much, and did not stay too long.
I recall sitting in an all-hands once where the engineers were bleeding out their eyes about the abomination that was the new start screen, while the head PM just kept repeating, "This is the right decision. WE HAVE THE DATA."
Separately from that, pushing back is often uncomfortable and unrewarding. Even in places that do expect developers to have autonomy, it seems like there's usually some people that choose to just follow directions because it's easier and there's no consequences for doing so.
At good firms that try to pay competitively, of course this doesn't happen much at all. But yes, it's unsettling to get to work, and have someone tell you that what they want is 3-4 well defined tickets that they'll write in the next two weeks, and don't want to engage even a little bit more.
So whenever i hear that coders are out of job because of AI, I always wonder where were those “coders”. Never met one