Data Analyst route

What to do next

Teaching Desk contains several old and future routes. This page is the decision layer: work only on the current stage and treat everything else as reference material.

Daily operating rule

1. Open this Guide and take one task from the highlighted stage.
2. Open that task, set it in progress, and run the study session from Daylife Desk.
3. Finish with the evidence requested by the task and a short learning note.
4. Ignore overdue dates and task counts outside the highlighted stage.

What each page is for

Guide:: decide what comes next.
Daylife Desk:: run today's task and timer.
Tasks:: read instructions and submit evidence.
Roadmap:: reference map, not today's queue.
Resources:: open only when a current task needs one.

Immediately after fCC RDB

1. Upload the final certificate in task #115.
2. Write the analyst bridge note in task #1310.
3. Finish the two SQL packs already in progress, then take one mixed checkpoint.
4. Begin SQL Analytics #1100.

The route

A stage unlocks when its required tasks are done.

Could not load task status. The route below is still valid; refresh the page after the API recovers.

Stage 1 Current

Finish and close freeCodeCamp Relational Databases

Finish what is already underway, preserve the evidence, and explicitly translate it into analyst skills.

0/2 required

Task #115

unknown

Task #1310

unknown

Tasks #1300-#1309 are audit checkpoints for sections already covered by the course. Mark them from existing work; do not redo course material merely to satisfy Desk.

Stage 2

Consolidate advanced SQL

Close the two packs already in progress and prove that CTEs, windows, JOINs, and aggregation work together.

0/3 required

Task #1002

unknown

Task #1001

unknown

Task #1003

unknown

Do not clear the entire old SQL backlog. Subqueries, schema design, transactions, and EXPLAIN become gap-specific resources.

Stage 3

Complete SQL for data analysis

Practice the actual analyst patterns: grain, cleaning, pivots, time series, funnels, retention, sessions, RFM, and attribution.

0/11 required

Task #1100

Task #1101

Task #1102

Task #1103

Task #1104

Task #1105

Task #1106

Task #1107

Task #1108

Task #1109

Task #1110

Stage 4

Build the Olist SQL case

Move from exercises to a realistic dataset, validated tables, safe joins, reusable marts, and dashboard-ready exports.

0/6 required

Task #1200

Task #1201

Task #1202

Task #1203

Task #1204

Task #1205

Stage 5

Create the spreadsheet handoff

Show that the analysis can be delivered to a stakeholder, not only queried by its author.

0/5 required

Task #1206

Task #1207

Task #1208

Task #1209

Task #1210

Power Query awareness task #1211 is useful, but it does not block the route.

Stage 6

Add Python and pandas to the same case

Use Python for repeatable validation, profiling, EDA, and charting after the SQL model already exists.

0/7 required

Task #1212

Task #1213

Task #1214

Task #1215

Task #1216

Task #1217

Task #1218

If task #1213 exposes a Python gap, use a small targeted supplement. Do not automatically start another full fCC curriculum.

Stage 7

Publish the Tableau dashboard

Turn the prepared marts into a public-safe executive dashboard with documented metric choices.

0/3 required

Task #1219

unknown

Task #1220

unknown

Task #1221

unknown

Stage 8

Package the analyst case

Write the business story, index the evidence, state assumptions, and make the case interview-ready.

0/2 required

Task #1222

unknown

Task #1223

unknown

Do not let these block the route

Use only for a diagnosed SQL gap

Core PostgreSQL practice, LearnSQL, subquery repetition, Schema Design Mini, Upsert & Transactions, and PostgreSQL Modeling/EXPLAIN.

Paused until the first analyst portfolio case is finished

JavaScript, TypeScript, n8n, Retool, PWA, AppSheet, DevOps, algorithms, OOP, game theory, CS50, dbt, DuckDB, and Polars.

Optional Python fallback

fCC Python tasks #1311-#1315 are supplements, not another mandatory course. Use them only when the CSV profiler or pandas work exposes a specific gap.

Interview detours

The Anti-Fraud route becomes current only for a real interview opportunity. It does not interrupt the Data Analyst route by default.

After the first portfolio case

Add a compact statistics and experiment-analysis phase, then rebuild the same Olist case with DuckDB and dbt. That is the point where analytics engineering starts helping instead of distracting from the analyst baseline.