Comment by secondtimepost | Hacker News Reader

Comment by secondtimepost | Hacker News Reader

City of Minneapolis | Data Engineer I | Minneapolis, MN | Full-Time | Remote or Hybrid (MN or WI candidates only)

As the largest and most vibrant city in the state, Minneapolis depends on purposeful, dedicated and innovative employees. Minneapolis has a large variety of careers for people of all experiences and backgrounds who come together for a singular purpose—serving the residents, businesses, and visitors of Minneapolis.

This position will be working on the Data + Analytics Services team, which is part of the Enterprise Data and Solutions division of IT. This position will design and maintain databases used for self-service ad hoc querying, custom applications or other production data warehouse environments for performance and reliability. The position will also contribute data engineering expertise to analytic and transparency initiatives.

Examples of projects: https://www.minneapolismn.gov/government/government-data/dat...

If you are interested, you are encouraged to apply: https://www.governmentjobs.com/careers/minneapolismn/jobs/39...

I don't understand the scaling of the titles here. Data Engineer I - which indicates the lowest level in most tech jobs or any careers - requires

"Experience Six years of experience in information technology, which have included four years experience maintaining or troubleshooting enterprise datamarts and ETL Packages."

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.

> 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.

@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!

Reply on news.ycombinator.com