I see other way around. We DB and Infra guys are not at all 😂

@dry-monkey-93718 that is a good question. I have often wondered about it. I think it comes down to what kind of product you are working on. And whether your company does a B2C or B2B product. My guess would be B2C products would like their FE devs more and B2B product companies would like their BE devs more 😊 But ofcourse, I am generalizing and using a very broad brush.

Question would be by whom ? by backend devs? YES By employers ? mostly not (I agree with @loud-glass-33663 on this) Salaries are also at par these days

A good engineering team respects all engineers, a good client respects all developers who provide value, a good developer respects all peers. If someone is judging you based on the techstack you use, they are not ethical, they are gate keeping and being toxic to the tech community. Call them out and stop engaging with them 🙂

Recipe for disaster and sack @nice-country-1598 😂😂

By peers. When I was the employer, every person was insanely important to me. But I've recently been thinking back to how the team dynamic worked. Even when we had tons more work in the frontend, I've had engineers completely capable of writing frontend code, hired as fullstack engineers try and peddle back from writing code near the UI. I've never witnessed it the other way around. Willingness to learn a new tech to cover gaps while we were hiring was also way less towards frontend, more towards backend. This has made me question hidden bias that might have existed and I couldn't see/fix. We were a B2B company so @loud-glass-33663's observation might apply. I'll try to remember the B2C days and see if it holds up.

Hmm.. That is interesting. I think it comes down to team dynamics and the way responsibility is shared. When I have worked in teams which had full-stack devs doing full stack work (i.e. you take a feature and execute it from DB -> Front End), anybody could do anything and they felt comfortable with the code. Now, I am working in a team which has responsibilities split across FE and BE and devs will not really want to cross the boundary unless they REALLY need to. It probably has a lot to do with not wanting to mess up someone else’s code or not being confident in the stack because you are not working in it regularly.

All of this is true 😅 There were definitely backend devs who were scared to mess things up. From another slack, someone mentioned that people have a bias towards a CS degree, who tend to be gravitate more towards the backend.

I feel this can happen if the Client/Manager is less technical and not aware of the complexities involved in the BE, they appreciate what they see, what is visually appealing, Some of my friends shared their experience that being BE engineers, they don’t get appreciated as the FE guys are. But Even if the client does not understand the BE complexity there must be some one who does, can be Architects /BAs /Tech Leads, who appreciate everyones work, without having any bias due to Tech-stack. Note: here i am talking about appreciation not respect, If there is a bias in respecting any professional then the problem is with that person.

Good point! I've heard of companies where the backend is paid much less attention to while the UI looks amazing! I think I now realise that the question was loaded and not framed well. Thank you all for spending your time helping me think better! 👍