When an interviewer asks about your experience with reporting and dashboards, a list of software is the weakest possible answer. They already know from your CV whether you have used Excel, Power BI, Tableau or Looker Studio. What they want to hear is whether your reports were accurate, whether the right people used them, and whether anything changed as a result.
Because the reporting experience interview question comes up in roles from administration to analytics, this article works through four common situations, with an illustrative answer for each and a note on why it works. Pick the scenario closest to your own experience and adapt it with real details.
Get the vocabulary right first
People use “report” and “dashboard” loosely, but some interviewers will notice if you mix them up. Microsoft’s Power BI documentation draws a clear line: a dashboard is a single page, often called a canvas, that shows the highlights of a story through tiles, while a report can run to one or more pages and supports filtering, highlighting and slicing. In Power BI, a dashboard can pull tiles from several reports and semantic models, and alerts can be set on some dashboard tiles. Those alerts are personal: according to Microsoft, only the person who sets an alert sees it, even on a shared dashboard, and alerts work only on cards, KPIs and gauges.
Other tools use the terms slightly differently, so mirror the language in the job advert. If it says “build and maintain dashboards”, describe your summary views as dashboards; if it says “management reporting”, lead with the regular reports you produced.
A simple frame for any reporting answer
- Audience and decision: who used it and what they decided with it.
- Data: where the numbers came from and how often they refreshed.
- Design: one or two choices you made for that audience.
- Result: time saved, an error caught, a decision made earlier.
Each scenario below follows this frame, in a different order to suit the story.
Scenario 1: You produce a regular report in Excel
This is the most common situation for administrators, coordinators and operations staff, and it is a perfectly good example if you describe it properly.
Illustrative answer: “Every Monday I produced the weekly operations report for our facilities manager: maintenance requests opened and closed, overdue jobs by contractor, and spend against the monthly allowance. The data came from two exports, our helpdesk system and the purchasing system, which I combined in Excel using lookups. When I took it over, it was a 12-tab workbook and the manager told me he only read the first page. I rebuilt it so the first page showed the five numbers he used in his Monday meeting, with the detail behind them on separate tabs. Preparation time went from most of a morning to about an hour, and he started using the overdue-jobs table to chase contractors the same day.”
Why it works: it names the reader and his decision, shows the data sources, and explains a design change made for that reader. The result is practical rather than dramatic, which makes it believable.
Scenario 2: You built a dashboard in a BI tool
For analyst, marketing and sales operations roles, interviewers will probe the build itself. Be ready to explain both the data model and the design.
Illustrative answer: “I built a Power BI sales dashboard for six regional managers. Before starting, I asked each of them which three numbers they checked first thing on a Monday, and the overlap was revenue against target, pipeline for the next 30 days and conversion rate. Those went across the top as headline figures, with a regional trend chart below and a table of open deals they could filter by account manager. The data came from our CRM through a scheduled refresh each morning. I also pinned each region’s target card to the dashboard and showed the managers how to set their own data alert on it, so they were notified if their region fell below 90% of target. Within a quarter, the managers had stopped requesting the separate spreadsheets they used to ask me for.”
Why it works: the candidate started from the users’ questions, not from the data available. That matches Tableau’s own guidance, which says the best visualisations have a clear purpose and work for their intended audience, and recommends placing the most important view in the upper-left area where viewers start reading. Tableau also suggests limiting a dashboard to two or three views and creating additional dashboards if the story needs more.
Scenario 3: You found that a report was wrong
Data quality stories are some of the strongest answers to this question, because they show judgement as well as technical skill.
Illustrative answer: “In my second month as an HR coordinator, I noticed our monthly headcount report didn’t match the figure finance used for payroll. The gap was about 20 people. I traced it to leavers whose final working day had passed but who were still active in the HR system because exit paperwork hadn’t been completed. I didn’t change the report on my own; I showed my manager the list, agreed a definition of ‘current employee’ with finance, and added a check that flagged anyone past their final day. After that, both reports matched each month, and the leavers’ backlog itself was cleared because it was now visible.”
Why it works: it shows curiosity, care with definitions and the sense to involve the people who own the numbers. It also turns a reporting problem into a process improvement.
Scenario 4: You simplified a report nobody read
This is a useful example if your role was more about requirements and communication than building.
Illustrative answer: “Our customer service team had a monthly report with more than 40 metrics, and when I asked the department head what she used it for, she said she mainly looked at complaints and response times. I ran a short review with the three team leaders who also received it, and we agreed on eight measures, each linked to a decision someone actually made. I moved the rest into an appendix that anyone could request. Feedback in the next quarterly review was that the report was finally being discussed in meetings rather than just circulated.”
Why it works: the candidate measured value by use, not by volume, and involved the readers in the decision. It is also a good answer for candidates who did not build the original report.
If you are early in your career
Coursework, a dissertation or a volunteer role can give you a usable example: a dashboard of survey results for a student society, or a tracker you built for a part-time job. Apply the same frame and be honest about the scale. A small dashboard someone used every week is a better story than an ambitious one nobody opened.
Follow-up questions to expect
“How did you choose your chart types?”
Give a reason tied to the data: a line chart for change over time, a bar chart for comparing categories, a table where readers need exact figures. You can add a detail that shows care, such as starting bar chart axes at zero. The ONS data visualisation guidance says bar and area chart axes should always start at zero, while line charts and scatter plots may use a cropped axis if needed.
“How did you know people were using it?”
Mention usage statistics if your tool provided them, or describe what you saw: questions you no longer received, the report being referred to in meetings, a manager acting on a figure from it.
“What happens when someone asks for one more metric?”
Explain that you ask what decision the metric supports and who else needs it. If it belongs on the page, add it; if not, offer a separate view or a drill-through rather than crowding the main one.
“How did you make sure the numbers were right?”
Describe your checks: reconciling totals to the source system, comparing against last period, documenting definitions, and having someone else review a new report before it went out.
Put the same evidence on your CV
A CV bullet such as “Rebuilt weekly operations report around five key measures; cut preparation time from a morning to an hour” gives the interviewer a natural opening for this question. The data analyst resume builder and business analyst resume builder include examples of reporting achievements, and you can check how a reporting-heavy CV reads to screening software with the ATS resume score checker.
Frequently asked questions
Do I need Power BI or Tableau experience to answer this question well?
No. A well-run Excel report that people relied on is a valid example. Explain who used it, what decision it supported and how you kept it accurate, then mention any BI tools you have learned.
How do I talk about dashboards I cannot show for confidentiality reasons?
Describe the structure instead: the audience, the main metrics, how often it refreshed and what changed because of it. If you have a portfolio, build a version with public or invented data that shows the same design choices.
What if the dashboard I built was not used much?
That can still be a good answer if you explain what you learned, for example that you built it before agreeing which decisions it should support, and what you did differently next time.
Which reports you have built should I mention first?
Lead with the one that had the clearest effect on a decision or saved the most time. Mention others in a sentence if the interviewer asks for more.
Sources
- Introduction to dashboards for Power BI designers, Microsoft Learn
- Set data alerts in the Power BI service, Microsoft Learn
- Best Practices for Effective Dashboards, Tableau Help
- Axes and gridlines, Office for National Statistics (ONS) Service Manual