Snowflake Data Engineer 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

   Design an event contract and schema registry process for Snowflake's warehouse query telemetry producers and data consumers

   MediumRound 6: System DesignData Contracts

   How to answer:

   Define versioned schemas, compatibility rules, ownership, validation at ingestion, documentation, and a migration process for breaking changes.

2. Q2

   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.

3. Q3

   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.

4. Q4

   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.

5. Q5

   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.

6. Q6

   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.

7. Q7

   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.

8. Q8

   What retention strategy would you apply to raw warehouse resume data and curated query marts at Snowflake?

   MediumRound 7: Cloud Data Warehouse System DesignData Warehousing

   How to answer:

   Keep raw data long enough for audit, replay, and compliance needs, but consider tiered storage or aggregation for very high-volume events. Curated marts often need longer retention because they support trends and finance or product history. The answer should account for privacy deletion and legal requirements.

9. Q9

   Design a star schema for Snowflake's cloud data warehouse platform that supports reporting on successful queries, credit consumption, and trial -> data load -> first query -> production workload

   MediumRound 4: Data ModelingDimensional Modeling

   How to answer:

   Define a clear fact grain for queries, add conformed dimensions such as warehouse, account, database, and region dimensions, and store additive measures separately from derived metrics.

10. Q10

    Design reconciliation logic for Snowflake's ETL so credit consumption in Snowflake internal analytics warehouse matches the operational source

    MediumRound 5: ETL DesignETL Reconciliation

    How to answer:

    Compare control totals by date and cloud region, track accepted tolerances, investigate deltas, and block publishing on material mismatches.

11. Q11

    For Snowflake, decide between ETL and ELT for transforming query, warehouse, storage, billing, and data-sharing events. What factors drive your choice?

    MediumRound 5: ETL DesignETL vs ELT

    How to answer:

    Choose ELT when the warehouse/lakehouse can scale transformations cheaply; choose ETL when privacy, bandwidth, or source constraints require pre-load shaping.

12. Q12

    How would you estimate sample size for detecting a change in active accounts at Snowflake?

    MediumRound 6: Cost Optimization Experimentation CaseExperimentation

    How to answer:

    Use baseline rate or variance, minimum detectable effect, significance level, power, and randomization unit. Adjust for clustering or repeated measures if observations are not independent. The answer should mention that business relevance should drive the MDE, not only what is statistically convenient.

13. Q13

    Why would Snowflake run an A/A test before launching major experiments?

    MediumRound 6: Cost Optimization Experimentation CaseExperimentation

    How to answer:

    An A/A test verifies randomization, logging, metric pipelines, and false positive behavior when no true treatment exists. It can reveal SRM, biased exposure, or broken joins. The answer should mention that passing A/A tests increases trust but does not guarantee every future experiment is valid.

14. Q14

    How would you model Snowflake's warehouse auto-suspend tuning experiment results so analysts can compare treatment and control without metric leakage?

    HardRound 4: Data ModelingExperimentation Modeling

    How to answer:

    Create assignment facts at exposure time, immutable variant dimensions, and outcome facts joined by actor and valid time windows.

15. Q15

    Design a data platform feature store or serving layer for Snowflake's dashboards and downstream ML features using query, warehouse, storage, billing, and data-sharing events

    HardRound 6: System DesignFeature/Data Serving

    How to answer:

    Define feature contracts, compute batch and streaming features, store point-in-time-correct values, monitor drift, and control access.

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

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

Indicative Data Engineer pay in India: ~₹10–45 LPA (role-level range, not a Snowflake-specific figure).

Other roles at Snowflake

Data Engineer interviews at other companies