“I want to work with data” is not a career plan — it’s a starting point that splits into very different jobs, and confusing them in interviews is a fast way to get rejected.
Data Analyst: answering questions with existing data
A Data Analyst takes data that already exists in clean, accessible tables and answers business questions — “why did sales drop in Q2?” — using SQL, Excel, and BI tools like Power BI or Tableau. The job is fundamentally about insight and communication.
Data Engineer: building the pipes that make data exist in the first place
A Data Engineer builds and maintains the infrastructure that collects, cleans, and stores data so analysts can use it. That means writing ETL/ELT pipelines, working with tools like Airflow and Spark, and thinking in terms of systems and reliability, not dashboards.
Why the confusion costs you offers
When a fresher says “I want to be a Data Analyst” but then talks entirely about building pipelines in their portfolio, interviewers get confused about what role to evaluate them for — and confused candidates get passed over for clear ones.
Pick your lane based on what you actually enjoy: storytelling with numbers (Analyst) or building reliable systems (Engineer). Then make every project and every sentence of your resume point in that one direction.
Leave a Reply