How much of a data analyst's day is spent writing SQL?

Most of it. On a typical day, 3 to 5 hours go into writing, testing, and fixing SQL queries. That's the bulk of the work, not a side skill. The queries aren't glamorous—you're pulling a table, checking if the numbers match what someone expects, joining it to another table, and formatting it so a non-technical person can read it.

Do data analysts use Python every day?

Not at the entry level, and often not later either. SQL and a spreadsheet tool cover most entry-level and mid-level analyst work. Python shows up more in data engineering, machine learning, or advanced analytics roles, not in the daily grind of a standard analyst seat.

What meetings does a data analyst attend?

A typical week includes a team standup, one or two stakeholder meetings where you present or explain a number, and the occasional call where someone wants to understand a dashboard they can't read on their own. The skill that matters most in these meetings is explaining a number in one sentence to someone who doesn't care how you got it.

Is being a data analyst boring?

Some of it, yes. Most days include stretches of repetitive query writing and data cleanup that nobody would call exciting. The interesting part shows up when a chart finally answers a question someone's been asking for weeks, or when you catch an error before it reaches a director's inbox.

What's the difference between a junior and senior analyst's day?

A junior analyst spends more time on execution: writing the queries, building the dashboard, fixing the data someone else flagged. A senior analyst spends more time deciding what should get built in the first place and pushing back when a request doesn't make sense. Both still write SQL most days. The senior version just spends less time on syntax and more time on judgment.

What tools does a data analyst use daily?

In order of frequency: SQL editor, a BI tool like Tableau or Looker, spreadsheets like Excel or Google Sheets, Slack or email, and Python (occasionally). SQL editor is used most, while Python ranks lower than many expect, especially at the entry level.

Data Analyst vs Business Analyst: Which Role Is Right for You?

Data analyst and business analyst are two roles that sound almost identical on paper but pull in pretty different directions in practice. If you're trying to figure out which one to target, the distinction matters — because the tools, the interviews, and the day-to-day work are not the same job.

Here's the direct answer: a data analyst works primarily with data systems — SQL, BI tools, databases — to find patterns and answer quantitative questions. A business analyst works primarily with stakeholders and processes — requirements gathering, documentation, systems analysis — to solve organizational problems. One role is heavier on data tools. The other is heavier on communication and process work.

Both are legitimate paths into a well-paying career. Here's how to figure out which one fits you.

What does a data analyst actually do?
What does a business analyst actually do?
Skills comparison: data analyst vs business analyst
Salary: what each role pays
Which role is easier to break into?
How to decide which path fits you
FAQ

What does a data analyst actually do?

A data analyst's job is to answer questions with data. Someone in the business has a question — why did sales drop, which product line is most profitable, where are users dropping off — and the analyst pulls the data, runs the numbers, and comes back with an answer.

On a typical day, that looks like:

Writing SQL queries to extract data from a warehouse or database
Building and maintaining dashboards in Tableau, Power BI, or Looker
Cleaning and transforming data in Excel or Python before analysis
Presenting findings to business stakeholders who don't work in data
Running ad hoc analysis when something unexpected happens in the numbers

The core of the role is quantitative. You're spending most of your time in SQL and a BI tool. The communication piece matters, but it's secondary to the technical work.

I broke into data analytics without a relevant degree. The skills I actually used on the job were SQL, Excel, and Tableau. The fundamentals are narrow — you can build real competency in months, not years, if you focus on the right things instead of trying to learn every tool that exists.

What does a business analyst actually do?

A business analyst's job is to figure out what a business needs and translate that into something actionable — usually for a technology or process change. The work is more about requirements and communication than data systems.

On a typical day, that looks like:

Meeting with stakeholders to understand what they need from a system or process change
Writing requirements documents, user stories, or process maps
Working with development or IT teams to make sure what gets built matches what the business asked for
Running gap analysis between current processes and desired outcomes
Managing projects or workstreams, often acting as the bridge between business and tech teams

Business analysts often work with data too, but the data work is lighter — Excel reporting, basic dashboards, some SQL at more technical companies. The heavier lift is in communication, documentation, and process analysis.

The title "business analyst" also varies more by company than "data analyst" does. At some companies, a BA is essentially a project manager. At others, it's closer to a data analyst role. Always check the job description for what tools and responsibilities show up.

Skills comparison: data analyst vs business analyst

This is where the 2 roles diverge most clearly.

Data analyst core skills:

SQL — the most important technical skill; most of your work lives here
Excel and Google Sheets for data cleaning, quick analysis, and reporting
A BI tool: Tableau, Power BI, or Looker
Basic statistics: averages, distributions, growth rates, correlation
Python or R (useful but often not required at entry level)
Clear communication of quantitative findings to non-technical audiences

Business analyst core skills:

Requirements gathering and documentation — translating business needs into written specs
Process mapping and workflow analysis (tools like Visio, Lucidchart, or just clear writing)
Excel for reporting and basic data analysis
Familiarity with project management frameworks (Agile, Scrum, waterfall)
Stakeholder management — running meetings, managing expectations, facilitating decisions
SQL at some companies, especially those that call the role "data BA" or "technical BA"

