Data Analyst Interview Prep

Across 62 companies' interview data, the skill that separates Data Analyst candidates who get offers from those who don't isn't SQL or Python. It's metric decomposition: the ability to take a number like "WAU dropped 8%," break it into cohort-level drivers, and recommend a specific action in under two minutes. Candidates who spend their prep time on ML theory and algorithm complexity instead of this skill are solving the wrong problem entirely.

What Data Analysts Actually Do

You'll find this role everywhere: FAANG product teams dissecting retention funnels, fintech startups tracking transaction fraud rates, retail companies optimizing inventory forecasts. The companies differ, but the core loop is the same: pull data in Snowflake or BigQuery, find the signal, convince someone to act on it. Success after year one means you own a metric area so thoroughly that stakeholders come to you before making decisions, not after.

A Typical Week

Writing and meetings together eat 36% of the week, more than analysis itself at 30%. Most candidates picture heads-down SQL all day, but you'll spend Thursday morning translating a Python significance test into a five-slide deck with plain-English takeaways for product leadership. The analyst who gets promoted isn't the one who writes the fastest window function; it's the one who can walk a game designer through a cohort retention chart in Looker and get a ship/no-ship decision before the meeting ends.

Skills & What's Expected

Machine learning won't come up in most DA interviews, but don't mistake that for the role being "easy mode." Interviewers want you to look at a Tableau dashboard showing a 12% WAU drop and immediately ask the right follow-up: is it seasonal, did a feature ship, is it concentrated in one geography or cohort? SQL proficiency (CTEs, window functions, self-joins) is non-negotiable at every level, and Python or R for data manipulation and reproducible analysis is expected from mid-level onward, not just at senior. Excel still shows up at finance-heavy shops and early-stage startups that haven't migrated off spreadsheets.

Levels & Career Growth

Most hiring clusters at entry and mid levels, where the promotion gap comes down to several concrete shifts: owning a metric area end-to-end, running your own A/B test power calculations, and writing analysis that PMs reference in roadmap reviews instead of filing away. Senior analysts define what to measure and mentor others on methodology. Staff and Principal titles are rare outside a handful of companies like Meta, Google, and Airbnb.

The IC-versus-management fork usually appears around the senior level. Many analysts pivot into analytics engineering, product management, or data science by year four or five, especially at companies where the senior IC ceiling feels low relative to those adjacent roles.

Data Analyst Compensation

The wide min-to-max bands you see above reflect real structural differences in how companies pay. From what candidates report, a 4-year RSU schedule is standard at large public tech firms, but the details matter: Amazon's back-loaded 5/15/40/40 vesting means your Year 1 take-home is dramatically lower than the headline number, while Meta and Google spread grants more evenly. Pre-IPO startups hand you options with a 1-year cliff that could expire worthless, so discount that equity heavily when comparing offers.

Signing bonuses and equity grants are almost always more negotiable than base salary. If you have a competing offer, say so explicitly. Recruiters at most mid-to-large companies have authority to bump RSU grants 10 to 20% to close a candidate, but they won't volunteer that room unprompted.

Refresh grants can quietly reshape your comp trajectory at senior levels and above. Strong performers at large public tech companies can expect annual refreshers running 20 to 30% of the initial grant, which compounds into a meaningful gap between staying and job-hopping every two years.

Data Analyst Interview Process

Four weeks is the typical timeline from recruiter call to offer, based on data aggregated from 54 companies. Big tech loops (Meta, Google, Amazon) often stretch to six or seven weeks because of hiring committee reviews and cross-team calibration. Startups and mid-market firms can compress to two weeks, though they rarely cut rounds so much as stack them into fewer days.

From what candidates report, the Hiring Manager Screen is where the most people quietly get cut. HMs want you to describe past impact with specifics ("I reduced churn by 3% after identifying a billing UX drop-off in a Tableau funnel dashboard"), and they screen out anyone who speaks only in generalities.

The behavioral round carries more weight than its final-round position suggests. By round six, the team has already scored your SQL and product sense. They're using STAR-formatted stories to judge whether you can defend a methodology to a skeptical VP or navigate conflicting priorities between, say, a PM who wants a launch metric and a finance lead who wants cost attribution, and candidates who prep five rehearsed stories (stakeholder pushback, ambiguous data, tight deadline, cross-team influence, a mistake you caught) consistently outperform those who wing it.

Data Analyst Interview Questions

SQL & Data Manipulation

