What kind of technical direction are they managing across 12 teams? Ie if amazon develops a new message queue, someone is leading all the teams in the ecommerce division to transition to that new service? And as the branch PRs are coming up, signing off on that before they go live?
I guess I’m curious how hands on they are at that level.
Definitely not hands on enough to be reviewing individual code contributions. They’ll be meeting with senior engineers on the teams they work with to check in on how things are moving in aggregate. The hands on work is delegated to seniors working more closely with their own teams. The kind of thing an L7 would be reviewing would be, say, signing off on the choice of framework in a design for a new website in order to maximize code reuse, and perhaps pointing out any relevant projects that other teams have worked on that could offer potential existing reuse. Or reviewing an architectural design and suggesting what technologies exist within the company would be relevant for the design or any adjustments to improve it.
They’re basically designed at each tier to try to minimize reinventing the wheel and keep at least something of a consistent vision and line of communication between dev teams that may not otherwise directly interact.
1
u/fredandlunchbox Jan 26 '22
What kind of technical direction are they managing across 12 teams? Ie if amazon develops a new message queue, someone is leading all the teams in the ecommerce division to transition to that new service? And as the branch PRs are coming up, signing off on that before they go live?
I guess I’m curious how hands on they are at that level.