On this page
Questions to practise
Tell me about a dashboard or analysis you built.
They want to see real work and understand your skills through one clear example.
Choose one project. Say the question, the data, what you built, and who used it. Finish with what changed: 'The team used it to plan stock each week.' If you do not know the result, say what the users did with it.
What did you do yourself on that project?
Many projects are team work. They want to know your own part.
Use 'I' for your work and 'we' for team work. Be honest. Name your tasks clearly: 'I cleaned the data and built the charts. My colleague wrote the database queries.'
Tell me about the messiest data you worked with. How did you fix it?
Real data is often messy. They want to see your careful steps.
Name one real problem, like mixed date formats or missing values. Then give your steps: how you found it, how you checked it, and how you fixed or explained it.
How would you explain that result to a sales manager?
Analysts must talk clearly to people outside the data team.
Use everyday words. Give one number and say what it means. For example: 'Sales fell ten percent in March, mostly in one region. So we changed the delivery days.'
Which tools do you use, and what for?
They want to know your real skills, not just a list of names.
Name each tool and give a short example of how you used it. Be honest about your level. For example: 'I used a database for the main data and a spreadsheet for checks.'
What do you do when data is missing?
Missing data can change results. They want to see good judgement.
Explain your steps: check how much is missing, look for the reason, then decide what to do. Say you tell people about it, so they understand the limits of the result.
How do you check that your numbers are correct?
Wrong numbers can lead to bad decisions. They want to see that you work carefully.
Give real checks you use: compare totals with another source, test small samples, ask a colleague to review. One short example makes your answer stronger.
Tell me about a result that surprised you.
They want to see curiosity and how you react when data says something unexpected.
Describe the surprise, how you checked it was real, and what the team did next. Show that you checked the data before you shared the result.
How do you decide what to show on a dashboard?
Good dashboards are simple and useful. They want to see you think about the users.
Say you start with the users' main questions. Explain how you keep only the key numbers and use clear charts. Mention asking users for feedback and making changes.
Do you have any questions for me?
Good questions show interest in the team and the work.
Prepare two questions. For example: 'What data does the team use most?' or 'Who will use my reports?' Listen to the answer and say thank you.
Let me think of a good example.
Clara
AI coach
Leo
AI coach
Lines to try
Let me think of a good example.
In simple words, the main result was this.
My own part was cleaning the data and building the charts.
I used a database for the main data and a spreadsheet for checks.
Before I shared the result, I checked it in two ways.
Could you repeat the question, please?
Common questions
What if my best example is from a course, not a job?
That is fine. Say clearly that it was a course or personal project. Then describe it like work: the question, the data, what you built, and what you learned. A real, honest example is better than general talk.
What if I don't know a tool the interviewer asks about?
Be honest. Say you have not used it yet. Then name a similar tool you know and how you used it. You can add: 'I learn new tools quickly, and I can start with the basics.' Only say this if it is true.
How long should my answers be?
Try about one to two minutes. Give one example with clear steps and a result. If they want more, they will ask. It is okay to pause and say, 'Let me think of a good example.'