Ask HN: Laid off by not being 'cross-functional'
I was shocked because my performance is very good and I had no problem of team integration. My team manager is equally surprised by this decision, and he raised an argument for me by showing the floor manager my github & jira stats which proved to be 'outstanding' (343 contributions & 6380 lines of code for last 3.5 months).
Background about my job: I was hired as front-end developer, and my contributions have been focused on company's front-end projects. One month ago the floor manager asked me the idea about 'cross-functional', I answered that the modern web apps are very complex both on front-end and on back-end, and is hard to master both sides at same time. Instead of doing a little bit everything, one should be professional at one side and contribute the best of his knowledge.
I am not saying that I will never take a look at back-end, I sometimes checked our Java codebase to understand related bugs. But I don't understand the definition of 'cross-functional': should one pick up a front-end story today, dive to back-end one tomorrow, and deliver both master quality? Am I wrong about my career goals (which is become a master of Web and focus more on front-end)?