In combative environments that's solved with a BFF maintained by the frontend team, and the backend gets away with exposing broad and generic API the frontend t

In combative environments that's solved with a BFF maintained by the frontend team, and the backend gets away with exposing broad and generic API the frontend team reprocesses on their layer. In sensible work environments, that's solved by aligning incentives at project level. If your frontend team crucially needs something done, but the backend can't give a shit, the problems run deeper than area of responsibility IMHO. Either what the frontend works on doesn't matter, or the backend team wants to sink the ship, or there's way too many fires to put out and the ship is already sinking. Having mega teams or filling them with jack-of-all-trades types also has critical downsides.