Analytics engineering and data analysis are related but distinct disciplines. Data analysts turn data into insight; analytics engineers build the data infrastructure that makes analysis possible. This guide clarifies the distinction, describes how the two roles interact, explains the skills each requires, and helps organisations understand when they need which — or whether one person can do both.
The Distinction in Practice
Data analyst and analytics engineer are related but distinct disciplines. Both work with data. Both write SQL. Both produce outputs that inform business decisions. The distinction is in what they are primarily building:
**Data analysts** turn data into insight — they investigate business questions, produce analyses, build reports and dashboards, and communicate findings to stakeholders. Their output is understanding.
**Analytics engineers** build the data infrastructure that makes analysis possible — they model raw data into clean, reliable, well-documented tables that analysts query. Their output is reliable data.
The simplest frame: analytics engineers build the roads; data analysts drive on them.
What Data Analysts Do
Data analysts are the primary interface between business questions and data. Their core responsibilities:
**Ad-hoc analysis**: Answering specific business questions — why did churn increase last month, which channels are driving the most qualified leads, how does retention differ between pricing plans? This requires SQL proficiency, statistical intuition, and business context.
**Dashboard and report building**: Creating Tableau, Power BI, or Looker dashboards that give business stakeholders visibility into ongoing performance. Includes designing the layout, selecting appropriate visualisations, and maintaining report accuracy as the underlying data changes.
**Business performance monitoring**: Owning the metrics that matter to a business unit — tracking performance against targets, flagging anomalies, providing context for trends.
**Stakeholder communication**: Translating data findings into business language — not "the regression coefficient is 0.3" but "for every additional support ticket in the first 30 days, users are 30% more likely to churn."
**Skills**: SQL (analytical queries, window functions, aggregations), BI tools (Tableau, Power BI, Looker), statistics (distributions, correlations, hypothesis testing), business domain knowledge, clear written and verbal communication.
What Analytics Engineers Do
Analytics engineers sit between raw data sources and the analysts who query them. Their core responsibilities:
**Data modelling**: Transforming raw tables — landing zone data from Fivetran, Airbyte, CDC pipelines — into clean, purpose-built analytical tables. Staging models clean and standardise. Mart models join, aggregate, and name data for specific analytical use cases.
**dbt development**: Writing dbt models, tests, and documentation. Maintaining a project structure that is version-controlled, tested, and documented. Designing the layered architecture (staging, intermediate, mart) that separates raw data from analytical data.
**Data quality and testing**: Writing dbt tests (uniqueness, not-null, accepted values, referential integrity) and defining expectations about what well-formed data looks like. Owning the reliability of the data that analysts depend on.
**Semantic layer management**: Defining and maintaining the shared data model that BI tools query — Tableau published data sources, Power BI semantic models, LookML. Ensuring consistent metric definitions across reports.
**Performance optimisation**: Designing models for warehouse performance — materialisation strategies, incremental models to avoid full rebuilds, partition and cluster key selection.
**Skills**: SQL (transformation logic, performance optimisation), dbt (modelling, testing, documentation), data warehouse architecture (Snowflake, BigQuery, Redshift, Databricks), version control (Git), dimensional modelling, data pipeline awareness.
How They Work Together
In a mature analytics organisation, analysts and analytics engineers collaborate closely:
**Analyst identifies need**: An analyst building a churn dashboard discovers they need a cohort assignment column that does not exist in any current table.
**Analytics engineer builds it**: The analytics engineer adds the column to the appropriate mart model, writes the dbt test to validate it, documents it in the schema.yml file, and merges the change.
**Analyst uses the result**: The analyst queries the new column and builds the dashboard on reliable, tested data.
This separation of responsibilities is the key insight: analysts should spend their time on analysis, not on debugging unreliable data or building transformation logic that should be in the warehouse layer. Analytics engineers free analysts from the infrastructure work that would otherwise consume their time.
When One Person Does Both
Many organisations — particularly small to mid-size data teams — have individuals who do both roles. The title "data analyst" at a company without analytics engineering infrastructure often means the analyst is also doing the modelling work: writing the transformation SQL, maintaining the pipeline, debugging data quality issues, and maintaining the BI tool semantic layer.
This is not inherently bad, but it has a ceiling. An analyst spending 60% of their time on data engineering work has 40% left for actual analysis. As data volume and complexity grow, the engineering work grows faster than the analysis work, and the individual becomes a bottleneck.
The signal to hire an analytics engineer (or build out the role within an existing data team) is when: data reliability issues consume significant analyst time; multiple analysts are writing duplicate transformation logic; the BI tool semantic layer is inconsistent between reports; or dbt would create significant leverage but nobody owns it.
Seniority and Career Path
**Data analyst career path**: Analyst → Senior Analyst → Analytics Lead → Director of Analytics (or Chief Data Officer). Senior analysts are defined by domain expertise and stakeholder influence as much as technical depth. Analytical leadership is as much about translating business strategy into measurement frameworks as it is about SQL.
**Analytics engineer career path**: Analytics Engineer → Senior Analytics Engineer → Analytics Engineering Manager (or Principal Analytics Engineer). The senior individual contributor path goes deep on data modelling, warehouse architecture, semantic layer design, and dbt at scale. The manager path involves owning an analytics engineering team and the data reliability for a business unit or organisation.
Some analytics engineers move toward data engineering (building and owning the pipelines, not just the models). Some move toward data product management (owning the data assets used by many teams). Some remain deep technical contributors throughout their careers.
Our data architecture practice provides analytics engineering consulting and team augmentation for data teams building their modelling infrastructure — contact us to discuss your team's requirements.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →