Data Analyst

What it is

Experimentation and causal inference decide whether a product or model change caused an outcome, how large the effect is, and whether the tradeoff is acceptable.

Why it matters

Product, growth, applied science, and health work all need causal discipline. Without it, teams over-credit launches, under-detect harm, and ship decisions based on biased observational data.

Proof to build

Analyze an experiment or quasi-experiment with hypothesis, primary metric, guardrails, power or MDE, segment checks, and a decision memo.

What it is

Spreadsheets is the practical work inside business and data foundations: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Spreadsheets matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Learn how teams define metrics, events, tables, and decision questions before touching a chart. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

Data literacy is the practical work inside business and data foundations: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Data literacy matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Learn how teams define metrics, events, tables, and decision questions before touching a chart. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

A business and data foundations portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one business and data foundations artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for business and data foundations is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns business and data foundations into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.

What it is

SQL analysis turns raw relational and event data into cohorts, funnels, user journeys, reporting tables, and defensible business metrics.

Why it matters

SQL is still the shared language across BI, product analytics, data engineering, governance, health analytics, and OR work. The practical bar is not syntax; it is avoiding double-counts, fanout joins, stale filters, and silent null bugs.

Proof to build

Solve a cohort or funnel analysis from raw tables, include validation queries, and explain how you checked row grain, duplicates, nulls, and date boundaries.

What it is

Aggregations is the practical work inside sql for analysis: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Aggregations matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Query, join, aggregate, window, and debug real business tables without memorizing syntax blindly. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

SQL analysis turns raw relational and event data into cohorts, funnels, user journeys, reporting tables, and defensible business metrics.

Why it matters

SQL is still the shared language across BI, product analytics, data engineering, governance, health analytics, and OR work. The practical bar is not syntax; it is avoiding double-counts, fanout joins, stale filters, and silent null bugs.

Proof to build

Solve a cohort or funnel analysis from raw tables, include validation queries, and explain how you checked row grain, duplicates, nulls, and date boundaries.

What it is

A sql for analysis portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one sql for analysis artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for sql for analysis is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns sql for analysis into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.

What it is

Python and pandas are the repeatable analysis layer: load data, clean it, reshape it, validate assumptions, automate checks, and package work so another analyst or engineer can rerun it.

Why it matters

SQL answers many warehouse questions, but real career work often needs Python for messy files, healthcare extracts, simulation inputs, forecasting prep, exploratory analysis, and reproducible notebooks.

Proof to build

Build a notebook or script that loads a raw dataset, profiles quality problems, cleans it, validates row counts and nulls, and exports a decision-ready table with clear assumptions.

What it is

NumPy is the practical work inside python and pandas: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

NumPy matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Use Python when analysis outgrows SQL: cleaning, reshaping, notebooks, and repeatable workflows. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

Python and pandas are the repeatable analysis layer: load data, clean it, reshape it, validate assumptions, automate checks, and package work so another analyst or engineer can rerun it.

Why it matters

SQL answers many warehouse questions, but real career work often needs Python for messy files, healthcare extracts, simulation inputs, forecasting prep, exploratory analysis, and reproducible notebooks.

Proof to build

Build a notebook or script that loads a raw dataset, profiles quality problems, cleans it, validates row counts and nulls, and exports a decision-ready table with clear assumptions.

What it is

A python and pandas portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one python and pandas artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for python and pandas is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns python and pandas into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.

What it is

Hypothesis tests is the practical work inside statistics for decisions: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Hypothesis tests matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Understand uncertainty, sampling, confidence intervals, and experiments well enough to avoid false certainty. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

A/B testing is the practical work inside statistics for decisions: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

A/B testing matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Understand uncertainty, sampling, confidence intervals, and experiments well enough to avoid false certainty. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

Confidence intervals is the practical work inside statistics for decisions: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Confidence intervals matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Understand uncertainty, sampling, confidence intervals, and experiments well enough to avoid false certainty. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

A statistics for decisions portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one statistics for decisions artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for statistics for decisions is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns statistics for decisions into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.

What it is

BI tooling turns governed data into dashboards, scorecards, drilldowns, alerts, permissions, refreshes, and recurring decision workflows.

Why it matters

Real BI value is not a pretty chart. It is a trusted operating surface that busy teams check without asking an analyst to explain every filter and caveat.

Proof to build

Build a dashboard case study with a metric dictionary, screenshot walkthrough, refresh plan, permission model, known caveats, and a QA checklist for the top numbers.

What it is

BI tooling turns governed data into dashboards, scorecards, drilldowns, alerts, permissions, refreshes, and recurring decision workflows.

Why it matters

Real BI value is not a pretty chart. It is a trusted operating surface that busy teams check without asking an analyst to explain every filter and caveat.

Proof to build

Build a dashboard case study with a metric dictionary, screenshot walkthrough, refresh plan, permission model, known caveats, and a QA checklist for the top numbers.

What it is

Storytelling is the practical work inside visualization and dashboards: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Storytelling matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Design charts and dashboards that answer the actual business question instead of decorating data. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

