Skip to content

Business & Productivity · Career

Data analyst skills checklist for your first job

The skills that appear in entry-level data analyst listings, split into the ones you need before applying and the ones you can learn on the job. Plus the one most people skip.

The Nextversity teamBusiness & Productivity schoolUpdated August 10, 20266 min read

On this page
  1. The short answer
  2. Tier 1: before you apply
  3. Tier 2: learn on the job, or shortly after
  4. Tier 3: nice to have, often oversold
  5. The skill everybody skips
  6. What a first portfolio looks like
  7. When this is not the right path
  8. Where to build the toolkit

The short answer

Entry-level data analyst listings ask for the same short list nearly every time: spreadsheets, SQL, one visualization tool, and the ability to explain what you found. Everything else is a bonus.

The order matters. Spreadsheets get you in the door of a lot of adjacent roles, SQL is the real filter on analyst listings, and the explaining is what decides whether you keep growing once you are in.

Tier 1: before you apply

Spreadsheets, properly. Not just formulas: lookups, pivot tables, cleaning, and structuring a workbook so somebody else can follow it. This is the daily tool in more analyst jobs than any conference talk admits.

SQL. SELECT, WHERE, GROUP BY, ORDER BY, and joins. If you can pull the last quarter's orders joined to their customers and grouped by region, you can do most of what a junior analyst does with a database. Joins are the concept worth the extra hour.

One charting tool. Excel charts count. So do Google Sheets, Power BI, Tableau or Looker Studio. Pick whichever your target employers mention and learn to make three clean charts, not thirty decorated ones.

Plain-language explanation. Take a finding and write four sentences: what you looked at, what you found, how confident you are, and what you would do next. This is the skill that separates candidates in interviews, and almost nobody practices it.

Tier 2: learn on the job, or shortly after

  • Statistics fundamentals. Mean versus median, distribution shape, sample size, and why correlation is not causation. Enough to avoid confidently wrong conclusions.
  • Data cleaning at scale. Power Query in Excel, or the equivalent in your stack. The reality of the job is that most of it is cleaning.
  • Dashboard design. Fewer charts, clearer labels, one message per screen.
  • A scripting language. Python with pandas is the common one. Genuinely useful, rarely a gate for a first role.
  • Domain knowledge. Knowing what a churn rate means in your industry is worth more than another tool.

Tier 3: nice to have, often oversold

Machine learning, big data platforms, advanced statistical modeling. These belong to data science roles rather than analyst roles, and chasing them early is a common way to spend six months and still not be job-ready. The US Bureau of Labor Statistics profile for data scientists shows how different that path is from the analyst one, and its market research analyst profile is closer to what many analyst jobs really involve.

Nobody was ever turned down for a junior analyst job because they had not used a neural network. Plenty have been turned down because they could not explain a chart.

The skill everybody skips

Asking better questions.

Most analysis requests arrive vague: "can you look at churn". A good analyst turns that into something answerable before opening any tool. Which customers, over what period, compared to what, and what decision will the answer change?

Practice this by writing the question down before you touch the data, every time. If you cannot write it, the analysis will not have a point, and no amount of chart polish saves it.

What a first portfolio looks like

Three short pieces are plenty. Each one should state a question, show the work, and end with a finding.

  1. A cleaning project. Take a genuinely messy public dataset and document how you made it usable. Boring, and hiring managers love it because it is what the job is.
  2. A SQL analysis. Query a public database, answer a specific question, show the query.
  3. A small dashboard. Three or four charts on one screen that answer one recurring question, with a paragraph explaining what a reader should do about it.

Publish them somewhere linkable. A shared document is fine. Presentation matters less than the reasoning being visible.

When this is not the right path

If you dislike spreadsheets and find data tedious, this career will not improve on acquaintance. It is a lot of cleaning and a lot of stakeholder conversations.

If your goal is building software, programming is a more direct route. And if you are already in a role that touches data (operations, finance, marketing), the fastest path is usually to become the person who does the analysis there, not to start over.

Where to build the toolkit

Excel data analysis covers the spreadsheet half and Database management using SQL covers the query half. Those two are the ones that appear in almost every listing. One subscription opens both, plus the whole Business & Productivity school.

Learn the two tools, do three small projects, and practice explaining them out loud. That is the checklist.

Questions people ask

What skills do you need to be a data analyst?

Spreadsheets, SQL, a charting or dashboard tool, and the ability to explain a finding in plain language. Statistics helps and Python is a bonus. Communication matters more than most people expect.

Do I need Python to be a data analyst?

Not for most entry-level roles. SQL and spreadsheets cover the majority of the work. Python becomes valuable when the analysis repeats, when the data is too big for a sheet, or when the team already uses it.

How much statistics does a data analyst need?

Enough to avoid misleading yourself: averages versus medians, sample size, correlation not implying causation, and what a percentage change is measured against. Formal statistical modeling is usually a data scientist job.

What tools should I learn first?

Excel or Google Sheets first because they are everywhere, then SQL because it is the real gate on most listings, then one visualization tool. Learn them in that order rather than in parallel.

How do I get experience without a job?

Analyze data you can get hold of: public datasets, your own spending, a club or side project's numbers. Write up three short pieces that state a question, a method and a finding. That is a portfolio.

Keep reading