It's compensation and promotion season, and there's one heuristic that I stand by above all others. I have repeated it so many times that recently someone told me that when they used it, the other person said, "Sounds like you've been talking to Rafe."
The heuristic is that we should level and compensate people based on what it would take to replace them, either in terms of responsibility or output. A Senior Manager you'd have to hire a Director to replace should be promoted. Same thing with a mid-level engineer who produces the output of a senior engineer. You should promote them. By the same token, if you have a really strong senior manager who you could replace with a less skilled senior manager based on the scope and complexity of their role, maybe you should defer the promotion and find a way to expand their responsibilities instead.
From the perspective of a person who's advocating for themselves, arguing about what it would take to replace you is more effective than arguing based on what you could command in terms of salary or level on the open market. Anybody who interviews well can parlay their current job into a higher paying job. Better to argue based on what it would take to replace you. In the meantime, when you think about your work day to day, you should also be honest with yourself about what it would take to replace you. If you're a senior engineer and you're always working on tickets a junior engineer could do, you should talk to your manager about finding more impactful work.
From a compensation perspective, this heuristic also works well within the bounds of any company's overall compensation strategy, because it avoids comparisons to other companies that may pay more (or less). It's also a helpful reminder that if you don't pay or level people fairly, you very well might wind up hiring their replacement.
Oh yeah, plus overtly complex cloud infrastructure and my favourite, frameworks.