I seem to spend all my time in meetings, preparing presentations, performing sysadmin tasks, testing things owned by other teams or external providers, looking things up for people, "resolving" tickets, communicating with other teams, chasing other teams, debugging internal infrastructure, doing code review, and being involved in a peripheral manner with more junior team members.
Apparently this is what being a "senior software engineer" is all about, and it really does suck.
My solution is to work on interesting things on the side and treat the day job for what it is: a ticket to financial independence before I'm 50. And if it all becomes too much, then the job market (for now) is at least very fluid.
This resonates with me. Working in a startup environment is fun and scrapy, but when you're never able to go back and improve what you did because "we barely care about that feature anymore" it becomes pretty frustrating. Building features that only a handful of people use is also soul draining.
Curious why you think that is. I think the difference is that coding under unreasonable deadlines (and then getting blamed when the quality produced under the unreasonable deadline is low) is what sucks.