Agreed, maybe a bad example.
But a team of SWEs at different experience levels for the same role won't be different job descriptions.
I'm in this situation right now, I have a minimum requirement, it could be MET with someone with 1-2 years of experience or 20 years.
But that is the MINIMUM, if I find someone that meets that minimum but I get a lot more, I will pay more. But I'm still not making multiple job descriptions with different ranges.
> But a team of SWEs at different experience levels for the same role won't be different job descriptions.
Why would you put people with different experience levels in the same role? You'll have three classes of people, only one of them "happy", for the others it'll be too much or too little. You cannot put a junior in the same position as a person who wants to be tech lead?
I think maybe I'm misunderstanding what you're saying, because having one job description for those three roles don't make much sense as I understand it currently.
You could just put multiple ranges and add additional details for what seniors/leads look like. You would have minimums for what those things are too, and those qualities would actually overlap a lot with a previous level's nice-to-have items.
There's valid conversation around the nuances of "what if this need isn't specific to a level?" but those don't excuse keeping people in the dark about what the job offers or requires.