I noticed that companies often differentiate between a job title and a role. 

On the one hand, the title is defined in your contract and is ofter connected so some kind of salary range. When you get promoted that title probably changes too.

On the other hand, the role tells what you are working on, what your role is within the team, what your work is focused on. 

For example, it is common that a software developer (title) is introduced as an Analyst or Consultant (role) to the client. A senior designer (title) might be a UX expert (role) or a project manager (title) can work in the role of a team lead.

And when you look at a typical career leader in a company there are often not many steps and therefore not must possible to choose from. But that is okay because the only thing the title defines is some kind of salary range within this company.

Whereas there are many different jobs to be done in a company and role to fill. It makes much sense to be specific. Someone can work in the role of a backend engineer, a requirement analyst, or a consultant for customers, and for the team and the client these roles are important, but from the point of HR they are all just software developers (title).