> if anything I'd argue that NOT tying yourself to a single framework is what makes you grow into a senior developer I disagree. A lot of this discussion is a

> if anything I'd argue that NOT tying yourself to a single framework is what makes you grow into a senior developer I disagree. A lot of this discussion is about semantics - what do we mean when we say senior developer? for FAANG they don't really care what languages you know - in fact they don't really seem to care how well you can code, it's all about your ability to solve algorithms under pressure. Is that a senior dev? Guess for them it is. But for smaller startups - where your ability to code well and onboard fast is critical to the team, when they hire a senior they will most often prefer someone familiar with their stack. So to them, a senior (preferably) has deep knowledge in their stack already (or is good enough to get up to speed really quickly).