IMO being able to think about the wider implications for smaller subsets of a system is an important ability. That being said, if your organization allows ICs to make technical decisions without any sort of review from someone whose job it is to architect large systems, idk that seems like something you should have.
It also depends greatly on what 'layer' of the stack you work in.
There's a difference between talking about the wider implications of a system and acting like software can be planned top down with any sense of accuracy
If you want to ask me about the wider implications for smaller subsystems then ask me about the Linux kernel. How did it become that system design is the only way to demonstrate this particular skill?
It also depends greatly on what 'layer' of the stack you work in.