Data Analyst hiring guide: screen, interview, score
Data analysts turn business questions into clean analysis, useful reporting, and decision-ready insights.
Copy the pieces you need and keep moving
Grab the checklist, questions, or scorecard for your ATS, doc, or interview panel.
What to look for before you start interviewing
Hire when teams need reliable dashboards, cleaner metric definitions, sharper analysis, and faster answers from data.
Strong candidates usually show
- Clear examples of using SQL, spreadsheets, BI tools, or Python/R to answer business questions.
- Strong data-quality instincts and comfort explaining assumptions, caveats, and tradeoffs.
- Evidence of turning analysis into decisions, not only producing charts or reports.
Scorecard preview
Full scorecardUse this before spending interview time
A crisp resume screen should separate must-have evidence from nice-to-have signals and red flags.
Must-have signals
- Hands-on experience querying, cleaning, analyzing, and presenting data.
- Comfort with SQL, spreadsheets, BI tools, and metric definitions.
- Examples of analysis that influenced a business, product, revenue, or operations decision.
- Clear communication of assumptions, limitations, and recommended next steps.
Nice-to-have signals
- Experience with Python, R, dbt, data warehouses, experimentation, or product analytics.
- Domain experience in SaaS, marketplace, finance, operations, marketing, or HR analytics.
- Experience building dashboards, automated reports, or self-serve analytics systems.
Resume red flags
- Lists tools without explaining business questions answered or decisions influenced.
- No evidence of data cleaning, validation, or metric-definition work.
- Creates charts but cannot explain interpretation, caveats, or actionability.
Best questions to validate the resume signal
Ask the same core questions to every candidate so the debrief has comparable evidence.
- 01
Walk me through an analysis you did that changed a decision.
Strong answer signal: Explains question, data, method, caveats, recommendation, and outcome.
Watch out for: Describes a dashboard but not the decision it supported.
- 02
How do you check whether a dataset is trustworthy?
Strong answer signal: Mentions missing values, duplicates, joins, outliers, definitions, and source checks.
Watch out for: Trusts exported data without validation.
- 03
Write the steps you would take to investigate a drop in weekly signups.
Strong answer signal: Segments by channel, geography, device, funnel stage, and time window.
Watch out for: Jumps to one explanation without structured diagnosis.
- 04
How do you define a metric when stakeholders disagree?
Strong answer signal: Clarifies business use, numerator, denominator, exclusions, and owner.
Watch out for: Picks a definition without aligning decision context.
- 05
Tell me about a dashboard you built. How did you decide what belonged on it?
Strong answer signal: Ties dashboard fields to users, decisions, cadence, and guardrails.
Watch out for: Adds every available metric without prioritization.
- 06
How would you explain a technical analysis to a non-technical stakeholder?
Strong answer signal: Starts with answer, explains evidence, caveats, and business implication.
Watch out for: Overloads the stakeholder with methodology before the answer.
- 07
Describe a time your first analysis was wrong or incomplete.
Strong answer signal: Shows validation, correction, transparency, and process improvement.
Watch out for: Cannot name an example or hides uncertainty.
- 08
What makes a good SQL query or spreadsheet model maintainable?
Strong answer signal: Mentions clear naming, comments, tests/checks, modular logic, and reproducibility.
Watch out for: Optimizes only for quick one-off output.
Score candidates on the criteria that actually matter
Use this scorecard to compare data analyst candidates on decision-quality evidence, not tool lists alone.
| Criterion | Weight | What to assess |
|---|---|---|
| Analytical problem solving | 25% | Question framing, structured diagnosis, assumptions, and recommendation quality. |
| Technical data skills | 25% | SQL, spreadsheets, BI, data cleaning, joins, reproducibility, and tool fit. |
| Data quality and metric judgment | 20% | Validation, metric definitions, caveats, source checks, and interpretation discipline. |
| Business communication | 20% | Clear storytelling, stakeholder alignment, answer-first communication, and actionability. |
| Ownership and learning | 10% | Follow-through, curiosity, documentation, and ability to improve analytics workflows. |
Run a short, evidence-based interview loop
Recommended interview loop
- Screen resumes for analysis impact, SQL/spreadsheet skills, and data-quality evidence.
- Run a recruiter or manager screen for communication, domain fit, and tool exposure.
- Use an analytics interview focused on problem framing and metric judgment.
- Give a realistic SQL, spreadsheet, or dashboard work sample.
- Run a stakeholder communication round using a short analysis presentation.
- Debrief with the same weighted scorecard.
Ask the candidate to analyze a small dataset, define key metrics, identify data-quality issues, and summarize recommendations.
- Time limit: 60–90 minutes live, or 2–3 hours take-home maximum.
- Problem framing and metric definitions.
- Data cleaning and validation approach.
- Accuracy of analysis and interpretation.
- Clarity of recommendation and caveats.
Clarify the role before you source
Align the role before posting
- Primary business area: product, revenue, marketing, operations, finance, or people analytics.
- Required tools: SQL, Excel/Sheets, BI tool, Python/R, warehouse, or analytics platform.
- Expected output: dashboards, ad hoc analysis, reporting, experimentation, or data cleanup.
- Metric ownership, stakeholder cadence, and decision-making context.
- Which decisions should this person help the team make faster?
- Which dashboards or metrics are currently unreliable or missing?
- What level of SQL, BI, spreadsheet, or Python skill is truly required from day one?
Adjust by role shape
- Product analyst: prioritize funnel analysis, retention, experimentation, and user behavior.
- Revenue analyst: prioritize pipeline, conversion, forecasting, pricing, and GTM metrics.
- Operations analyst: prioritize process metrics, capacity, cost, quality, and exception tracking.
- People analyst: prioritize hiring, retention, engagement, workforce planning, and privacy discipline.
Adjust the bar by level
- Junior: focus on SQL/spreadsheet fundamentals, accuracy, curiosity, and communication.
- Mid-level: focus on independent analysis ownership and stakeholder-ready recommendations.
- Senior: focus on metric strategy, ambiguous problem solving, systems thinking, and analytics leadership.
Avoid signals that create false confidence
Signals that look better than they are
- Tool-heavy resume without business impact or decision examples.
- Beautiful dashboards that do not clarify decisions or metric definitions.
- Advanced modeling claims without data-quality or stakeholder communication evidence.
What success should look like after hiring
30 days
- Understands key data sources, dashboards, metrics, and stakeholder questions.
- Completes small analyses with review and documents assumptions.
60 days
- Owns recurring reporting or a focused analysis area with clear definitions.
- Improves data quality checks, dashboard usability, or metric documentation.
90 days
- Delivers decision-ready analysis independently.
- Helps teams make faster decisions with clearer metrics and trusted reporting.
Use the guide, then generate the assets faster
These links are placed here as a compact toolkit, but the same tools are also embedded in the relevant sections above.
Free AI Resume Screening
Screen data analyst resumes against this checklist.
Free AI Rubric Generator
Generate a weighted analytics screening rubric.
Interview questions by role
Find more data analyst questions.
Free Hiring Analytics Spreadsheet
Track candidates and scores.
Free AI JD Generator
Create the data analyst JD before posting.
Common questions about hiring a data analyst
Turn this guide into a ranked data analyst shortlist
Upload resumes, screen against a role-specific rubric, and review evidence-backed candidate rankings in HireSort.
Start screening resumes