A lot of the work in bigger companies is "backend." You work on APIs that are probably invoked somewhere in the service of a web request, but may not be directl

A lot of the work in bigger companies is "backend." You work on APIs that are probably invoked somewhere in the service of a web request, but may not be directly web facing. And if they are web facing, you have a mobile or frontend developer colleague who implements the client. You don't have to do frontend if you don't want to. Obviously if you want to work in startups and build a product from scratch it'll be pretty important. If you want to work in big companies, the backend path has less skills churn (we don't throw out our framework every 6 months) and higher growth potential (it is easier to have a big impact on the org vs. churning out features, which is a low to mid level position).