Product Engineer

The role

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

This role spans everything from user-facing tools like SDKs and the CLI to backend systems, data workflows, and the infrastructure that powers them.

You’ll work across different parts of the product, helping improve how users explore, understand and build with their data. While a big part of the work happens in the frontend, we’re looking for someone comfortable going deeper when needed, whether that’s backend logic, data workflows, or understanding how things run on top of ClickHouse.

• 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.

Things we care about

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.

Who we’re looking for

We’re looking for product engineers who:

• 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, and don’t mind going deeper into data or infrastructure when needed

• Are curious about how systems work end-to-end, from user-facing features down to data and infrastructure

• Have strong product sense and care about user experience

• Use AI tools effectively as part of their daily workflow

• Experience with TypeScript (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

How we work

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.

Depending on the problem, this might also involve going deeper into backend logic, data pipelines, or understanding how things run on top of ClickHouse.

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 you’re also expected to contribute to product and UX decisions, not just implement them.

Our stack includes TypeScript (React), Python, SQL, and our own tooling around data workflows. Working with databases is a core part of the job, so you should be comfortable querying data, understanding how it’s structured, and using it to make decisions. You don’t need to know everything, but you should be comfortable moving across the stack and picking up new tools quickly.

We are a remote company, committed to a remote-first culture, but we have found that being together in person, especially in our Madrid office, often helps us move faster, stay aligned, and solve hard problems more effectively. Every now and then, we try to meet in person and spend time together.

Compensation:

The Process

We try to simplify the process as much as we can, and we don't like to extend it with any candidate more than necessary. As candidate, you're recruitment process will look like this:

• First contact meeting, where you will meet the Hiring Manager of the process.

• Live Technical Assessment (1h, live, sharing screen, with 2 people from the team) to demonstrate your skills.

• Team Alignment meeting (45min, with other 2 people from the team) to talk about technology and team work.

• A last meeting with our CEO to go over culture-fit, long-term company vision, and any other questions you might have.

• We make you an offer. And that's it!