How to become a data analyst from scratch in 2026

What "from scratch" actually means

If you have never written code, never opened a database, and "left join" makes you nervous — that is truly from scratch. The good news: data analyst is one of the few six-figure tech roles that does not require a CS degree. The honest news: budget 4 to 8 months of real work, not the "30 days to data analyst" timeline a bootcamp ad promised.

The plan below ignores everything that does not show up in interviews and points you at SQL first, dashboards second, Python third — in that order, on purpose. Skip a stage and the next one collapses.

Realistic timelines

How long it takes depends almost entirely on how many hours per day you can put in. The hours compound — there is no shortcut where two hours on Saturday equals one hour daily.

Thirty minutes every single day will beat three hours every Saturday. Consistency, not intensity, is what pays the rent here.

The 5 topics that actually matter

Skip everything else until these five are solid. No machine learning, no Spark, no deep learning. Hiring managers for entry-level analyst roles screen for the same five every time.

1. SQL — the load-bearing skill

SQL is roughly 80% of what a junior analyst does day to day. It is also the first thing every screen tests. Walk into an interview without SQL and you will be walking back out within the hour.

Minimum surface area for junior:

-- The shape of what you should be able to write cold
WITH daily_signups AS (
  SELECT
    DATE_TRUNC('day', created_at) AS signup_day,
    user_id
  FROM users
  WHERE created_at >= CURRENT_DATE - INTERVAL '30 days'
)
SELECT
  signup_day,
  COUNT(DISTINCT user_id) AS new_users,
  SUM(COUNT(DISTINCT user_id)) OVER (
    ORDER BY signup_day
  ) AS running_total
FROM daily_signups
GROUP BY signup_day
ORDER BY signup_day;

That snippet uses CTEs, date truncation, aggregates, and a window function. If you can write it cold, you have cleared the bar for most junior screens. Drill on StrataScratch, DataLemur, LeetCode SQL, and Mode Analytics tutorials.

2. Product metrics

SQL without product sense is just syntax. The classic disqualifier is "how would you measure retention for our new feature" — and the candidate freezes because nobody taught them what D1, D7, D30, or a cohort actually mean.

Cover DAU/MAU/WAU, retention curves, conversion funnels with drop-off, and unit economics (ARPU, LTV, CAC). You do not need to be a PM. You do need to know what each metric measures and what makes it move.

3. Statistics — just enough

You need p-values, significance levels, Type I/II errors, the central limit theorem, confidence intervals, and the basic mechanics of an A/B test. Khan Academy's stats track is free and sufficient.

4. Python and pandas

Not every team uses Python daily, but enough do that "I cannot read pandas" closes doors. Get comfortable with DataFrame filtering, groupby, merge, and basic matplotlib/seaborn plots. Kaggle Learn is free; DataCamp works if you prefer guided exercises.

5. One BI tool

Pick one and ship a dashboard: Tableau, Power BI, Metabase, Looker, or Superset. A Tableau Public profile with three real dashboards beats a polished resume with zero. Tableau Public is free; that is where most beginner portfolios live.

A 16-week plan that works

This is the plan I would give a friend starting tomorrow with 2 to 3 hours per day. Adjust the calendar but not the order.

Weeks 1 to 4 — SQL foundations. SELECT, WHERE, ORDER BY, LIMIT. Every kind of JOIN. GROUP BY with all the aggregate functions. Five problems per day, every day. By the end of week 4 you should breeze through an "easy" tier on any SQL platform.

Weeks 5 to 6 — advanced SQL. Window functions (ROW_NUMBER, LAG, LEAD, SUM OVER), CTEs, correlated subqueries, date math, ranking. Most learners quit here. Push through.

Weeks 7 to 8 — product metrics. DAU/MAU, retention cohorts, funnels, unit economics. Take a Kaggle e-commerce dataset and compute these metrics yourself.

Weeks 9 to 10 — statistics. p-values, power, confidence intervals, and a clean walkthrough of an A/B test from hypothesis to readout.

Weeks 11 to 12 — Python and pandas. Just enough to wrangle a CSV, join two DataFrames, and plot a chart. No ML.

Weeks 13 to 14 — portfolio. Three projects on GitHub:

1. SQL analysis of a public dataset (e-commerce, NYC taxi, GitHub events)
2. A Tableau Public dashboard with at least 3 connected views
3. An A/B test write-up or a cohort retention analysis with charts

Weeks 15 to 16 — job hunt. Resume, LinkedIn rewrite, apply to 5 to 10 roles per day, take the first five interviews as practice. The first interview will go badly; that is the point.

Salary reality check by region

Bootcamp ads love to flash one number. Reality has tiers. These are entry-level data analyst base ranges from levels.fyi, Glassdoor, and Built In as of early 2026, before signing bonus or equity.

At top product companies — Google, Meta, Stripe, Airbnb, Netflix, Notion, Linear, Figma — entry-level total comp (base + bonus + equity) can land closer to $130k to $160k in the US thanks to equity. Those roles are competitive and usually want a referral or an internship. The median path is a 50-to-500-person company first, FAANG-tier second.

Fears vs reality

"I have no math background." Junior analysts do not solve differential equations. You need arithmetic, percentages, basic probability, and logic. If you can balance a spreadsheet you have the math.

"I am too old." Plenty of analysts get hired at 40+. Domain experience helps. The blocker is willingness to start on a junior salary, not age.