A visualization and dashboards portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one visualization and dashboards artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for visualization and dashboards is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns visualization and dashboards into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.

What it is

LLM application engineering connects prompts, structured outputs, retrieval, tool calls, and evaluation into a product workflow that users can trust repeatedly.

Why it matters

AI roles in 2026 are less about toy prompts and more about building systems that survive ambiguous inputs, private data, latency budgets, source grounding, and regressions after a model update.

Proof to build

Ship a small RAG or structured-output app with traces, citations, an evaluation set, fallback behavior, and a short writeup explaining the failure modes you found.

What it is

Validation is the practical work inside ai-assisted analysis: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Validation matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Use AI to speed up analysis while still validating SQL, assumptions, and conclusions yourself. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

Workflow design is the practical work inside ai-assisted analysis: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

Workflow design matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Use AI to speed up analysis while still validating SQL, assumptions, and conclusions yourself. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

A ai-assisted analysis portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one ai-assisted analysis artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for ai-assisted analysis is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns ai-assisted analysis into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.

What it is

dbt basics is the practical work inside modern data stack: the concepts, tools, checks, and deliverables a Data Analyst uses to turn this stage into real output.

Why it matters

dbt basics matters for Data Analyst because this stage is where a learner turns the role from a title into evidence. Learn enough dbt, warehouses, and data quality to collaborate with analytics engineering teams. A strong learner should be able to explain the tradeoffs, build a small artifact, and connect the result to a business or product decision.

Proof to build

Build a small artifact for this topic: a query, notebook, dashboard, architecture note, evaluation table, or decision memo that shows the input, method, validation, caveat, and recommendation.

What it is

Warehouse architecture covers storage, compute, marts, permissions, cost controls, performance tuning, deployment layers, and how data products are exposed.

Why it matters

Data architects and analytics engineers need enough platform judgment to avoid expensive, slow, or brittle designs. Cost, query latency, lineage, and ownership are architecture decisions, not afterthoughts.

Proof to build

Write an architecture decision record comparing two warehouse/lakehouse designs for the same workload, with cost, freshness, governance, and performance tradeoffs.

What it is

Data quality work defines expectations for completeness, freshness, validity, uniqueness, consistency, and business-rule compliance.

Why it matters

Every role that uses data depends on this layer. AI systems make the risk worse because bad source data can become automated bad decisions at scale.

Proof to build

Create tests for a small analytics pipeline: schema checks, null thresholds, accepted values, freshness, duplicate keys, and a failure runbook.

What it is

A modern data stack portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one modern data stack artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for modern data stack is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns modern data stack into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.

What it is

Portfolio and interview work turns learning into proof: a public artifact, decision memo, reproducible repo, diagram, dashboard, notebook, or interview story.

Why it matters

Hiring teams cannot infer readiness from a list of tools. They need evidence that you can frame a problem, make tradeoffs, validate your result, and explain the business impact.

Proof to build

Publish one role-specific artifact with README, assumptions, dataset notes, validation checks, screenshots, and a short hiring-manager summary of what the work proves.

What it is

SQL analysis turns raw relational and event data into cohorts, funnels, user journeys, reporting tables, and defensible business metrics.

Why it matters

SQL is still the shared language across BI, product analytics, data engineering, governance, health analytics, and OR work. The practical bar is not syntax; it is avoiding double-counts, fanout joins, stale filters, and silent null bugs.

Proof to build

Solve a cohort or funnel analysis from raw tables, include validation queries, and explain how you checked row grain, duplicates, nulls, and date boundaries.

What it is

Portfolio and interview work turns learning into proof: a public artifact, decision memo, reproducible repo, diagram, dashboard, notebook, or interview story.

Why it matters

Hiring teams cannot infer readiness from a list of tools. They need evidence that you can frame a problem, make tradeoffs, validate your result, and explain the business impact.

Proof to build

Publish one role-specific artifact with README, assumptions, dataset notes, validation checks, screenshots, and a short hiring-manager summary of what the work proves.

What it is

A portfolio and interviews portfolio artifact is a public proof piece for this stage: a small but complete deliverable that shows how a Data Analyst frames the problem, chooses tools, validates the result, and explains the tradeoffs.

Why it matters

This is the work product that makes the stage credible. For Data Analyst, the artifact should show inputs, assumptions, methods, validation, tradeoffs, and a decision-ready output rather than a tutorial clone.

Proof to build

Publish one portfolio and interviews artifact with README, inputs, assumptions, method, validation checks, screenshots or outputs, caveats, and a short summary of what the artifact proves for Data Analyst readiness.

What it is

The interview signal for portfolio and interviews is your ability to explain the work under pressure: assumptions, tradeoffs, failure modes, implementation choices, and how the output would help a real team decide what to do next.

Why it matters

Hiring teams need to see judgment, not just vocabulary. This topic turns portfolio and interviews into interview-ready stories, diagrams, live explanations, and examples that map to real Data Analyst work.

Proof to build

Prepare a two-minute explanation, one diagram or query/notebook walkthrough, and three follow-up answers for this stage: why this approach, what could fail, and how you would improve it in production.