Snowflake Data Analyst Interview Questions (2026)

1. 1HackerRank Online Assessment60 minMedium

   2-3 medium-to-hard problems screening early-career candidates before human rounds.

2. 2Coding Round60 minHard

   Hard-leaning implementation problem with attention to memory and performance, not just correctness.

3. 3Systems / Database Internals Round60 minHard

   Deep-dive on OS and DB fundamentals: concurrency control, caching, columnar storage, query execution - hardest for engine-team candidates.

4. 4Design Round60 minHard

   Design a warehouse-scale component: metadata service, result cache, or multi-tenant compute scheduling with storage/compute separation reasoning.

5. 5SQL & Data Round45 minMedium

   For data/solutions roles: advanced SQL, warehouse performance tuning and data-modeling scenarios on Snowflake itself.

6. 6Hiring Manager + HR Round45 minEasy

   Project walkthrough, team fit and motivation, followed by a standard HR discussion on level and compensation.

1. Q1

   Model Snowflake's query analytics using facts and dimensions. What is the fact grain?

   MediumRound 2: Account Usage Data ModelingData Modeling

   How to answer: The fact grain should be one row per business-defined query unless a lifecycle-event grain is explicitly needed. Dimensions such as region, warehouse size, and user attributes should attach through stable keys. The explanation should emphasize declaring grain first, because metric correctness and join safety depend on it.

2. Q2

   How would you model warehouse resume, query start, query completion, and credit usage events for Snowflake?

   MediumRound 2: Account Usage Data ModelingData Modeling

   How to answer: Keep a raw immutable event table, create typed staging models per event family, and build a lifecycle or funnel fact for analysis. The raw layer supports audit and replay, while analytics models standardize timestamps, identities, and event names. Good answers address schema evolution and duplicate events.

3. Q3

   warehouse size attributes change over time at Snowflake. Design the dimension table

   HardRound 2: Account Usage Data ModelingData Modeling

   How to answer: Use an SCD Type 2 dimension with surrogate key, natural key, effective_start, effective_end, is_current, and tracked attributes. Facts should join to the dimension version valid at the fact timestamp. This allows historical analysis without overwriting old attributes when current-state source values change.

4. Q4

   Snowflake needs to analyze queries by multiple classifications of warehouse size. When would you use a bridge table?

   HardRound 2: Account Usage Data ModelingData Modeling

   How to answer: Use a bridge table when one query or dimension member can belong to multiple categories and a simple foreign key would force duplication. The bridge should include allocation weights if metrics need to sum correctly across classifications. The explanation should warn about double counting and clearly define how rollups are handled.

5. Q5

   Which conformed dimensions would help Snowflake compare credit consumption, warehouse utilization, and data sharing adoption across teams?

   MediumRound 2: Account Usage Data ModelingData Modeling

   How to answer: Common dimensions such as date, region, warehouse size, and user or account segments should be standardized across marts. Conformed dimensions reduce reconciliation debates because teams slice metrics the same way. The answer should mention ownership, slowly changing attributes, and backward compatibility.

6. Q6

   When would you use a periodic snapshot fact for Snowflake's account usage query history?

   HardRound 2: Account Usage Data ModelingData Modeling

   How to answer: Use a periodic snapshot when the business needs state at regular intervals, such as daily availability, balance, utilization, or inventory. It complements event facts by making point-in-time reporting easier. The explanation should include snapshot grain, date spine, storage tradeoffs, and handling corrections.

7. Q7

   Design an accumulating snapshot for the lifecycle from query completion to credit usage to data share access at Snowflake

   HardRound 2: Account Usage Data ModelingData Modeling

   How to answer: Create one row per query with milestone timestamps and statuses that update as the lifecycle progresses. This makes duration and bottleneck metrics easy to calculate. The answer should discuss mutable records, idempotent updates, late-arriving milestones, and whether completed records become immutable.

8. Q8

   Snowflake has anonymous events and logged-in events for account admins. How would you model identity resolution?

   SeniorRound 2: Account Usage Data ModelingData Modeling

   How to answer: Maintain an identity graph that maps anonymous IDs, device IDs, and user IDs with validity windows and confidence levels. Analytics models should choose the identity appropriate to the metric, such as session-level or account-level. The explanation should address privacy, merge/split corrections, and reproducibility of historical metrics.

9. Q9

   How would you model adjustments such as cloud services credit adjustment so Snowflake's data sharing adoption remains reconcilable?

   HardRound 2: Account Usage Data ModelingData Modeling

   How to answer: Use an append-only ledger or adjustment fact with transaction type, effective date, posted date, amount, currency, and source reference. Avoid overwriting historical amounts without an audit trail. The explanation should separate operational correction time from business effective time and show how net metrics are derived.

10. Q10

    Give a factless fact example for Snowflake involving warehouse resume or eligibility

    MediumRound 2: Account Usage Data ModelingData Modeling

    How to answer: A factless fact can record that a user, account, or item was eligible for an experience, policy, or inventory state even when no measurable transaction occurred. It supports denominator calculations and coverage analysis. The explanation should mention that absence of activity is meaningful only when the eligible population is modeled.

11. Q11

    A model combines user-level attributes with query-level facts at Snowflake. What grain problems can occur?

    HardRound 2: Account Usage Data ModelingData Modeling

    How to answer: User-level rows can multiply facts if the user dimension contains multiple versions or multiple roles. Define the fact grain, join to one valid dimension record, and aggregate only after join safety is guaranteed. The explanation should include tests for primary key uniqueness and row count before and after joins.

12. Q12

    How would you model semi-structured attributes from warehouse resume payloads at Snowflake?

    MediumRound 2: Account Usage Data ModelingData Modeling

    How to answer: Store raw payloads for replay, then extract stable high-value attributes into typed columns. For sparse or rapidly changing attributes, use a key-value satellite table only when analysts need flexibility and understand its costs. The explanation should cover schema drift, data types, and query performance.

13. Q13

    What aggregate tables would you create for high-traffic Snowflake dashboards on credit consumption?

    MediumRound 2: Account Usage Data ModelingData Modeling

    How to answer: Create daily aggregates by common dimensions such as region, warehouse size, and workload type, while preserving a detailed fact for drilldown. Aggregates should be derived from canonical facts and tested against them. The answer should mention freshness, backfill, and avoiding a separate business definition in the aggregate.

14. Q14

    Would you choose Data Vault, dimensional modeling, or a hybrid approach for Snowflake's analytics platform? Why?

    SeniorRound 2: Account Usage Data ModelingData Modeling

    How to answer: A hybrid can work: raw vault-like structures preserve source history and auditability, while dimensional marts serve analysts and BI tools. The choice depends on source volatility, regulatory needs, team skill, and consumption patterns. A strong answer avoids methodology dogma and focuses on maintainability and business usability.

15. Q15

    Snowflake facts include multiple timestamps such as created, updated, and completed. How would you model role-playing dates?

    MediumRound 2: Account Usage Data ModelingData Modeling

    How to answer: Use a shared date dimension joined multiple times with clear aliases, or keep date keys directly on the fact with semantic names. Metrics should specify which date role they use. The explanation should mention that inconsistent date roles are a common cause of reporting discrepancies.

Practice these with instant AI feedback in a live mock interview → Start a Snowflake Data Analyst mock

Deepen SQL, warehousing and cloud data internals; prepare data-system design

Indicative Data Analyst pay in India: ~₹6–22 LPA (role-level range, not a Snowflake-specific figure).

Other roles at Snowflake

Data Analyst interviews at other companies