Interview scorecard templates

Business Intelligence Analyst interview scorecard template

A BI analyst is only as useful as the dashboards people actually open. This scorecard covers dashboard design, SQL, data modeling, business understanding and stakeholder management.

Customize this scorecard

Free to use. Nothing you type on the scorecard is saved.

Interview scorecard

Business Intelligence Analyst

Score each skill from 1 to 5. A 1 is below the bar for this role, a 3 meets it, and a 5 is above it. The examples show what each sounds like. Use 2 and 4 for answers that fall in between.

Dashboard design

Builds dashboards that help a specific audience answer their key questions quickly and accurately.

Score for Dashboard design

Questions

  • Tell me about a dashboard you built. Who used it and what decisions did it support?
  • How do you decide which metrics and charts go on a dashboard?
  • Tell me about a dashboard people stopped using or misread. What did you change?

1: Below the bar

Starts with the data available, not the user's needs. Adds many charts and can't say why each is there.

3: Meets the bar

Asks who will use it and what they need. Picks sensible charts and fixes problems when users complain.

5: Above the bar

Defines decisions first, limits metrics to what matters, tests with real users, and tracks usage to improve it afterward.

SQL

Writes accurate, readable queries that answer business questions and checks the results before sharing them.

Score for SQL

Questions

  • Tell me about a complex query you wrote recently. What question did it answer?
  • Tell me about a time your query returned wrong numbers. How did you find out?
  • Tell me about a slow query you improved. What did you change?

1: Below the bar

Describes only simple queries. Doesn't check results and can't explain how joins or filters affect the numbers.

3: Meets the bar

Describes multi-table queries with joins and aggregation. Checks totals against a known source and fixes slow queries with some trial and error.

5: Above the bar

Explains complex queries clearly, validates results routinely, and diagnoses slow or wrong output by naming the specific cause.

Data modeling

Structures data into clear, reliable tables that answer business questions and stay accurate as needs change.

Score for Data modeling

Questions

  • Tell me about a data model you built. How did you decide its structure?
  • Tell me about a time a model gave wrong or confusing numbers. What caused it?
  • How have you changed a model when the business changed, without breaking reports?

1: Below the bar

Describes copying data into one big table. Can't explain why the structure was chosen or how errors were found.

3: Meets the bar

Explains a sensible structure and why, such as separating facts from descriptions. Fixes problems after they appear and notes some trade-offs.

5: Above the bar

Designs around the questions users ask, defines grain and keys up front, and adds checks. Plans changes so existing reports keep working.

Business understanding

Connects data work to how the company makes money and which decisions matter most.

Score for Business understanding

Questions

  • Tell me about a time you learned how a team's business works before analyzing its data.
  • Describe an analysis that changed a business decision. What question did you start with?
  • Tell me about a metric that looked good but hid a business problem.

1: Below the bar

Describes data tasks without naming the business goal. Reports numbers but can't say what decision they support.

3: Meets the bar

Links own analyses to a clear business goal. Asks basic questions about the business but relies on others for context.

5: Above the bar

Explains how the business earns money and ties each analysis to a decision. Challenges misleading metrics and suggests better ones.

Stakeholder management

Keeps stakeholders aligned by clarifying requests, setting expectations, and handling disagreement about data requests.

Score for Stakeholder management

Questions

  • Tell me about a time a stakeholder's request was vague. How did you clarify it?
  • Describe a time you had to say no or push back on a request.
  • Tell me about a time a stakeholder disagreed with your numbers. What did you do?

1: Below the bar

Takes requests as given or avoids conflict. Stakeholders learn about delays or problems late, or not from the candidate.

3: Meets the bar

Asks follow-up questions, sets rough timelines, and explains numbers calmly. Handles pushback but mostly reacts rather than anticipates.

5: Above the bar

Probes for the real need, agrees on timelines upfront, and updates people early. Turns disagreement into a shared decision.

Overall recommendation

Decide on your own, before you compare notes with the rest of the panel.

Overall recommendation

Use this scorecard in PontaHR

With PontaHR, your team fills out scorecards on the candidate's profile. Compare ratings and feedback side by side when it's time to decide.

See how scorecards work in PontaHR, then try it with a guided free trial.

More interview scorecard templates

Hiring for a different role? Make your own scorecard