MotherDuck Interview Guide 2026: DuckDB-Based Serverless Analytics, Hybrid Execution, and Jordan Tigani Heritage

MotherDuck Interview Process: Complete 2026 Guide

Overview

MotherDuck is the serverless data-warehouse company built on DuckDB — the open-source analytical database that runs embedded in applications and laptops alongside traditional server-side execution. Founded 2022 by Jordan Tigani (ex-Google BigQuery founding engineer and The Big Data Problem author) and Tino Tereshko (ex-Firebolt, Google BigQuery), private with a Series B in 2024. ~90 employees in 2026, deliberately small relative to product scope. Headquartered in Seattle with distributed engineering across the US and Europe. MotherDuck’s distinctive technical position: hybrid execution between DuckDB running on the user’s laptop / application and MotherDuck’s cloud service, with the query optimizer deciding where to run each operation. This architecture addresses the observation that most analytical workloads fit on a single modern machine, while cloud execution handles the rare cases that don’t. Engineering stack is C++ / Rust for DuckDB core, Go / TypeScript for cloud orchestration, Python / SQL for the data-processing layer. Interviews reflect the database-systems heritage of the founders — genuine depth expected, pragmatic engineering culture.

Interview Structure

Recruiter screen (30 min): background, why MotherDuck, team interest. The engineering surface is compact: DuckDB core / extensions contribution, MotherDuck cloud platform, hybrid-execution query optimizer, developer experience (SDK, CLI, web console), and AI-adjacent features (MotherDuck AI / text-to-SQL). The small team size means broader scope per engineer.

Technical phone screen (60 min): one coding problem, medium-hard. C++ for DuckDB-core contributions; Go / Rust for cloud platform; TypeScript for web; Python for data. Problems tilt systems-y — parse a SQL expression, implement a columnar operation, build a small query-plan node.

Take-home (many senior / staff roles): 4–8 hours on a realistic systems or database-engineering problem.

Onsite / virtual onsite (3–5 rounds):

Coding (1–2 rounds): one algorithms round, one applied database / systems round.
System design (1 round): analytics-platform prompts. “Design the hybrid-execution query planner deciding client vs cloud execution for each operation.” “Design the data-sharing mechanism between DuckDB clients and MotherDuck cloud.” “Design the text-to-SQL pipeline with MotherDuck AI grounded in the user’s schema.”
Database / systems deep-dive (1 round): DuckDB internals, columnar execution, vectorized processing, OLAP vs OLTP, extension ecosystem. Genuinely deep for core-DB roles.
Behavioral / hiring manager: past projects, small-team fit, database-systems passion.

Technical Focus Areas

Coding: C++ for DuckDB-core (modern C++17/20, template depth for the vector / type system); Go / Rust for cloud platform; TypeScript for front-of-platform; Python / SQL for analytics pipelines.

DuckDB internals: vectorized columnar execution, type system (logical types, physical types, chunking), query optimization (Cascades-adjacent rules), extension mechanism, CSV / Parquet / JSON / Arrow integration, in-memory and single-node execution model, recent work on larger-than-memory processing.

Hybrid execution: MotherDuck’s core differentiation. Understanding how the optimizer decides operations’ execution location, how data flows between client and cloud, consistency trade-offs, and performance implications is central.

Columnar / analytical databases: vectorized execution, compression schemes (RLE, dictionary, bit-packing), predicate pushdown, projection pushdown, partition pruning, zone maps.

Cloud platform: multi-tenant orchestration, storage for MotherDuck-hosted data, compute isolation, cost-aware execution, billing / metering per query execution.

Data-source integration: Parquet, Arrow, Iceberg, Delta Lake, live-query integrations with Snowflake, BigQuery, Postgres. The philosophy is “meet users where their data is.”

MotherDuck AI: text-to-SQL grounded in user schemas, query explanation, anomaly surfacing. Practical applied AI rather than frontier research.