Expect questions that force you to translate messy payments/product prompts into correct SQL under time pressure. You’ll be evaluated on joins, window functions, cohorting, and debugging logic to produce decision-ready tables.

For each listing, compute the trailing 28-day booking revenue, excluding the current day, and return the top 50 listings by that metric for yesterday. Bookings can be refunded, so use net revenue per booking.

AirbnbMediumWindow Functions and Time Windows

Sample Answer

Compute daily net revenue per listing, then sum it over the prior 28 days using a date-based window that excludes the current day. You avoid double counting by aggregating to listing-day before windowing, then filtering to yesterday at the end. Use $[d-28, d-1]$ as the window, not 28 rows, because missing days exist. Net revenue should incorporate refunds at the booking level before the listing-day rollup.

SQLCopy

1WITH booking_net AS (
2  SELECT
3    b.booking_id,
4    b.listing_id,
5    DATE(b.booking_ts) AS booking_day,
6    COALESCE(b.gross_amount_usd, 0) - COALESCE(b.refund_amount_usd, 0) AS net_amount_usd
7  FROM bookings b
8  WHERE b.status IN ('confirmed', 'completed', 'refunded')
9),
10listing_day AS (
11  SELECT
12    listing_id,
13    booking_day,
14    SUM(net_amount_usd) AS net_revenue_usd
15  FROM booking_net
16  GROUP BY 1, 2
17),
18scored AS (
19  SELECT
20    listing_id,
21    booking_day,
22    SUM(net_revenue_usd) OVER (
23      PARTITION BY listing_id
24      ORDER BY booking_day
25      RANGE BETWEEN INTERVAL '28' DAY PRECEDING AND INTERVAL '1' DAY PRECEDING
26    ) AS trailing_28d_net_revenue_excl_today_usd
27  FROM listing_day
28)
29SELECT
30  listing_id,
31  trailing_28d_net_revenue_excl_today_usd
32FROM scored
33WHERE booking_day = CURRENT_DATE - INTERVAL '1' DAY
34ORDER BY trailing_28d_net_revenue_excl_today_usd DESC NULLS LAST
35LIMIT 50;

You need host-level cancellation rate for the last 90 days, where the numerator is guest-initiated cancellations and the denominator is all bookings that reached confirmed status. Hosts can have multiple listings, and booking status changes are tracked in an events table with one row per status transition.

AirbnbHardEvent Log Deduping and Conditional Aggregation

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more SQL & Data Manipulation questions

Product Sense & Metrics

The bar here isn’t whether you know a metric name—it’s whether you can structure an analysis plan that maps to decisions. You’ll need to define success, identify leading vs lagging indicators, and anticipate confounders and data limitations.

How would you define and choose a North Star metric for a product?

EasyFundamentals

Sample Answer

A North Star metric is the single metric that best captures the core value your product delivers to users. For Spotify it might be minutes listened per user per week; for an e-commerce site it might be purchase frequency. To choose one: (1) identify what "success" means for users, not just the business, (2) make sure it's measurable and movable by the team, (3) confirm it correlates with long-term business outcomes like retention and revenue. Common mistakes: picking revenue directly (it's a lagging indicator), picking something too narrow (e.g., page views instead of engagement), or choosing a metric the team can't influence.

Outbound delivery speed for the company Logistics improved from 2.3 to 2.1 days, but CS contacts per 1,000 orders increased by 12% in the same period. You have order, shipment scan, and contact reason data, propose a metric framework to diagnose whether the speed win is causing the contact increase.

AmazonMediumMetric Decomposition and Customer Contacts

Sample Answer

You could do cohort decomposition by promised speed buckets or you could do contact rate standardization holding mix constant. Cohort decomposition wins here because it exposes which promise and ship-method segments changed behavior, and whether contacts spike specifically where speed improved. Standardization is faster but can hide operational failure modes like more partial shipments or missed promised windows. You want both eventually, but the cohort view answers causality-adjacent questions with fewer assumptions.

A company reduces the guest service fee by 1 percentage point in 5 countries, and Finance wants a metric tree that separates demand lift from margin impact and host behavior changes. Propose the primary success metric, the decomposition you would show (with formulas), and 2 guardrails that prevent gaming or long-run supply damage.

AirbnbHardMetric Tree and Unit Economics

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more Product Sense & Metrics questions

A/B Testing & Experiment Design

What is an A/B test and when would you use one?

EasyFundamentals

Sample Answer

