You don't need to learn every tool on a data analyst posting before you apply. You need SQL that holds up under pressure, one dashboard tool you know well, and the habit of checking your numbers before anyone else does. Pay moves around, but skills take a while to build, so learn them in this order and let the rest wait.
| Certificate | Best for | Effort | Worth it? |
|---|---|---|---|
| Google Data Analytics Professional Certificate | Career changers who want a structured start | a couple of months of evenings | A decent map of the basics and a recognisable name on a resume. It won't carry you on its own, so pair it with a project on real data. |
| Microsoft Certified: Power BI Data Analyst Associate | Anyone targeting companies that run on Microsoft tools | a few weekends if you already use Power BI | The most useful one for working analysts. It tests DAX, data modelling and report design, which is the actual job at a Power BI shop. |
| Tableau Certified Data Analyst | Analysts whose target teams build in Tableau | a month or so of steady practice | Worth it if Tableau shows up in most of the postings you want. A strong Tableau Public profile can do the same job for free. |
Exam content, prices and names get updated, so check the details on Google's, Microsoft's or Tableau's own site before you pay for anything.
Created dashboards and reports using SQL and Tableau.
Rewrote 14 SQL reports as 3 dbt models feeding one Tableau dashboard, fixing a double-counted refund join that had overstated monthly revenue by $85K and cutting weekly report prep from 5 hours to 20 minutes.
Look at the postings in your area and count which one comes up more. Power BI is common at companies already on Microsoft tools, and Tableau shows up a lot in tech and marketing teams. Once you know one well, the other takes weeks, not months.
Less than a stats degree covers, but more than averages. You'll use distributions, medians versus means, correlation and the logic behind a test result.
Not before. Learn it once you're writing SQL daily and notice the same logic copied across reports. That's the problem it solves, and it'll make sense right away at that point.
Checking row counts. Before and after every join, look at how many rows you have. It catches more wrong answers than any clever technique.