Coding Interview Details

Two coding rounds, 60 minutes each. Difficulty is medium-hard for core-database roles, medium for platform roles. Comparable to Snowflake / DuckDB open-source contribution standards.

Typical problem shapes:

Parse and evaluate a SQL-like expression tree with typing rules
Implement a columnar operation (hash aggregation, sort, filter) with vectorization
Query routing: given a query, determine optimal execution location
Data-format conversion (Parquet read / Arrow interop)
Classic algorithm problems (trees, graphs, DP) with database-applied twists

System Design Interview

One round, 60 minutes. Prompts focus on analytics-platform realities:

“Design the hybrid-execution query planner deciding what operations run client-side vs cloud-side.”
“Design data-sharing between local DuckDB clients and MotherDuck cloud with consistency guarantees.”
“Design the extension-distribution system letting community-authored extensions load safely.”
“Design MotherDuck AI’s text-to-SQL pipeline with schema-grounded prompts and evaluation.”

What works: database-engineering-aware reasoning (query optimization, execution locality, consistency), practical cost-awareness (compute-seconds are expensive), engagement with DuckDB’s specific architecture (embedded vs server execution, extension model). What doesn’t: generic “build a SaaS” responses ignoring what makes MotherDuck’s approach technically distinctive.

Database / Systems Deep-Dive

Distinctive for core-DB and hybrid-execution teams. Sample topics:

Walk through DuckDB’s vectorized execution model.
Discuss columnar compression schemes and their trade-offs.
Reason about hybrid-execution decisions for specific query shapes (TPC-H-like queries).
Explain how predicate pushdown interacts with partition pruning.
Describe what happens when a DuckDB query exceeds single-node memory.

Candidates with real database-engine background (especially columnar / analytical) have a clear edge. Strong database generalists from OLTP-only backgrounds (Postgres, MySQL) need some analytics-focus prep.

Behavioral Interview

Key themes:

Small-team comfort: “How do you operate when owning broad scope with limited infrastructure?”
Database-engineering passion: “What drew you to database systems specifically?”
Pragmatic shipping: “Describe a trade-off between theoretical correctness and practical shipping.”
Customer empathy: “Tell me about engaging with a data-analyst or application-developer user.”

Preparation Strategy

Weeks 3-6 out: C++ LeetCode medium/medium-hard for core-DB roles; Go / Python for platform. Database Internals by Alex Petrov for context.

Weeks 2-4 out: install DuckDB and use it for real analytical work — run queries on Parquet files, try the Python / Node.js bindings. Try MotherDuck for a real project. Read DuckDB’s architecture documentation and papers. MotherDuck’s blog has specific technical posts.

Weeks 1-2 out: mock system design with analytics-platform prompts. Prepare database-passion stories. Jordan Tigani’s writings (including the famous “Big Data is Dead” essay) are context for the company’s thesis.

Day before: review DuckDB execution basics; prepare behavioral stories; refresh columnar-database fundamentals.

Difficulty: 7.5/10

Solidly hard for the smaller company size. Database-engineering rigor is real. The hybrid-execution specialty creates distinctive interview challenges without clean analogs at other companies. Small-team dynamic filters candidates seeking larger-company structure.

Compensation (2025 data, US engineering roles)

Software Engineer: $180k–$225k base, $150k–$280k equity (4 years), modest bonus. Total: ~$280k–$440k / year.
Senior Software Engineer: $230k–$290k base, $300k–$550k equity. Total: ~$380k–$600k / year.
Staff Engineer: $295k–$360k base, $600k–$1.1M equity. Total: ~$550k–$870k / year.

Private-company equity valued at recent Series B marks. 4-year vest with 1-year cliff. Expected value is meaningful given the analytics-platform trajectory and the high-quality team. Cash comp is competitive with top private-company database-platform bands.

Culture & Work Environment

