I have been working in the core frontend for the past 2 years for a fintech product. In many places you'll find api calls being made and then it renders the data on screen. No big deal, it doesn't update in realtime nor has much user interaction.
But as soon as you start building a product that involves a lot of realtime data coming through sockets or need to derive a lot of values and sync states between several screen/components. Difficulty increases as you keep on building.
You need efficient updates and responsive ui otherwise you'll lose out on business or get angry customers.
Apart from this you need to ensure your screen loads quickly and show correctly across several screen sizes/orientation, following user preferences also it's accessible. If your page web vitals are not good enough it can impact your web ranking.
This is just a small part of FE. Being able to come up with proper routing/consistent components and abstractions itself is a task.
Backend folks are equally important without a doubt, they have their own issues.
Regarding features as you mentioned, it gets developed and you move on to the next. That's not always the case. Product team might keep on improving or add some other functionality in the same feature which could have a broader impact on overall logic. What if the same components are being rendered upon different screens? It increases complexity.