I like the product/infra distinction quite a bit more than frontend/backend. This is basically how Facebook describes its engineers - product engineers who typi

I like the product/infra distinction quite a bit more than frontend/backend. This is basically how Facebook describes its engineers - product engineers who typically work in the "product" repo and works on UI as well as API design and data fetching, vs infrastructure engineers who work in the "service" repo and work on what you typically think of infrastructure (data, systems, efficiency, etc). After being here for a while and speaking with recruiters from other companies, I've really grown to dislike describing myself as "backend" since I have to make myself explicitly clear that I do not want to work on "backend" portion of product and enjoy myself in the infrastructure side of the world.