The idea is that staff+ engineers can drive high-complexity work, right. There are arguably two types of that work: 1. Work where no individual component is co

The idea is that staff+ engineers can drive high-complexity work, right. There are arguably two types of that work: 1. Work where no individual component is complex, but there are a ton of moving parts and interlocking dependencies and interacting systems and so forth. A staff+ engineer is needed to drive this, but that job is less about writing the hard code and more about teasing out and resolving the hard interactions, so that kind of system design 'n' people role. 2. Work where there is a self-contained component that is very complex. A staff+ engineer is great to drive this, and may do so by writing the code themselves and reviewing other people's code as a developer. In practice, many more companies have complex distributed systems than complex contained systems, but certainly both kinds exist.