The word "analyst" in a course title hides three different professions with different tools, salaries and personality fits. Data analyst, product analyst and business analyst overlap by roughly a third; the rest is separate skill sets. Choosing wrong costs about six months: a people person drops out of a SQL-and-Python program, while a would-be modeler spends half a year drawing process diagrams. Here is how the roles differ in practice and how to pick a direction before you pay for a course.
Three roles, one example
Take a food-delivery service where repeat orders are falling. The data analyst pulls order history, builds a data mart, computes retention by cohort and shows that the drop comes from customers whose first order arrived more than 20 minutes late. The product analyst takes that hypothesis, designs an A/B test with compensation for late deliveries, calculates the required sample size and reports two weeks later whether the compensation pays for itself. The business analyst goes to logistics and support, maps how an order is handed to a courier today, finds where minutes are lost and writes requirements for the dispatch system.
One problem, three kinds of work. The first lives in data, the second in experiments and product metrics, the third in processes and requirements.
Side-by-side comparison
| Parameter | Data analyst | Product analyst | Business analyst |
|---|---|---|---|
| Core question | What is happening and why? | Which product change will pay off? | How should the process work and what does the system need? |
| Main tools | SQL, Python (pandas), BI tools, Excel | SQL, statistics, A/B platforms, event trackers, BI | BPMN/UML, Confluence/Jira, prototypes, basic SQL |
| Math load | Moderate: descriptive statistics, basic probability | Highest: hypothesis testing, confidence intervals, test power | Lowest: project impact, unit economics |
| Share of people work | 20-30% | 40-50% | 60-70% |
| Reports to | Head of analytics or CDO | Product manager | Project lead or business owner |
| Grows into | Data engineer, data scientist, analytics lead | Product manager, head of product analytics | Systems analyst, project manager, product owner |
| Typical first project | Regional sales dashboard | Funnel review with a proposed test | As-is process map and a change request |
Shared skills and separate ones
All three share a core: confident SQL, the habit of asking clarifying questions, and the ability to explain findings to non-technical people. Learn SQL regardless; it transfers between roles.
Then the paths split. A data analyst needs Python for tables and charts plus one BI tool known in depth. A product analyst needs enough statistics to explain why a test must not be stopped early, and a grasp of product metrics: retention, funnel conversion, LTV. A business analyst needs process notations, requirement-gathering techniques (interviews, observation, document analysis) and the skill of writing a spec a developer reads only one way.
A related role is the 1C analyst: essentially a business analyst tied to one ERP platform, in steady demand wherever accounting runs on 1C.
How to tell which one fits you
A simple test: the day before buying a course, spend an hour on each of three tasks. Download an open dataset and find the weekday with the highest sales in a spreadsheet. Then pick any app on your phone and write half a page on which metric you would improve and what experiment would prove it. Finally, map step by step how purchasing works at your current job and what could be removed. The task you want to keep doing is your answer.
The second signal is prior experience. Accountants and logisticians move faster into business analysis; marketers and support managers fit product analytics; people with technical degrees, or who like digging into numbers alone, fit data analysis.
Course checklist for your chosen direction
- The course names your specific role, not "analyst" in general; data and business analytics are different programs.
- SQL takes at least a quarter of the syllabus, with exercises on JOINs, window functions and grouping.
- Data analyst: Python and BI with a project you can show, not an overview.
- Product analyst: a dedicated module on statistics and A/B testing with sample-size calculation.
- Business analyst: practice in requirement gathering and spec writing with instructor feedback.
- The final project can be published in a portfolio rather than staying locked inside the platform.
- Full cost with installments calculated and compared against two or three other schools.
FAQ
Can you become an analyst without a technical degree?
Yes, in all three roles. In business analysis, domain experience often matters more than a diploma; in data and product analytics, the portfolio and interview problem-solving decide. A technical degree speeds things up but is not a filter.
Which role gets you hired fastest?
Usually data analyst: more openings, and junior requirements are spelled out clearly (SQL, Excel, one BI tool). A business analyst without domain experience searches longer; product analysts often grow out of data analysts inside a company.
What if I choose wrong?
Switching is realistic because the core is shared: a data analyst with product curiosity becomes a product analyst within a year, and a business analyst who adds SQL and Python moves into data.
Bottom line
Choose by the kind of work you are willing to do every day, not by the salary in an ad: data, experiments or processes. Learn SQL either way. Detailed role pages with tasks, salaries and growth paths: data analyst, business analyst and product manager, where the product track leads. Programs for all three directions are in the analytics course catalog.