I worked at a B2B company with a monolith without API's that rendered old-style CSS. Big projects included defining and writing API's to support a self-service web app for admins, as well as a new web app for end users which was responsive on their tablets and phones. Similarly, a B2C company on features for four sets of audience instead of two. I worked closely with PMs on front-end.

Software engineers who are hired to think, and not just type, can provide a lot of value to teammates, product managers, and designers, and also supplement these other roles. But typing lots of lines is the way to look good in a spreadsheet during layoffs. And, many engineers want projects where they get to type for 4-12 months before users use the features.

Note, the above is not a complaint: I recommend software engineers track and ship a consistent number of diffs every week. It forces you to ask yourself if someone's blocking your reviews, or if maybe it's a good time to squeeze in several quick, safe unrelated improvements, etc. Shipping code should not feel like a chore; the company "owes" you the ability to ship code to production since they value your performance based on that.