> "Senior engineer/dev" is a title, this is not the same as being the 'senior member' of the team. I call bs. I should probably say, “that hasn’t been my expe

> "Senior engineer/dev" is a title, this is not the same as being the 'senior member' of the team. I call bs. I should probably say, “that hasn’t been my experience”, but I just flat out don’t believe you. So, let me get this straight. In 20 years, you’ve found that senior developer is the role given to developers who have no responsibility above what a junior developer has, they just cost more? Rubbish. It’s a sliding scale; I bet you those senior developers have other responsibilities; code reviews, mentoring, deployments, prod support, ci/cd. I have never worked in, or heard of, an organisation where senior developers just get to sit around, goof off and write code all day… but get paid a senior developer rate. Sounds great! What organisations are these? I want to work there! Hook me up. I think you’re suggesting that responsibility for team and project management is like a step function; you get none until you’re a principal. That certainly hasn’t been my experience. I honestly just have to say I flat out don’t believe that in 20 years at large organisations it has been yours either.