Same for senior level and mid level. There needs to be less "demonstration of work" that fits the career ladder document but more autonomous work that provides

Same for senior level and mid level. There needs to be less "demonstration of work" that fits the career ladder document but more autonomous work that provides value. That's it. As an example, if a senior engineer spent last 3 months trying to fix dev environment issues at the expense of RFCs, commits, bug fixes (but at the direction of management) - This is fine and should be recognized. Recognizing only activities enumerated in some BS levels document is a fools errand that fails to recognize that different stages of different teams and different projects may require different behaviors.