About Tinybird
At Tinybird, we help developers and data teams unlock the power of real-time data. This enables them to build data pipelines and innovative data products quickly. With Tinybird, you can seamlessly ingest multiple data sources at scale, query them using the SQL you already know, and publish results as low-latency, high-concurrency APIs for your applications. Developers can create fast APIs; what used to take hours or days now takes only minutes. Tinybird is the essential tool that data engineers and software developers have been waiting for, making it easier to drive innovation.
About the Platform team
The Platform team builds, operates, and continually improves the technical foundations that Tinybird relies on.
We help Tinybird run safely at scale, evolve predictably, and support product and customer growth with minimal operational friction. This involves working on the systems that ensure reliability, observability, performance, infrastructure, cost efficiency, CI/CD, development environments, and critical backend services.
Platform is both an infrastructure team and an operations team. We focus on making Tinybird's foundations reliable, observable, scalable, and easier to evolve.
What we are looking for
You have strong experience in designing, building, and running distributed cloud architectures and large-scale web-based production systems.
You have deep knowledge of Kubernetes, which is essential for this role. You should be comfortable designing and operating production-grade clusters, writing custom controllers or operators as needed, and tuning autoscaling mechanisms (KEDA, Karpenter, and similar) to respond to real-time workloads. You know how Kubernetes manages networking, storage, scheduling, and resources, and you can analyze performance and failure scenarios at scale.
You are skilled in AWS and GCP.
Coding skills are required. We are not looking for a software developer, but baseline. You should be able to explore our codebase, ClickHouse source code, or any other software we use to understand how things work. Our primary languages are Python and some C++.
You are comfortable operating close to production: debugging incidents, understanding system behavior, improving observability, and enhancing service reliability.
You think in systems and pay attention to edge cases, failure modes, and specific implementation details.
You care about performance, reliability, cost efficiency, and operational simplicity. You prioritize action, iteration, and delivery. You know many decisions can be reversed quickly, and that speed is important in business and technology.
You take ownership, follow through, and are willing to tackle issues that may be broken, because you can fix them if necessary.
You enjoy data and SQL, and you are curious about how real-time analytical systems work. We use our own product, so you'll need some SQL experience to query our own data. Experience with ClickHouse and/or launching database systems at scale would be a big plus.
Familiarity with Traefik, Varnish, Redis, Terraform, or Ansible is not mandatory, but it's helpful and will get you up to speed quickly. We don't expect anyone to know the full stack upon arrival.
You communicate clearly in writing. This is important because we work asynchronously, document decisions, write operational notes, and share context across teams.
You use AI tools such as Claude Code, Cursor, ChatGPT, and others to enhance efficiency and improve your workflows.
You are fluent in English and Spanish. English is the primary language we use at Tinybird, and Spanish is commonly spoken within the Platform team.
You are willing to participate in on-call rotations, not only to maintain service health but also to understand the real problems our customers and internal teams face.
You are located in an EU timezone.
We seek an experienced Site Reliability Engineer who enjoys keeping large-scale distributed systems reliable and adaptable as they grow. You should understand how to make hardware and software work well together and be eager to grasp both our product and the real challenges our customers and internal teams face.
You might be a good fit if:
Our stack
Kubernetes: the foundation of our infrastructure. Most of our infrastructure runs on top of it, and autoscaling is crucial.
ClickHouse: our primary data store.
Python: mostly used for our backend, except for some components that rely on C++ for performance.
Varnish: for load balancing and, at times, caching.
Traefik: for ingress and routing.
Redis: for our metadata store.
Zookeeper: for coordinating ClickHouse replicas.
ArgoCD: for GitOps-based continuous delivery.
Grafana, Loki, Mimir, and OpenTelemetry (OTEL): for monitoring, alerting, and telemetry (we're increasingly standardizing on OTEL).
We run our stack on Linux and aim to keep things simple. The technologies we use include:
What you will work on
Enhancing high availability and elasticity so the system can scale automatically and efficiently as our customer base grows. It should make capacity decisions transparently and safely, without manual intervention.
Boosting our observability capabilities, from low-level resource usage to high-level service metrics, including telemetry, dashboards, alerting, and long-term visibility into system health.
Improving disaster recovery with better tools, incident discovery, and enhanced oncall experiences.
Handling Kubernetes lifecycle tasks, managing cluster infrastructure, autoscaling, and ensuring safe deployments.
Understanding how ClickHouse operates under the hood and extracting the best performance possible from it.
Identifying bottlenecks and improving performance across storage, networking, and compute.
Reducing operational burden by transforming manual or fragile processes into repeatable, well-managed systems.
Assisting with incident prevention, operational reviews, and follow-up tasks after reliability issues.
Strengthening CI/CD foundations to help teams build and deploy changes with greater confidence.
As part of the Platform team, your work will focus on the systems that keep Tinybird reliable, efficient, observable, and scalable. We operate a large-scale distributed system where efficiency is key. This is not just about automating infrastructure; it's about building and evolving a self-service platform that optimizes the underlying hardware, adapts to workload changes, and autoscales accordingly.
Depending on the week, you could be:
You'll collaborate closely with product and backend teams to design system architecture, optimize resource use, and make our platform more adaptable and autonomous. This role suits someone who enjoys both building software and understanding how that software behaves in production.
How could your typical day look like?
- In our company, everyone is part of the product team. While your focus will be on the Platform, your work priorities will often arise from what the product, customers, and engineering teams need from Tinybird's foundations.
- Some days, you might design autoscaling behavior or develop our Kubernetes infrastructure. Other days, you could be investigating a production issue, improving dashboards, ensuring safer deployments, optimizing ClickHouse performance, or helping another team move forward by reducing platform friction.
- We regularly discuss the product and the platform since they are closely linked. Tinybird needs to address today's customer challenges while building foundations for future scalability. Having someone understand the internals, operational realities, and long-term technical trade-offs is crucial.
How we work
We are a remote company committed to a remote-first culture. However, we find that occasionally gathering in person, especially in our Madrid office, can help us move faster, stay aligned, and solve difficult problems effectively. From time to time, we try to meet in person and spend time together.
Your contributions will significantly influence how Tinybird operates and scales. We believe in ownership, transparency, and clear communication.
We value engineers who balance speed with reliability, and short-term needs with long-term platform health.
We prefer documented decisions, clear ownership, and operational practices that make systems easier to comprehend and maintain. We build software with empathy to make it user-friendly and manageable.
We work closely with product, support, customer success, and other engineering teams because the Platform exists to support the rest of the company.
Check out our blog or follow us on LinkedIn to learn more about what matters to us.
The process
Initial contact meeting with the Hiring Manager to discuss the process.
Live Technical Assessment (1 hour, live, screen sharing, with two team members) to demonstrate your skills.
Team Alignment meeting (45 minutes with the other two team members) to discuss technology and teamwork.
Final meeting with our CEO to review culture fit, long-term company vision, and any remaining questions.
We aim to simplify the recruitment process as much as possible and avoid unnecessary steps for candidates. Your recruitment process will look like this:
Originally posted on