Soldato
I might have someone who's just completed the 2 year grad scheme join at 50k, and then I interview someone who's got 10 years experience who joins at 100k - they all work supporting the same kit for the same customers in the same team - so they all have the same title and job description.Then surely you categories each job role then have a set salary unless it's like sales or something. There's only so many categories you can do in a workplace. If it's DevOps Engineer then that's 1 role, with 1 salary.
Unless that's a role where it's paid per fix or something like that? I do understand where people are coming from though.
We have tried banding our roles into various levels but it doesn't really work and becomes a situation where time in service = more pay. This didn't work for us - so now its talent and delivery = more pay
Since moving to this model we have seen increased staff retention, and it makes it far easier to have salary conversations with people. Those on lower pay can see exactly how much value and work others are generating - so have things to work toward that we can help them move forward with. Before this they were just trying to check boxes on a form from HR that said junior/senior/principal and they couldn't capture things like creativeness/innovation/commitment to role etc.