An A/B test is a randomized controlled experiment where you split users into two groups: a control group that sees the current experience and a treatment group that sees a change. You use it when you want to measure the causal impact of a specific change on a metric (e.g., does a new checkout button increase conversion?). The key requirements are: a clear hypothesis, a measurable success metric, enough traffic for statistical power, and the ability to randomly assign users. A/B tests are the gold standard for product decisions because they isolate the effect of your change from other factors.

You run an experiment on the guest cancellation flow and randomize by user_id, but a guest can book multiple trips and see both variants across devices. How do you detect and quantify interference, and what changes to the design or analysis would you make?

AirbnbMediumSUTVA violations and unit of randomization

Sample Answer

Reason through it step by step as if thinking out loud. Start by checking exposure logs, does the same guest_id have multiple variant assignments across sessions or devices, and what share of traffic is affected. Next, quantify bias risk by comparing outcome rates for cross-exposed users versus clean users, and by re-estimating the lift on the clean subset to see how sensitive the result is. Then pick a fix: enforce sticky assignment at the guest_id level with consistent identity stitching, or move randomization to a higher level like booking_id if the treatment is per booking. If you cannot fix assignment, analyze with cluster-robust standard errors at the guest_id level, or switch to a design like switchback only if the interference is time-based rather than user-based.

A company runs 8 simultaneous experiments on the host pricing page, and your experiment shows $p = 0.03$ on booking conversion and $p = 0.20$ on contribution margin. How do you decide whether this is a real win, and what correction or validation would you apply?

AirbnbHardMultiple testing and ambiguous readouts

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more A/B Testing & Experiment Design questions

Statistics

Most candidates underestimate how much applied stats shows up in fraud analytics, from thresholding to false-positive tradeoffs. You’ll need to reason clearly about distributions, sampling bias, and how to validate signals with limited labels.

What is a confidence interval and how do you interpret one?

EasyFundamentals

Sample Answer

A 95% confidence interval is a range of values that, if you repeated the experiment many times, would contain the true population parameter 95% of the time. For example, if a survey gives a mean satisfaction score of 7.2 with a 95% CI of [6.8, 7.6], it means you're reasonably confident the true mean lies between 6.8 and 7.6. A common mistake is saying "there's a 95% probability the true value is in this interval" — the true value is fixed, it's the interval that varies across samples. Wider intervals indicate more uncertainty (small sample, high variance); narrower intervals indicate more precision.

A company Logistics changed a routing rule and late deliveries dropped from $2.4\%$ to $2.1\%$ over 14 days, but shipment volume also increased and the mix shifted toward longer-distance lanes. How do you estimate whether the routing change reduced late deliveries, and which statistical model or adjustment would you use?

AmazonMediumConfounding and Adjusted Comparisons

Sample Answer

Walk through the logic step by step as if thinking out loud. Start by defining the outcome as a binary label per shipment (late or not) and list the main confounders, lane distance, carrier, promised speed, weather, day-of-week, and volume. Then fit a logistic regression with a treatment indicator for the routing rule change plus those covariates (and ideally lane fixed effects) so you compare like with like. Validate by checking pre-change trends by lane, then report an adjusted lift with a CI, not just the raw $2.4\%$ to $2.1\%$ delta.

An AWS Console UI experiment shows a $+1.2\%$ lift in weekly active users, but the metric has heavy-tailed session counts and the variance doubled during the test. How do you decide whether to ship, and what statistical technique would you use to make the result decision-ready?

AmazonHardVariance, Heavy Tails, and Robust Inference

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more Statistics questions

Data Modeling

When you design tables for analytics, you’re being tested on grain, keys, and how modeling choices impact BI performance and correctness. Expect star schema reasoning, fact/dimension tradeoffs, and how you’d model common product/usage datasets.

An ETL job builds fct_support_interactions from Zendesk tickets, chat transcripts, and on-chain deposit events, and you notice a sudden 12% drop in interactions after a schema change in chat. What data quality checks and pipeline safeguards do you add so this does not silently ship to dashboards again?

CoinbaseMediumETL Monitoring, Data Quality

Sample Answer

Get this wrong in production and your CX dashboards underreport demand, staffing and SLA decisions get made on fake stability. The right call is to add volume and freshness checks (row count deltas by source, max event timestamp lag), completeness checks on required keys (ticket_id, interaction_id, user_id), and distribution checks on critical dimensions (channel, product surface). Gate the publish step with alerting and fail-closed thresholds, plus backfill logic and schema versioning so a renamed field cannot null out a join unnoticed.

