At Tinybird, we enable developers and data teams to build real-time data products at any scale. Engineering teams who use Tinybird achieve much faster development velocity, which means new products / features get to market faster. In addition, our engineering team has done an amazing job architecting our product in a way that allows Tinybird customers to deliver a blazing fast user experience in a cost-effective way.
Our founding team has deep expertise building cloud and data intensive products serving organizations all over the world, and we are backed by great team members and investors who have built or are building some of the most relevant developer tools out there (including the Founders of GitHub, Algolia, and Vercel amongst others.
Being a remote-first company with over 40 birdies from different nationalities, we believe our strength lies in cultivating a diverse environment. Everyone at Tinybird plays a role in forming and executing our strategy, and we truly believe our globally diverse workforce is the key to unlocking the most value for our customers.
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 to ensure that it remains the fastest database out there 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 most of the time 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 done in the past, such as:
We use Basecamp and slack for daily coordination and planning, GitLab for issue tracking and milestones and Google Docs to discuss things like product decisions. There is always something to read and discuss or to contribute to.
We discuss the product pretty much every day. It needs to be a balance between today and tomorrow's problems so the vision of someone that is working with the product to fix real problems is crucial, but the outlook of someone that knows the internals (your case) is invaluable to making the right long term decisions.
Our product design approach is to work backwards: 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. Often time 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.
We are not putting a cap on this one: it really depends on experience and how “ideal” a candidate you are for the role, whether you have been developing in Clickhouse or not and how quickly you could ramp up to fill the role. You tell us!
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...