10 Comments
User's avatar
Madison Mae's avatar

Very well laid out! Interestingly enough, my latest role is on a data team of only analytics engineers with a lot of dashboarding and analysis sprinkled in. Different than what I'm used to and what I think of as the typical "analytics engineer" role, but hoping it will be helpful in building even stronger AE skills!

Oleg Agapov's avatar

It's inevitable to perform tasks that are adjacent to AE work. I do that sometimes as well. But let's not make this into a rule 😅

Colette Molteni's avatar

This articulates something many people feel but struggle to name: role confusion isn’t a skills gap, it’s an empathy gap in how organizations design work. When expectations collapse multiple disciplines into one role, we don’t get “unicorns”, we get burnout and brittle systems. Clear boundaries aren’t limiting; they’re what allow analytics engineers (and the teams around them) to do their best thinking.

Oleg Agapov's avatar

Very well summarized, that you Colette 👍

Thais Cooke's avatar

This is very well explained. Thank you for sharing!

Peter Ndiforchu's avatar

Such a great article Oleg! Do also find that some Senior Data Analyst turn to be doing a lot AE related work? I find myself as an Analyst doing a lot AE work around building reusable data models to support downstream data products.

Oleg Agapov's avatar

Yes, I've experienced that as well, though I didn't know that I was doing AE work 😅

It happens in unexperienced teams or without a strong Head of Data who'd understand different kinds of roles and responsibilities.

chrsOlv's avatar

Clear and simple article, now could you please share it with all the LinkedIn recruiters? :)

Oleg Agapov's avatar

Haha, for sure!