Tinybird is the developer-first real-time analytics platform — built on ClickHouse, exposes SQL-as-API for low-latency analytical queries. Series B in 2024. The interview emphasizes deep ClickHouse engineering, real-time data ingestion, and the developer experience of analytics-as-API.
Process
Recruiter screen → 60-minute coding (Python or Go) → onsite virtual: 2 coding, 1 system design (often distributed-data-flavored), 1 craft deep-dive, 1 behavioral. Cycle: 3–4 weeks.
What they actually ask
- Design a multi-tenant ClickHouse platform with isolation
- Design a high-throughput ingestion pipeline (Kafka → ClickHouse)
- Design a SQL-to-API publishing system with caching and rate-limiting
- Coding: medium DSA, often with data or pipeline framing
- Behavioral: developer empathy, ownership, OSS-inspired culture
Levels and comp (2026)
- SE: $160K–$220K total (cash + meaningful equity)
- Senior SE: $230K–$310K total
- Staff: $315K–$430K total
Prep priorities
- Be fluent in Python (most of the platform) and Go (some backend)
- Understand ClickHouse internals (MergeTree, materialized views, partitioning)
- Brush up on streaming ingestion (Kafka, Flink) and analytical query patterns
Frequently Asked Questions
Is Tinybird remote-friendly?
Distributed-first since founding. Hubs in Madrid and remote across EU/US.
How does Tinybird compare to ClickHouse Cloud or SingleStore?
Tinybird is the developer-first abstraction layer (SQL-as-API) on top of ClickHouse. ClickHouse Cloud is the managed engine itself. SingleStore is a different engine entirely. Tinybird’s differentiator is the API publishing UX. Comp competitive at senior+ for early-mid stage data infrastructure.
What is the engineering culture?
Small, customer-driven, calm pace. Strong async / written-first culture across the EU/US split.