Interview questions
Data analyst interview questions
Analyst interviews check two things: can you get the right number out of messy data, and can you explain what it means to someone who does not read SQL. Expect a technical test and at least one open-ended metric question.
Questions by stage and what a strong answer includes
- 01
What tools do you use daily?
Strong answer: SQL dialect and warehouse (BigQuery, Snowflake, Postgres), BI tool (Tableau, Looker, Power BI), spreadsheets, and Python or R if you use them. Be honest about level; it will be tested.
- 02
Who were the main consumers of your analysis?
Strong answer: Teams and seniority: marketing managers, ops leads, executives. It tells the recruiter whether you have translated numbers into decisions.
- 03
Tell me about an analysis that changed a decision.
Strong answer: The question, the data, what you found that people did not expect, and what the business did differently. The decision is the point, not the query.
- 04
Describe a time your numbers were wrong.
Strong answer: How the error happened, how it was caught, how you told stakeholders and what check you added afterwards. Owning data quality builds trust.
- 05
Write a query: monthly active users and their 30-day retention by signup month.
Strong answer: Clean CTEs, correct date handling, distinct counts, a left join so cohorts with zero retained users still show. Explain your assumptions as you write.
- 06
Conversion dropped from 3.1% to 2.6% overnight. How do you investigate?
Strong answer: Rule out tracking or deploy issues, check traffic mix, segment by device, channel and country, find where in the funnel it broke, then confirm with whoever owns that step.
- 07
How would you explain a confidence interval or an A/B test result to a non-technical manager?
Strong answer: Plain language, a range rather than a single number, what the result means for the decision, and whether the test ran long enough. No jargon wall.
- 08
A stakeholder asks for a dashboard with 30 metrics. What do you do?
Strong answer: Ask what decisions it should support, agree on a few core metrics with clear definitions, and keep the rest as drill-downs. Fewer metrics, more trust.
- 09
Present your take-home: what did you find and what would you recommend?
Strong answer: Start with the answer, support it with two or three charts, state limitations and next steps. Keep code out of the slides unless they ask.
- 10
How do you decide what to work on when you get more requests than you can handle?
Strong answer: Impact on decisions, effort, deadlines, and a visible queue agreed with your manager. Self-serve dashboards for repeated questions.
- 11
What kind of growth are you looking for in this role?
Strong answer: A direction: deeper statistics and experimentation, analytics engineering, or moving toward product analytics. Ties your salary conversation to scope.
One answer, before and after
Tell me about an analysis that changed a decision.
Weak answer
I did a lot of analysis for the marketing team and they used my dashboards to make decisions. One time I found something interesting in the data and they changed their strategy.
Strong answer in STAR
- Situation
- Marketing at an online furniture retailer planned to double paid social spend because its last-click reports showed the lowest cost per order.
- Task
- My manager asked me to check whether those orders were really incremental before the budget was approved in two weeks.
- Action
- I matched orders to customer histories and found that 40% of paid social orders came from returning customers who already had an abandoned cart. I then set up a two-week geo holdout with the marketing lead, pausing ads in three comparable regions.
- Result
- Incremental orders from paid social were about half what the reports claimed. The team raised the budget by 15% instead of 100% and moved the rest into search, saving roughly $60,000 that quarter.
Why it works
The weak answer has no question, no method and no decision. The strong one shows skepticism about the default metric, a clean test and a decision with a money figure. These numbers are illustrative, so use your own.
How a practice session works
- 01
Pick a stage, paste the job posting
Recruiter screen, HR interview, hiring manager, final round or offer talk. Add the posting and your resume so the questions are about your role, not generic.
- 02
Talk it through by voice
The interviewer speaks the language you chose, interrupts, follows up and digs into details like on a real call. If the connection drops, you pick up where you stopped.
- 03
Get the review and drills
A score, 7 skills, what you said next to a stronger way to say it, plus pace, filler words and talk share. Weak spots turn into short drills.