Product Engineer; SDK, CLI & Interfaces

About Tinybird

At Tinybird, we help developers and data teams take flight by unlocking the power of real‑time data to quickly build data pipelines and innovative data products. With Tinybird, you can effortlessly ingest multiple data sources at scale, query and shape it using the 100% pure SQL you already know and love, and publish results as low‑latency, high‑concurrency APIs for your applications to chirp about.

Developers can create fast APIs, faster. What used to take hours and days now only takes minutes! Tinybird is the essential tool that data engineers and software developers have been waiting for enabling you to drive innovation with ease.

We’re looking for an experienced Product Engineer to help us build and evolve how developers interact with Tinybird.

This role spans everything from the SDKs (Typescript and Python) and CLI to the features and workflows that shape the overall experience.

You’ll work across different parts of the product, helping improve how users explore, understand and build with their data. Many of these areas closely tied to AI:

• Explorations — interactive data exploration with AI
• Playgrounds — quick environments to test queries and ideas
• Local development — build and test data workflows locally
• Time series tools — working with time‑based data
• MCP (analytics agents) — AI‑powered workflows and data agents

Some of these are already widely used. Others are still evolving. All of them have room to improve, especially in how they feel to use.

A big part of the role is also exploring what’s next. Many of these areas are still evolving, especially with AI, and we’re constantly thinking about new ways to improve how users interact with their data or entirely new features that can make that experience significantly better.

You’ll work closely with design, but this is not a “just implement” role. You’ll be expected to make decisions, shape features, and push things forward.

You’ll also use AI as part of your daily workflow to explore ideas, speed up development, and iterate quickly.

• Autonomy – We don’t assign work ticket by ticket. Engineers decide what to work on based on impact, urgency, and context.
• Shipping fast – We ship every day. Iteration matters more than perfect planning.
• AI as a tool – AI is part of the workflow. It helps us explore ideas, move faster, and reduce the time from concept to production.
• Product ownership – Engineers don’t just implement features, they shape them. You’re expected to make decisions and push things forward.
• Developer experience – We care deeply about how our product feels to use. Small improvements in clarity, speed, or usability matter a lot.

• Take ownership and are comfortable making decisions without waiting for perfect direction
• Move fast and know how to prioritize what matters most
• Have experience building products used by developers
• Have worked on SDKs, CLIs, or developer‑facing tools
• Are comfortable working across frontend and backend
• Have strong product sense and care about user experience
• Use AI tools effectively as part of their daily workflow
• Experience with Type Script (React) and Python is a plus, we use both across the product
• Experience working with databases and SQL is highly valued, data is at the core of what we build

We ship to production every day. Building and iterating is a continuous process.

Most of your time will be spent building: sometimes new features, sometimes improving existing ones, sometimes fixing real problems from users. You might be working on the SDK or CLI, improving workflows like deployments or jobs, or shaping features like Explorations or MCP.

A big part of the work is also thinking about what doesn’t exist yet, exploring new ideas, especially around AI, that can significantly improve how users interact with their data.

There won’t always be a clear spec or a predefined plan. Deciding what to work on and where you can have the biggest impact is part of the job.

You’ll take features from idea to production and beyond: defining the approach, building the first version, shipping it, and iterating based on real usage and feedback.

You’ll work closely with design, but…