Two dashboards, two on-time numbers
Operations reports one on-time rate and finance reports a lower one, for the same month. Find out why, write the measure both teams agree on, and recommend which number goes to customers.
Level 1: Newcomer
0 points
Sign in to save your progress across devices.
Learn to query and shape data, model it for reporting, write the measures behind a dashboard and build reports people trust, in Power BI and in Tableau. Every exercise is checked, and the pathway ends in dashboard projects, a timed assessment across the tools and the interview.
About 47 hours of lessons, from the estimate on each lesson.
Nothing done yet. Progress saves in this browser as you finish lessons, and in your account when you sign in.
Take the steps in this order. Each step is a set of units from one course, not the whole course: the units this role uses. Open a unit to start its first lesson.
A BI developer gets data out of the warehouse before anything reaches a chart. You query, summarize and join tables, use functions, window functions and the models analytics teams report from.
Source data rarely arrives ready. You learn the editor and its applied steps, clean and type columns, add calculated columns, reshape and combine queries, so the report refreshes on its own next month.
This is the core of the job in many companies. You go from a first report to a data model with relationships, DAX measures and CALCULATE, time intelligence, advanced modeling, interactive reports, row-level security, performance and publishing.
Many teams use Tableau instead, and some use both. You build views with the Marks card, write calculated fields and table calculations, use parameters and sets, design dashboards and work with level of detail expressions.
Build reusable warehouse fields and measures, test join grain and save a dashboard definition. Use access filters for regional restrictions and check the source totals before sharing.
Each project starts from a fictional company's brief and moves between tools the way the job does: what you build in one stage is where the next one starts. Every brief is free to read.
Operations reports one on-time rate and finance reports a lower one, for the same month. Find out why, write the measure both teams agree on, and recommend which number goes to customers.
Store managers say shelves keep running empty, but the shelf checks are messy. Mark every check, compare the stores fairly and show availability next to how much was checked.
Marketing ran eight promotions this summer and wants to plan the fall. Turn the offers into numbers, measure each one against the weeks before it, total the extra sales and write the memo.
Copperline's on-time report is a spreadsheet someone rebuilds every Monday. Rebuild it on the warehouse: one current row per shipment in Snowflake, a tested dbt model, and a Tableau view operations can trust.
Your first week as Hearthline's data analyst. Turn a messy order export into gross profit in Excel, roll it up in SQL, measure what each discount code costs in pandas, chart the margin in Power BI and tell your manager what to change.
When you finish the units, test yourself across the tools of the job at once: 15 practical tasks in 65 minutes, each in the tool it is about and checked automatically. The clock keeps running if you close the page.
| Tool | Tasks | Minutes |
|---|---|---|
| Looker and LookML | 3 | 11 |
| SQL | 3 | 11 |
| Power Query | 3 | 11 |
| Power BI | 3 | 15 |
| Tableau | 3 | 15 |
The assessment is free. The result is practice feedback in the Interview Hub's report format, not a hiring decision. Retakes draw different tasks where the question pools allow.
The Interview Hub runs the bI developer interview round by round, at a fictional employer: you answer out loud or in writing, the interviewer follows up, and the report quotes your answers.
A BI developer builds the reports and dashboards a company runs on, and the data models underneath them. They agree on what a measure means, write it once so every report shows the same number, control who sees which rows, and keep reports fast as the data grows. When two dashboards disagree, they are the person who finds out why.
SQL comes first because every report starts with data you can query. Power Query prepares that data so refreshes are automatic. Power BI is the longest step, from a first chart to security and publishing. Tableau comes last, so you can work in either tool.
At Copperline, operations and finance report two different on-time rates for the same month. You find out why, write the measure both teams agree on and recommend which number goes to customers. At Greenbasket you show shelf availability fairly across stores in Tableau. Each is a story about a number people trust again, which is what BI interviews look for. The assessment then shows which tool to practice before you apply.
They overlap. A data analyst answers questions; a BI developer builds and maintains the models and reports many people use to answer their own. That is why this pathway goes deeper into Power BI modeling, security and publishing than the data analyst pathway.
Read the ads for the jobs you want: they usually name one. This pathway covers both because the ideas carry over and many employers list either. If you know which one you need, take its units first.
The lessons on this pathway add up to about 47 hours. The Power BI step is the longest on purpose. We don't promise how long getting hired takes.
The first unit of every course is free, with no account. One Course opens one course in full; All Access opens the whole pathway. The pricing page shows every plan and its price.