Managerial round questions for data analysts, with answers

Workload and prioritisation

1. "Three people ask for reports on the same day, each saying it's urgent. What do you do?"

I'd ask each of them two things: what decision the report feeds, and when that decision is made. That usually separates a board-meeting deadline from a nice-to-have. If two are still genuinely urgent, I'd bring them to you with an estimate for each and ask you to set the order, rather than deciding between two senior people myself. While waiting, I'd start whichever needs the longest data pull.

Listening for: questions about decisions and deadlines, estimates, and knowing when a priority call belongs to the manager.

2. "How long would a new weekly sales dashboard take you?"

It depends on three unknowns, so I'd give a range and the assumptions: if the data is already in one table and the metrics are agreed, two to three days for a first version; if definitions need agreeing across teams, add a week for that alone. I'd share a rough version on day two so the stakeholder can react before I polish anything.

Listening for: ranges with assumptions, not a single confident number, and early drafts.

3. "What would you do in your first 30 days here?"

Week one: understand the three or four reports people rely on most, who uses them and for which decisions. Weeks two and three: rebuild one of them myself from raw data to learn the tables and find where numbers come from, and note any definitions that differ between teams. By day 30: deliver one small improvement someone asked for, and a short list of data-quality issues I'd found, with a suggestion for which to fix first.

Listening for: learning before changing, and a concrete early deliverable.

Judgement and pushback

4. "A senior leader asks you for a chart that you think will mislead. What do you do?"

I'd make the chart they asked for and a version that shows the same data without the problem — say, a full axis instead of a truncated one, or the base size next to a percentage — and explain in one sentence why I'd suggest the second. It's their decision, but they should make it knowing the risk.

Listening for: respect for the stakeholder combined with a clear professional opinion.

5. "Someone asks you to exclude a region so the numbers look better for a review. What do you do?"

I wouldn't quietly exclude it. If there's a legitimate reason — for example, the region launched mid-quarter and isn't comparable — I'd exclude it and label it clearly with the reason. If the only reason is how it looks, I'd say I'm not comfortable presenting it that way and raise it with you. A number that's been shaped once is never trusted again.

Listening for: integrity without drama. This is often the question that decides the round.

6. "Your analysis contradicts what the business head believes. How do you present it?"

I'd check my work first, including asking someone to review the logic, because a surprising result is more likely to be a mistake. Then I'd present it to them privately before any group meeting, lead with the finding and the evidence, acknowledge what the data can't tell us, and ask what they are seeing that I might not be. Sometimes their experience explains the gap.

Listening for: self-checking, no public ambush, and openness.

Communication

7. "Explain a median to someone in sales who has never heard the word."

"Line up all our customers by how much they spent. The median is the person exactly in the middle. We use it because a few very large orders can make the average look higher than what a normal customer spends."

Listening for: plain language and a reason the concept matters.

8. "How do you write an email with an analysis result?"

Lead with the answer and the recommended action in the first two lines, then the two or three numbers that support it, then limitations, then a link to the detail. The reader should be able to stop after the first paragraph and still act correctly.

Working style

9. "What do you do when you're stuck on a problem for a few hours?"

Write down what I've tried and what I expected, which often shows the mistake. If I'm still stuck, I'll ask a colleague with a specific question rather than "it isn't working". I set myself a time limit — if something small blocks me for more than about half a day, I tell you, because it may affect a deadline.

10. "Speed or accuracy?"

It depends on the use. A rough number for an internal brainstorm can be quick and labelled "estimate". Anything that goes to a customer, finance or leadership gets the full checks. The mistake is sending a quick number without saying it's rough.

11. "How do you handle repeated last-minute requests?"

Do the urgent one, then look at the pattern. If the same report is requested every Friday at 5 PM, automate or schedule it, and talk to the requester about what triggers the rush. Repeated emergencies are usually a process problem.

12. "Why do you want to work in this team specifically?"

Answer with something you have actually found out: the products the team supports, the kind of analysis mentioned in the job description, something you noticed on the company's public site. Connect it to one piece of your own experience. Avoid generic answers about growth and learning; the manager hears them in every interview.

Questions to ask the manager back

Close with one or two questions that show you are thinking about the work: "Which report or analysis does the team spend the most time maintaining?" and "How would you judge whether I'm doing well at the end of three months?" For more, see questions to ask the interviewer.

Stakeholder handling and written summaries are practised alongside SQL and Power BI in the Data Analyst programme, and the behavioural STAR bank covers the story-based questions that often come in the same round.