Database-systems-serious culture with pragmatic-shipping orientation. Jordan Tigani’s “Big Data is Dead” thesis (most workloads fit on one machine) shapes the product philosophy. The founders bring Google BigQuery engineering heritage; the team includes genuine database engineers. Remote-friendly with Seattle HQ presence. Pace is deliberate for core-database work, faster for product / platform surfaces. Small team means broad scope and visible impact per engineer.

Things That Surprise People

The database-engineering depth is substantial for company size. The team includes real database experts.
DuckDB itself is a significant open-source project that MotherDuck contributes to and benefits from.
The hybrid-execution thesis (most workloads fit on a laptop) is a genuine technical-strategic bet.
AI / text-to-SQL features are shipping but the company remains grounded in analytical-database engineering.

Red Flags to Watch

Weak database / SQL knowledge for core-DB roles.
Treating MotherDuck as “Snowflake but smaller.” The architecture is genuinely different.
Dismissing the “single-machine is enough” thesis without engaging with it.
Not having used DuckDB for real analytical work.

Tips for Success

Use DuckDB seriously. Run analytical queries on real data. Understand the performance characteristics.
Try MotherDuck’s free tier. Understand the hybrid-execution product experience.
Read Jordan Tigani’s writings. “Big Data is Dead” and related essays frame the company thesis.
Engage with database-systems literature. Columnar execution, vectorization, query optimization — foundational vocabulary.
Be authentic about database-systems interest. This isn’t a company that rewards generalist thinking alone.

Resources That Help

MotherDuck engineering blog and Jordan Tigani’s essays
DuckDB architecture documentation and academic papers (the DuckDB team has published several)
Database Internals by Alex Petrov
The Red Book (Readings in Database Systems) for database-systems literature
DuckDB itself — install locally, run queries on Parquet / CSV, try the Python API
MotherDuck free tier for hybrid-execution experience

Frequently Asked Questions

What’s the “Big Data is Dead” thesis?

Jordan Tigani’s observation (from his time at BigQuery) that most analytical workloads are small enough to fit on a single modern machine — typically under 100GB of compressed data. The industry’s emphasis on “big data” solutions has outlasted the reality of most workloads. MotherDuck’s hybrid architecture applies this insight: run on the laptop when you can, in the cloud when you must. This thesis is more nuanced than a slogan; candidates interviewing at MotherDuck benefit from engaging with it seriously.

Is DuckDB the same as MotherDuck?

No, but related. DuckDB is the open-source analytical database (contributed to by DuckDB Labs in the Netherlands). MotherDuck is a separate commercial company building a serverless cloud data warehouse based on DuckDB plus its own hybrid-execution layer. MotherDuck contributes to DuckDB and has close relationships with DuckDB Labs, but they’re distinct organizations. Candidates can contribute to DuckDB as open-source regardless of MotherDuck interview paths.

How does MotherDuck compare to Snowflake / BigQuery on interviews?

Different emphasis. Snowflake and BigQuery are cloud-first, larger-scale-oriented database platforms with more rigorous interview loops for infrastructure roles. MotherDuck’s interviews focus more on analytics-specific execution, hybrid-architecture reasoning, and smaller-team broad scope. Compensation at MotherDuck is competitive but typically below Snowflake / BigQuery in dollar terms; Snowflake / BigQuery have more predictable public-company equity.

What’s the opportunity in DuckDB contributions?

MotherDuck engineers regularly contribute to DuckDB as part of their work. This is genuine open-source engagement, not a marketing side effort. Candidates who’ve contributed to open-source analytical databases or shown interest have an edge; candidates who haven’t can grow into the open-source-contribution rhythm post-hire. The dual benefit (MotherDuck product + DuckDB open-source community) is distinctive.

Is remote work supported?

Yes for most roles. Seattle HQ has some in-person presence; remote US and limited international hiring happens. Timezone overlap with US business hours is generally expected. The small-team distributed-engineering model means async practices are mature.