Did the summer promotions pay?
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.
Level 1: Newcomer
0 points
Sign in to save your progress across devices.
Learn to write requirements and user stories and map a process, analyze it in Excel and SQL, track the work in Jira, show the result in Power BI and structure a business problem. Every exercise is checked, and the pathway ends in projects, a timed assessment across the tools and the interview.
About 68 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.
The core of the job. You find the need behind a request, work out who it affects, ask good questions, write requirements and user stories with acceptance criteria, draw BPMN process maps, find the gaps between today's process and the new one, prioritize the work and plan the user acceptance tests.
Turn a documented requirement into a canvas app with live formulas, a filtered gallery and a validated form. Check the saved record and test a known match beyond a connector row limit before accepting the prototype.
Business analysts test ideas in a spreadsheet before anyone builds anything. You write formulas with the right references, IF logic, conditional totals and lookups, keep data in tables, summarize it in PivotTables and highlight what matters with visual reporting.
The process you are studying leaves records in a database. With SQL you count, filter and join them yourself: how many orders waited more than a day, which depot handles the exceptions, where the handoffs stall.
Your findings turn into work for a team. You create and organize work items, follow workflows and transitions, search with JQL, run Scrum and Kanban boards, plan sprints and build the filters and dashboards a team checks every morning.
Stakeholders need to see the before and after. You build a report on a data model, slice and filter it, clean the source data and write the first DAX measures.
A business analyst is often handed a vague question. The case units teach you to break it into parts, read an exhibit, do the arithmetic and finish with a recommendation someone can act on.
Turn findings into an answer-first PowerPoint storyline, keep source links available and prepare a review deck that separates observations from recommendations.
Build structured Word reports with headings, sections and an automatic table of contents. Review changes and comments before handing the document to its owner.
Set the audience and roles for a Google document or slide deck, suggest and review changes, name a version and refresh a chart from its Sheets source before handing it over.
Practice ticket identity, shared views and event-driven rules on original support requests. Check the saved conversation and excluded records before recommending a workflow change.
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.
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.
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.
Demo requests from the Central region have gone quiet since August. Fix the Salesforce rule that sends them to a rep who left, build the flow that tells each owner about a new lead, and report conversion by owner in Excel.
Ashgrove has won eight weeks of bridge inspections. Find who can really take the work in the resource planner, after leave, part-time hours and other jobs, then show everyone's load in Excel and tell operations whether to hire.
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.
When you finish the units, test yourself across the tools of the job at once: 12 practical tasks in 50 minutes, each in the tool it is about and checked automatically. The clock keeps running if you close the page.
| Tool | Tasks | Minutes |
|---|---|---|
| Excel | 3 | 10 |
| SQL | 3 | 11 |
| Jira | 3 | 14 |
| Power BI | 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 business analyst 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 business analyst finds out how work really gets done, where it goes wrong and what should change. They sit with the people doing the work, measure the process from its data, write requirements and acceptance criteria a team can build from, and check after the change that it helped. The title covers many jobs, from operations to IT systems, but the core is the same: a clear problem, evidence, and a change someone can deliver.
Excel comes first because it is where most analysis starts and ends. SQL follows, so you can get the evidence yourself. Jira is where requirements become work. Power BI shows the result. The case units come last, because by then you have the tools to answer a business question and only need the structure.
The projects are operations work at fictional companies. At Ashgrove Engineering you find who can really take eight weeks of new inspections, then tell operations whether to hire. At Quillfield you fix the Salesforce rule that sent demo requests to a rep who left. At Hearthline you explain why profit fell while sales rose. Each ends in a written recommendation, which is what a business analyst hands over. The assessment then shows which tool to practice before you apply.
Support operations in Zendesk. Practice ticket identity, shared views and event-driven rules on original support requests. Check the saved conversation and excluded records before recommending a workflow change.
There is a lot of overlap. A data analyst mostly answers questions with data; a business analyst also studies how work gets done and writes the requirements for changing it. That is why this pathway adds Jira and case structuring, and the data analyst pathway adds Python instead.
Fewer than an engineer, more than many people expect. Most job ads ask for Excel, and many ask for SQL and a reporting tool. You don't need to program, but you need to understand the data well enough to question it.
The lessons on this pathway add up to about 68 hours. Each unit ends in a practice set on fresh data. 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.