We are looking for someone who wants to contribute to Open Source as a full time job. In particular, someone that wants to contribute to ClickHouse, the database on which Tinybird is built.
Things are changing rapidly in the Open Source world: popular companies are changing the licenses of their OS products trying to prevent bigger players from monopolizing the market they created. But we still firmly believe in Open Source as a force for good: how couldn’t we? We have built our professional lives on top of it.
So we want to contribute to making ClickHouse better: to serve our needs, of course, but also to give back to the community and ensure that it remains the fastest database for years to come.
If you are the ideal candidate, it probably means that one of the below is true:
However, if none of the above is true for you but you still think you are right for this, feel free to apply and let us know why.
Some other things that are important to us:
In this company, everyone is part of the product team. While your focus will be on ClickHouse, the priorities of what you tackle will be mostly driven by the things we want to accomplish with the product.
For instance, you might need to prioritize solving ClickHouse bugs that may be causing our customers grief. Other times you will be developing new ClickHouse features. And oftentimes you will be helping someone on the team figure out what is the best way to solve a problem with ClickHouse. For example, there are multiple examples of public contributions we have made in the past, such as:
We discuss the product pretty much every day. It needs to balance today’s problems with tomorrow’s, so the vision of someone working with the product to fix real problems is crucial, but the outlook of someone who knows the internals (your case) is invaluable to making the right long-term decisions.
Our product design approach is to work backward: someone proposes a solution to a problem, explains why it's important, describes how it would work, and writes (but doesn’t yet publish) the announcement blog post. Then, everyone else reads it, asks questions, and we decide if that makes sense or not. You'll be part of this, of course. Typically, we build what we call an MSP (“Minimum Shitty Prototype”) that enables us to see very roughly how it would work and to understand the real effort involved in actually shipping it.
Here you have our company principles.
First, check out this ClickHouse bug. If this is something you would feel comfortable solving (or at least, trying to solve), you should by all means apply. Give it a go! Then apply below and tell us a bit about yourself, how you would tackle (or have tackled) the issue and ask us whatever you need to know about the problem we are trying to solve, the company, your role, etc...