LOL... the irony being that for a lot of folks whether they are A-Team or B-Team or C-Team depends a lot on the company culture, impact of work they are assigned on, problem statement, team (esp. foundational team), exec alignment and a tonne of other factors that may or may not be in their control.
A supposed "A-Team" Engineer at FB who was part of the early team that built out a messaging platform that is used across FB Engineering will still be seen as a "B-Teamer" at a 20 person startup if she's unable to create similar impact (again, not because she's intrinsically a different person between FB and the new company).
Heck, the easiest way to be considered a 10xEngineer/A-Teamer today is to bring 15% increments to 10 teammembers' productivity rather than be some insanely productive, busfactor=1 developer.
We really need to stop with this silly ranking of devs
A supposed "A-Team" Engineer at FB who was part of the early team that built out a messaging platform that is used across FB Engineering will still be seen as a "B-Teamer" at a 20 person startup if she's unable to create similar impact (again, not because she's intrinsically a different person between FB and the new company).
Heck, the easiest way to be considered a 10xEngineer/A-Teamer today is to bring 15% increments to 10 teammembers' productivity rather than be some insanely productive, busfactor=1 developer.
We really need to stop with this silly ranking of devs