Interview questions · Data Analyst

Data Analyst interview questions

Recruiters hiring Data Analysts look for a blend of technical proficiency—SQL, Python, and data visualization tools—combined with strong business acumen and the ability to translate complex findings into actionable insights. They assess how candidates handle messy, real-world data, communicate with non-technical stakeholders, and drive decisions through evidence rather than intuition.

Walk me through how you would approach a new data analysis project from scratch.

Recruiters want to see if you have a structured, repeatable analytical framework rather than jumping straight into tools.

Model answerAt my last role, a product team asked me to investigate a 15% drop in user retention. I started by clarifying the business question and success metrics with stakeholders, then audited available data sources in our warehouse before writing SQL queries to segment users by cohort and behavior. By following this structured approach—define, collect, analyze, communicate—I identified that a recent onboarding change was causing drop-off, and the fix increased retention by 12% within two months.

Describe a time you worked with a large, messy dataset. How did you clean and validate it?

Recruiters need to know you can handle real-world data quality issues, not just clean textbook datasets.

Model answerI was handed a 4-million-row customer transactions table that had duplicate records, inconsistent date formats, and ~8% null values in key revenue fields. I used Python (pandas) to profile the data, wrote deduplication logic based on composite keys, imputed nulls using median values segmented by customer tier, and documented every transformation in a cleaning log. The resulting dataset reduced downstream reporting errors by 30% and became the single source of truth for the finance team.

Which SQL techniques do you use most often, and can you give a concrete example of a complex query you've written?

SQL is the core tool for most Data Analyst roles, and recruiters want to gauge your actual depth of knowledge beyond basic SELECT statements.

Model answerI rely heavily on window functions, CTEs, and subqueries. In one project, I needed to calculate a 30-day rolling average of daily revenue per sales region while excluding weekends. I used a CTE to generate a clean date spine, a LEFT JOIN to fill missing days with zeros, and a window function with a ROWS BETWEEN 29 PRECEDING AND CURRENT ROW clause. The query ran in under 10 seconds on 50 million rows and fed a live executive dashboard.

Tell me about a time you presented data findings to a non-technical audience. How did you make the insights accessible?

Recruiters want to confirm you can bridge the gap between raw data and business decision-making.

Model answerI had to present churn analysis results to our VP of Marketing, who had no analytics background. Instead of showing model coefficients, I built a Tableau dashboard with a single headline metric—'Every 1-point drop in NPS score correlates with a 2% increase in churn'—backed by a simple bar chart. I used plain business language throughout the presentation, and the VP immediately approved a $200K customer success initiative based on the findings.

How do you decide which visualization to use for a given dataset or business question?

Choosing the wrong chart type can mislead stakeholders, and recruiters want to see deliberate, audience-aware thinking.

Model answerWhen asked to show monthly subscription growth across five product lines, I considered a stacked bar chart but realized it would hide individual trends. I instead used a small-multiples line chart, which made it immediately clear that one product line had plateaued while another was growing 40% month-over-month. This choice led the strategy team to reallocate budget within one week of the presentation.

Describe a situation where your analysis led to a business decision that turned out to be wrong. What did you learn?

Recruiters test intellectual honesty, resilience, and your ability to learn from failure—key traits for analytical roles.

Model answerI recommended a price increase for a mid-tier subscription plan based on price-elasticity analysis that showed low sensitivity; however, I had not accounted for a competitor who launched a cheaper alternative the same week. Churn spiked 18% in the first month. I immediately built a competitive pricing tracker and added external market signals to my analytical checklist, which prevented similar blind spots in future recommendations.

How do you handle a situation where a stakeholder disagrees with your data findings?

Recruiters assess your ability to defend your work rigorously while remaining collaborative and open to new information.

Model answerA sales director once argued my analysis showing declining lead quality was flawed because it contradicted his team's experience. Rather than backing down, I walked him through my methodology step by step and invited him to share any data points I might have missed. He surfaced a regional campaign I hadn't factored in; I reran the analysis including that segment, which refined—but largely confirmed—my original conclusion, and we aligned on a joint action plan.

What metrics would you track to measure the health of an e-commerce business, and how would you prioritize them?

This tests domain knowledge and your ability to connect data points to business outcomes rather than reporting vanity metrics.

Model answerI would prioritize conversion rate, average order value, customer acquisition cost, and 90-day repeat purchase rate as core health metrics, since they directly map to revenue and profitability. I would also monitor cart abandonment rate as a leading indicator of friction. In a previous role, focusing on repeat purchase rate over raw traffic helped us identify that loyalty program members spent 3x more annually, shifting the marketing budget toward retention and increasing overall revenue by 22%.

How do you ensure the reproducibility and documentation of your analyses?

Recruiters want analysts who build trust and institutional knowledge, not siloed work that disappears when someone leaves.

Model answerI use version-controlled Jupyter notebooks or Python scripts stored in GitHub, with a README explaining the business question, data sources, and key assumptions. I also maintain a data dictionary for any derived metrics. When I introduced this practice at my last company, onboarding time for new analysts reviewing existing reports dropped from two days to half a day, and we eliminated three instances of conflicting metric definitions within the first quarter.

Tips for this role

Practise for THIS role

Paste your job offer, pick a recruiter, and run a mock interview with a detailed coaching report.

🎤 Start an interview

Everything you can do