I've noticed in more and more projects a trend for the front-end team to build a legit backend server as a facade interface for multiple other backends. So I gu

I've noticed in more and more projects a trend for the front-end team to build a legit backend server as a facade interface for multiple other backends. So I guess this is the front-end-of-the-back-end-of-the-front-end? The rationale is that it is often easier for the JavaScript to talk to one backend facade layer, and have that backend facade handle talking to the "real" backend servers. So think sequencing and/or parallelism of API calls, serialisation, transformation etc all happening on the backend server before sending only the final result as simplified JSON to the browser. So now your front-end dev also needs to know java/go/c++ as well as html/CSS/JavaScript/typescript :)... We just call them frontend engineers and be done with it. The best engineers tend to have broadly applicable skills and can rapidly learn something all with a smile and good attitude. A sneering/condescending/moaning/complaining/whinging aversion or outright refusal for writing CSS/c++ (it cuts both ways) is usually a red flag IME.