If you genuinely enjoy working in data systems, SQL, and BI tools, data analyst is the right fit. If you're more energized by process problems, communication, and working across teams to make things happen, business analyst is worth considering.

For the data analyst path specifically, the Analyst Hive program focuses on exactly the SQL, Excel, and BI skills that show up in actual analyst roles — not a broad survey of every tool, just what gets you hired.

Salary: what each role pays

Both roles pay reasonably well. Data analysts tend to earn slightly more, especially at companies where technical depth is valued.

For data analysts in the US, entry-level salaries typically run $55,000 to $80,000. Mid-level roles land around $80,000 to $110,000. Senior analysts at larger companies can reach $120,000 to $140,000.

Business analysts follow a similar entry-level range — $55,000 to $75,000 is common for junior roles. Mid-level BAs earn $75,000 to $100,000 at most companies. Senior BAs and those who move into product ownership or business architecture can reach $110,000 to $130,000.

The gap widens at the top end. Senior data analysts at tech companies often out-earn senior BAs because the technical skills are harder to find. That said, experienced BAs who move into product management or program management can close the gap significantly.

Neither role has the salary ceiling of data engineering or data science, but both pay well enough to build a strong career without a graduate degree.

Which role is easier to break into?

Business analyst is often slightly easier to break into without a technical background, but the answer depends on what your existing background looks like.

If you're coming from a non-technical field — operations, project coordination, business administration, HR — the BA path has a lower technical bar. The core skills are communication, documentation, and process thinking, which many people have built without realizing it.

If you're willing to invest a few months learning SQL and a BI tool, data analyst becomes very accessible even without a technical degree. The job market for data analysts is large, the skills are learnable, and the interview process tests specific, practiceble things.

A few practical differences worth knowing:

Data analyst interviews almost always include a SQL assessment — this is specific, testable, and you can prepare for it directly
Business analyst interviews lean more toward behavioral questions, case studies, and process scenarios — less technically specific, but harder to prepare for without real examples from your experience
Data analyst portfolios can be built with public datasets and free tools — 2 or 3 solid SQL and Tableau projects can get you an interview
Business analyst portfolios are harder to build without work experience, since the work product is mostly internal documents and process artifacts

I have 125,000 followers on LinkedIn who are mostly trying to break into data. The people who stall out on the BA path are usually those without relevant work experience to draw from in interviews — the role relies heavily on past examples. On the data analyst side, people stall out when they try to learn everything instead of getting competent in SQL and one BI tool first.

How to decide which path fits you

A few direct questions that cut through it:

Go data analyst if:

You want to spend most of your time working in data tools — SQL, Excel, BI platforms
You're comfortable building technical skills from scratch over a few focused months
You want a role where your output is quantitative answers and dashboards
You're targeting companies where data work is clearly technical, not just reporting in Excel

Go business analyst if:

You have a background in operations, coordination, or process work you can draw from in interviews
You're more energized by solving organizational problems than by working in data systems
You want a path into product management or program management over time
The idea of writing requirements docs and facilitating stakeholder meetings sounds more appealing than writing SQL queries

There's no wrong answer. Both roles pay well, have clear career progression, and are accessible without a specialized degree. The real question is where you want to spend your working hours — and what kind of problems you actually want to solve.

FAQ

Is a data analyst or business analyst more in demand?

Data analyst roles have seen stronger job growth over the last several years, driven by the expansion of data infrastructure at companies of all sizes. Business analyst roles are more stable and widespread across industries but haven't grown at the same rate. Both have solid job markets.

Can a business analyst transition into data analytics?

Yes, and it's a common move. BAs who pick up SQL and a BI tool can reposition themselves as data analysts, often without starting over. The stakeholder communication skills transfer directly — the technical gap is the main thing to close.

Do business analysts use SQL?

At some companies, yes — especially in tech and at companies that call the role a "technical business analyst" or "data BA." At others, the data work stays in Excel. Check the job description: if SQL is listed, treat it as required. If it's absent, you may not need it at all.

Which role has better long-term career growth?

Both have strong paths. Data analysts can move into senior analyst, analytics manager, data science, or data engineering roles. Business analysts commonly move into product management, program management, or business architecture. The ceiling depends more on the industry and company than the role title.

Can you do both roles at the same company?

At smaller companies, the lines blur. You might join as one and end up doing the other. At larger companies, the roles are distinct with separate teams, different managers, and different toolsets. If you want both, it's worth being intentional about which skills you build first.

Where to go from here

If data analyst is the path, Analyst Hive is a day-by-day program built to take you from zero to job-ready. It covers the SQL, Excel, and Power BI skills that actually show up in analyst roles, plus the resume, portfolio, and interview prep that gets you hired. Month 1 builds your assets. Month 2 sharpens them. Month 3 gets you into interviews and negotiations.