"I do not have a technical degree." Many working analysts came from humanities, finance, marketing, ops, or teaching. Hiring managers screen for a portfolio and the ability to think in data, not the line on your CV.

"Nobody will hire me with no experience." Roughly 30 to 40% of junior analyst postings on LinkedIn explicitly allow zero experience. Portfolio and take-home performance matter more than resume bullets.

"Bootcamps are expensive." They are, and they are optional. Coursera, DataCamp, Springboard, and Mode have low-cost tracks covering the same ground. The people who learn fastest treat one free platform like it costs $15k.

Where to find the first job

Spread the search across multiple channels — single-channel job hunts stall.

LinkedIn is the default. Filter for "data analyst," "junior," "entry-level," and your region. Set daily alerts. Send a short connection note to the hiring manager when you apply.

Glassdoor filters by salary band and shows interview reviews — knowing a company's loop cuts prep time in half. levels.fyi is the most reliable source for actual comp at tech companies; use it before you negotiate.

Built In and Wellfound (formerly AngelList) skew toward startups, where junior analysts get more ownership faster at lower base comp. Internships and new-grad programs at Google, Meta, Stripe, Airbnb, Notion run on fixed cycles — apply 4 to 6 months ahead.

Referrals beat cold applications by roughly 5x. Spend an hour a week in analytics Slack communities (Locally Optimistic, MeasureSlack), Reddit's r/analytics, and analyst meetups. One warm intro replaces fifty cold applications.

If you want to drill SQL questions like the ones on every screen — JOINs, windows, cohorts, retention — NAILDD is launching with 500+ SQL problems from real interviews at Google, Stripe, and Airbnb.

Common pitfalls

The first pitfall is learning everything in parallel. Beginners try to study SQL on Monday, Python on Tuesday, stats on Wednesday, and Tableau on Thursday, hoping breadth will compound. It does not. By Friday nothing is sticky and motivation tanks. Sequence the topics, finish one before adding the next, and your retention will roughly double.

A close second is collecting courses instead of finishing one. Six tabs of "I should take this someday" is not progress. Pick one SQL course, finish it, then move on. The marginal value of the second SQL course is much smaller than the value of building one project.

The third pitfall is skipping the portfolio. A clean LinkedIn with no GitHub or Tableau Public profile gets filtered before a human reads it. Hiring managers want to see you have shipped something — even three small projects beat zero polished ones. A messy dashboard you actually built beats a perfect dashboard you only watched a tutorial about.

Fourth is applying too late. Learners often wait until they "feel ready," which never arrives. Start applying around week 12 even if you feel underprepared. Early interviews are free practice — you will learn more in one bad onsite than in a week of solo study.

Fifth is anchoring on FAANG. Junior offers at Google or Meta exist but are heavily competitive. The realistic first job is at a 50-to-500-person company where the bar is "can you write a clean JOIN and explain a retention chart" — not "do you have a Stanford degree." Get the first offer, ship for 12 to 18 months, then jump tiers if you want.

Related reading

• SQL for data analysts
• Statistics for data analysts
• SQL window functions interview questions
• Cohort analysis data science interview
• A/B testing peeking mistake
• Why are you leaving — interview answer

FAQ

How long does it really take from absolute zero?

At 2 to 3 hours per day, plan for 4 to 6 months before your first offer. Full-time learners can compress to 2 to 3 months but tend to burn out around week 8 if they do not pace themselves. One-hour-per-day learners realistically need 8 to 12 months, including the job-hunt tail of 6 to 12 weeks on top of the study plan.

Do I need fluent English?

For US, UK, or remote roles at US-headquartered companies, yes — business-fluent English is required because most stand-ups, docs, and Slack channels run in English. For EU local-market roles in non-English-speaking countries, fluent English is a strong asset but not always mandatory. Technical English picks up naturally inside the first 3 to 4 months of any analytics study plan.

Can I do it without paying for a bootcamp?

Yes, and most working analysts did. Coursera, DataCamp, Mode Analytics, Kaggle Learn, and Khan Academy together cover everything a bootcamp covers, for under $200 if you pay for one platform. A $15k bootcamp buys structure, deadlines, and a Slack community — real value, but not the skill itself. The deciding factor is whether you ship a portfolio, and that is on you regardless of path.

What matters more — SQL or Python?

At the junior level, SQL by a wide margin. Roughly 80% of entry-level screens focus on SQL, and most analyst postings list SQL as required, Python as "nice to have." Python becomes critical at mid-level and above, especially on data science or ML-adjacent teams. Get SQL fluent first, then layer Python on top.

Should I get a master's degree first?

Almost never. A master's adds 18 to 24 months and $40k to $80k in cost, and the hiring uplift for a junior analyst role is small to zero. Exceptions: home markets that require a master's for visa sponsorship, or pivoting into data science / ML research where graduate-level stats matters. For analyst roles, a portfolio plus three months of focused SQL drilling beats a master's every time.

How many applications until the first offer?

Plan for 80 to 150 applications and 8 to 15 interview loops for a first analyst offer in a normal market. In a tight market that doubles. Track your funnel: applications, recruiter screens, technical screens, onsites, offers. If your application-to-screen rate is under 5%, the resume is the bottleneck; if your screen-to-onsite rate is under 30%, your SQL needs more drilling.