A company wants a single "gross bookings" metric used by Finance and Product, but your model has cancellations, modifications, partial refunds, and multiple payment captures per reservation. How do you model facts and keys so that gross bookings, net bookings, and revenue can be computed without double counting across these flows?

AirbnbHardFact Modeling, Double Counting, Payments and Reservations

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more Data Modeling questions

Visualization

When dashboards become the source of truth, small choices in charting and narrative can change decisions. You’ll be tested on picking the right visual, communicating insights to non-technical stakeholders, and proposing actionable next steps.

A Tableau dashboard for the company Retail shows conversion rate by store, but the VP wants stores ranked and "actionable" by tomorrow. What is your default chart and sorting approach, and what adjustment do you make to avoid overreacting to small-sample stores?

AppleMediumRanking, Variability, and Visualization Choice

Sample Answer

The standard move is a ranked bar chart of conversion with a reference line for the fleet median, plus a small table for traffic and transactions. But here, sample size matters because $n$ varies wildly by store, so the ranking is mostly noise for low-traffic locations. You either filter to a minimum volume threshold or plot a funnel chart (conversion versus sessions) with confidence bands, then call out only statistically stable outliers for action.

You ship an exec dashboard for iOS crash rate by build, but a new build rollout causes an apparent crash-rate jump. How do you redesign the dashboard so leadership can tell whether the build is worse versus the user mix changing due to staged rollout?

AppleHardCohorting, Segmentation, and Narrative Design

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more Visualization questions

Data Pipelines & Engineering

In practice, you’ll be asked how you keep reporting accurate when pipelines break or definitions drift. Strong answers cover validation checks, anomaly detection, backfills, idempotency, and communicating data incidents to stakeholders.

What is the difference between a batch pipeline and a streaming pipeline, and when would you choose each?

EasyFundamentals

Sample Answer

Batch pipelines process data in scheduled chunks (e.g., hourly, daily ETL jobs). Streaming pipelines process data continuously as it arrives (e.g., Kafka + Flink). Choose batch when: latency tolerance is hours or days (daily reports, model retraining), data volumes are large but infrequent, and simplicity matters. Choose streaming when you need real-time or near-real-time results (fraud detection, live dashboards, recommendation updates). Most companies use both: streaming for time-sensitive operations and batch for heavy analytical workloads, model training, and historical backfills.

You need a trustworthy daily metric for App Store subscriptions that powers Finance reporting and product dashboards, and events can arrive up to 72 hours late. How do you design the warehouse tables and the incremental rebuild logic so the metric is both stable and correct?

AppleMediumLate Arriving Data and Incremental Loads

Sample Answer

Start with what the interviewer is really testing: "This question is checking whether you can keep a metric stable for stakeholders while still correcting for late data." You typically separate an immutable raw events layer from a curated fact layer keyed by a stable business grain (for example, subscription, day, storefront), and define a rolling recompute window of the last $N$ days where $N \ge 3$ to absorb late arrivals. You also need a clear definition of when the metric is final (for example, a watermark), plus audit columns like load_timestamp and source_max_event_time so you can explain changes and meet SLAs.

An Airflow DAG builds a daily fact table for payouts to hosts, partitioned by payout_date, and finance reports missing payouts for a two week window after a backfill. How do you design the backfill and data quality safeguards so you avoid double counting, preserve idempotency, and keep downstream Superset dashboards stable?

AirbnbHardBackfills, Idempotency, and Data Quality Gates

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more Data Pipelines & Engineering questions

Causal Inference

What is the difference between correlation and causation, and how do you establish causation?

EasyFundamentals

Sample Answer

Correlation means two variables move together; causation means one actually causes the other. Ice cream sales and drowning rates are correlated (both rise in summer) but one doesn't cause the other — temperature is the confounder. To establish causation: (1) run a randomized experiment (A/B test) which eliminates confounders by design, (2) when experiments aren't possible, use quasi-experimental methods like difference-in-differences, regression discontinuity, or instrumental variables, each of which relies on specific assumptions to approximate random assignment. The key question is always: what else could explain this relationship besides a direct causal effect?

Hulu ad load was reduced for a subset of DMAs, but advertisers also shifted budgets toward those same DMAs mid-flight due to a sports schedule. You need the causal effect of ad load reduction on ad revenue per hour, do you use a geo-based diff-in-diff or an instrumental variables approach, and why?

DisneyMediumGeo Experiments and Instrumental Variables

Sample Answer

