SQL, grain, BI
Data Analyst
SQL you can defend, a metric someone will argue with, and a BI-shaped interview loop.
Dinesh Chandra writes from production Snowflake, Databricks, and Airflow work. The same warehouse shows up in analyst, engineer, scientist, and ML interviews. Pick your role on DataLane first. Then follow the five steps.
SQL, grain, BI
SQL you can defend, a metric someone will argue with, and a BI-shaped interview loop.
Dashboards, grain, warehouse
Warehouse SQL at dashboard grain. Windows, ranking, and a refresh that does not lie.
dbt, tests, metrics
Mart SQL, tests that page someone, and a metric finance can trust.
Pipelines, warehouses, on-call
SQL, orchestration, streaming, and the platform sketch they ask at 3pm.
SQL, stats, experiments
SQL for features, stats without vibes, and a holdout you would defend.
Train, serve, rollback
Features as tables. Latency as an SLA. Metrics you can put in CI.
Gates, serving, incidents
The SQL that proves training and serving agree, then the gate that blocks a bad model.
RAG, eval, retrieval
Retrieval is a pipeline. Eval is a job. The model brand is not the incident.
Grain, cost, paved roads
You still have to query the mart you designed. Quality SQL and a time you said no.
Follow this proven sequence from foundation to interview offer.
Analyst, BI, analytics engineer, data engineer, scientist, ML, MLOps, AI engineer, or architect. Open that flowchart, then the coding pads and interview track for the same role.
Windows, grain, and anti-joins. Analysts, engineers, and scientists all sit this pad. Filter the problem list by your role, then read the window guide.
NumPy, plain Python, or PyTorch on the same problem. Scientists and ML engineers live here; analysts and DEs still get asked means, joins-in-code, and metrics.
Snowflake credits and Query Profile before Cortex. If you live on Databricks, start with Delta instead. BI roles: still learn who pays for the extract.
Open the track for your role, run the coding labs, then sit a practice exam if your loop uses one.