I think as you grow in your career you'll tend to specialize rather than generalize. You get really good at a few things, rather than somewhat good at lots of things. The "Senior FE" roles are fewer but more specific. Now and then I see listings for "Performance Engineer", "Accessibility Engineer", and "Infrastructure Engineer", but on further inspection these are actually Senior Front End roles, but not in title.
Recently I went through a generic Sr FE interview at Google (still waiting to find out if I've been ghosted after). There were 5 or 6 rounds, and I feel I totally bombed one of them, excelled at one, and did okay at the others. I think that's acceptable at this level. I went through a "Performance Engineer" interview loop at another company, and the rounds were all specific to the role. I had a much better experience in that interview.
I've often gotten the impression that Google interviews more for general applicability to working at Google than for the specific role advertised. Your comment here being no exception -- is that your experience, is that what you mean to convey?
We're in agreement. It reflects my experience. I had to question the recruiter about it, "How does Google hire FE specialists in Accessibility for example?" and I didn't get a good answer. I assume they throw some fungible engineer at the problem and hope for the best?
Comments
I think as you grow in your career you'll tend to specialize rather than generalize. You get really good at a few things, rather than somewhat good at lots of things. The "Senior FE" roles are fewer but more specific. Now and then I see listings for "Performance Engineer", "Accessibility Engineer", and "Infrastructure Engineer", but on further inspection these are actually Senior Front End roles, but not in title.
Recently I went through a generic Sr FE interview at Google (still waiting to find out if I've been ghosted after). There were 5 or 6 rounds, and I feel I totally bombed one of them, excelled at one, and did okay at the others. I think that's acceptable at this level. I went through a "Performance Engineer" interview loop at another company, and the rounds were all specific to the role. I had a much better experience in that interview.
I've often gotten the impression that Google interviews more for general applicability to working at Google than for the specific role advertised. Your comment here being no exception -- is that your experience, is that what you mean to convey?
We're in agreement. It reflects my experience. I had to question the recruiter about it, "How does Google hire FE specialists in Accessibility for example?" and I didn't get a good answer. I assume they throw some fungible engineer at the problem and hope for the best?