You Think You’re a Data Analyst. You Might Actually Be an Analytics Engineer

When the job title says ‘Data Analyst’ but the work says ‘figure it out and make it scalable.

You’ve got the title, the warehouse access, and a growing collection of dashboards with your name on them. You’re delivering numbers, answering questions, and technically doing what a data analyst is meant to do.

But somewhere between refreshing the same report for the fifth time and being asked to “just add one more KPI” something starts to feel off.

You’re asked to bring in a new data source. Then to fix a report that keeps breaking. Then to make sure a table refreshes automatically because “the business needs it every morning.”

None of this feels dramatic, but it does feel heavier than analysis.

You start questioning yourself. Are you under-supported? Is this normal? Do you need a data engineer? Or are you simply not good enough at the role you were hired for?

Here’s the truth most people don’t say out loud: if this sounds familiar, you’re probably not failing as a data analyst. You’re growing out of the role.

What’s actually happening is a shift in how you think about data. Your work slowly moves away from answering questions and toward shaping the data itself. You’re spending less time on charts and more time thinking about structure, reliability, and repetition.

At some point, you catch yourself thinking things like:

• Why am I doing this manually again?
• This could be automated.
• This logic shouldn’t live in a spreadsheet.
• Why does this break every time a new column appears?

That’s not “bad analysis.” That’s systems thinking.

I’ve been there. I was hired as a data analyst and spent a surprising amount of time adding fields, refreshing tables, fixing joins, and rebuilding logic that clearly shouldn’t have been rebuilt every week.

Eventually, it clicked: once you automate most traditional analyst tasks, especially in a small startup, there isn’t much analysis left. What remains is the work that makes analysis possible in the first place.

That’s analytics engineering.

The confusing part is that nobody hands you a clean definition. There’s no announcement, no promotion meeting where someone says, “You’re an analytics engineer now.” The role lives in the grey space between analytics and engineering, and it looks slightly different everywhere.

But in practice, analytics engineering usually means you’re doing things like:

• Building and maintaining data pipelines
• Transforming raw data into clean, usable models
• Working directly in the warehouse
• Using tools like dbt, LookML, and BI layers
• Making sure metrics are consistent, trusted, and scalable

It’s not about abandoning analysis. It’s about owning the foundation beneath it.

For many people, this isn’t a dramatic career pivot. It’s a natural progression. If you enjoy the technical side of the job, like thinking in systems, and feel more satisfaction fixing root causes than patching symptoms, analytics engineering probably already suits you.

And if you recognise yourself here, that’s a good sign.

It means you’ve stopped seeing your role as purely reactive. You’re no longer just responding to requests; you’re thinking about how data should work. That mindset shift matters more than the job title.

So take the leap, even if it’s gradual.

At some point, you stop waiting for permission and realise the leap was always part of the job.

Start small. Learn how your data is modelled. Explore dbt projects. Get comfortable working closer to the warehouse.

Ask yourself one simple question: could I take a source, clean it, structure it, and present it in a way that scales beyond the initial scope?

If the answer is yes, or if learning how excites you, then you might not be “just” a data analyst anymore.

You’re an analytics engineer in the making. And once you see it that way, your role stops feeling confusing and starts feeling intentional.