zlacker

I've seen this with technical roles where you start in one job family and get promoted to another. E.g., Integration Analyst I....Integration Analyst IV -> Data Engineer I

There's also cases like Medical Doctors where the start already requires meaningful education and training.

Some titles/responsibilities aren't appropriate for someone with no experience but that doesn't make the people in those titles senior at that function.

>>datami+(OP)
> There's also cases like Medical Doctors where the start already requires meaningful education and training.

In this example, it's a bit different as in it is known across the industry.

>>kyawza+Of
@dataminded explained it pretty well, at least based on my experience. I'm not on the HR/hiring manager side of this one (technically a separate team I collaborate with), so I can only say that it does appear that it is the desired years of experience for this particular role.

Having worked for a number of years in both the private and public sectors, I can say that job titles and descriptions do not necessarily always align between the two. In other words, I understand what you're saying, and can empathize with your confusion.

If helpful, the job descriptions/classifications for all roles at the City of Minneapolis are available online:

https://www.governmentjobs.com/careers/minneapolismn/classsp...

I don't know that it will resolve the confusion entirely, but it may help to shed some light. Thank you again for the question!