Re:Developer Tropes: “Google Does It”
by alexhutcheson on Monday July 15, 2019 @05:15PM
(#20445352)
The typical route would be to 20% with the team for a couple quarters to learn the ropes and demonstrate your skills, and then transfer 100% once the destination team has the headcount to absorb you. I know multiple people who have done this, although not specifically to the WebGL team.
For domain specific roles I ought to think that the members of the current team would be more than happy to provide insight/advice/coaching to someone looking to skill up and get involved. This is typically how I've seen lateral moves done at other companies that encourage mobility. For example, moving from a primarily DBA job to devops/operations/wahetever.
To what extends does this work? Let's say I want to work on Chrome's WebGL implementation, but I've no prior professional experience with neither C++ nor 3D graphics - would they still take me as a noob that will take a couple years to ramp up? I suspect not. So, you're probably most likely just stuck with your current niche and can only move within it - which, to be fair, is still much better than in most other companies where you're just stuck with your current project.