You could do geo diff-in-diff or instrumental variables (IV). Geo diff-in-diff is simpler, but it loses credibility here because budget reallocation creates time-varying confounding correlated with treatment assignment. IV wins if you have a plausibly exogenous instrument for ad load, for example a policy or capacity constraint that shifts ad load but does not directly shift demand, then you estimate $\text{AdLoad}\rightarrow\text{RevenuePerHour}$ via 2SLS and defend exclusion and relevance.

A company runs a retargeting campaign for the company+ lapsed subscribers, but exposure is highly selective because it targets users with high predicted return probability. How do you design a quasi-experiment to estimate incremental resubscription lift, and what diagnostics convince you the estimate is not driven by selection bias?

DisneyHardSelection Bias and Quasi-Experimental Design

Sample Answer

Unlock the full solution

View detailed answers and practice in our question bank

View Solution

Practice more Causal Inference questions

The distribution is bottom-heavy: eight areas each carry between 10% and 18%, so no single topic dominates and you can't afford to skip any of them. Where candidates get burned is the overlap between A/B Testing and Statistics, because a question about randomization unit conflicts (like the guest cancellation example above) quickly demands you reason about power analysis, minimum detectable effect sizing, and multiple comparison corrections in the same breath. Most people over-index on SQL drills and treat Causal Inference as optional, yet difference-in-differences and instrumental variable questions show up at the same 10% rate as Data Pipelines, and they're far harder to improve on in a last-minute cram.

Browse 900+ real questions sorted by area and difficulty at datainterview.com/questions.

How to Prepare

Weeks one and two: SQL and product sense. Solve two window-function problems daily on realistic multi-table schemas, focusing on ROW_NUMBER, LAG, LEAD, self-joins, and CTEs with messy NULL handling. Alongside that, pick a product you actually use (Spotify, DoorDash, whatever), decompose its North Star metric into component drivers, and practice explaining a hypothetical 10% drop out loud in under two minutes.

That two-minute drill trains you to structure metric-decline answers the way interviewers actually score them: hypothesis breadth first, then segmentation logic, then data you'd pull to confirm. For product sense, the rubric rewards how quickly you prioritize plausible causes over how many you list. Weeks three and four, rotate into A/B testing, statistics, and behavioral prep.

For experimentation, drill the three traps that sink the most candidates: underpowered sample sizes, novelty effects that inflate early results, and one-tailed vs. two-tailed test selection (which depends on your pre-registered analysis plan and whether the loss function is symmetric, not just a gut feeling about direction). Expect interviewers at places like Airbnb or Uber to ask you to explain a confidence interval while walking through a real case study, or justify difference-in-differences over a naive pre/post comparison on non-randomized data.

On the behavioral side, write out five STAR stories before you need them, each covering a distinct scenario: pushing back on a stakeholder's flawed assumption, navigating incomplete data, delivering under a tight deadline, influencing a team you didn't manage, and catching your own mistake before it shipped. Rehearse each one out loud at least twice. Candidates who wing behavioral rounds sound vague, and vague gets cut.

Try a Real Interview Question

1WITH base AS (
2  SELECT
3    a.market,
4    a.variant,
5    s.session_id,
6    CAST(s.did_book AS DOUBLE) AS did_book
7  FROM experiment_assignments a
8  JOIN sessions s
9    ON s.user_id = a.user_id
10   AND s.session_start >= a.assigned_at
11   AND s.session_start < a.assigned_at + INTERVAL '7' DAY
12  WHERE a.experiment_name = 'search_ranker_v2'
13), agg AS (
14  SELECT
15    market,
16    variant,
17    AVG(did_book) AS conversion_rate
18  FROM base
19  GROUP BY 1, 2
20)
21SELECT
22  market,
23  MAX(CASE WHEN variant = 'control' THEN conversion_rate END) AS conv_control,
24  MAX(CASE WHEN variant = 'treatment' THEN conversion_rate END) AS conv_treatment,
25  (MAX(CASE WHEN variant = 'treatment' THEN conversion_rate END)
26   - MAX(CASE WHEN variant = 'control' THEN conversion_rate END)) AS lift
27FROM agg
28GROUP BY 1
29ORDER BY 1;

This type of multi-step SQL problem mirrors live-coding rounds, where you'll get an unfamiliar schema with a few joined tables and 20 minutes to produce a business-ready result set. The gap between knowing what a window function does and writing one correctly under time pressure is enormous, and only repetition on varied schemas closes it. Practice more problems like this at datainterview.com/coding.

Test Your Readiness

If any topic area feels shaky, that's where to focus your remaining prep time. Drill those weak spots at datainterview.com/questions.