Frankly, someone who hasn't:
- written a self-bootstrapping compiler
- designed and microcoded a branch-predicting, pipelined processor
- written a toy OS that works
- spent an inordinate time with assembly
- ran fuzzing against a library
can't legitimately call themselves an engineer. People who don't grasp the implications of their implementation decisions are vast the majority... and how many of them can fix things when something malfunctions at a layer that they they're unwilling/incapable of debugging? Either they can depend on some other specialists, find a local generalist engineer to fix it for them or they can "be the change they seek."