"... how the world would be worse off if you simply didn't show up"
I've been reflecting on this recently and I think in the context of a job, it operates at both a macro and micro level, and ultimately to feel fulfilled in the long term you need to feel like you matter on both levels.
Macro contributions are the stuff upper management sees— the new products and features, the deals closed, the systems you designed and maintained, the technical directions to advocate for and staff you mentor, the conference presentations you give. These are highly visible contributions are are "easy" to recognize you for, but on the other hand they're also relatively easy to succinctly describe, for example, on a job req, which will be necessary if you do indeed stop showing up.
In contrast to this, the micro contributions are what your close colleagues see. They're who recognize your taste, your care and attention to detail, the thoughtfulness with which you lay out code, balance requirements, utilize tools, and maintain hard-to-measure things like interface boundaries and testability. It's these contributions that quietly keep technical debt under control, save time by preventing problems from ever occurring, and push systems toward ever greater reliability and observability. If you disappear tomorrow, none of this stuff will fall apart overnight; it will degrade in more subtle ways that take much longer to manifest as an actual "problems".
I think for me at least, I sometimes feel a disconnect where I have lots of acknowledgment at the macro level, but still feel burnt out and unappreciated due to gaps at the micro level. The Q12 question about having a "best friend at work" [1] I think is also really tied into all of this, since that's likely to be a person who will see you and what you have to offer much more than a busy manager hustling between meetings all week and rubber-stamping your code reviews.
[1]: https://www.gallup.com/workplace/397058/increasing-importanc...