Clickhouse Developer

About Tinybird

Building applications over large amounts of data is hard and, as the amount of data grows, it gets exponentially harder. Much more so if you want to exploit that data as it happens, in real-time, before the opportunity to make mission critical decisions disappears.

We created Tinybird to help Developers and Data teams do just that: building real-time data products at Scale. It can ingest millions of rows per second and serve low-latency, high-concurrency SQL based APIs. 

We are deeply focused on improving the developer experience with Tinybird. And because data won’t stop growing any time soon, on ensuring that any developer can build highly scalable data applications over any amount of Data. 

‍

Who are we?

We are a team of 12. We have a long experience in building and growing data intensive products and companies (and sometimes selling them). All of the founders have a technical background. We like simplicity and speed. And we believe that data-driven real-time applications have the potential to change entire industries.

We also firmly believe in equal opportunities and in a workplace which is safe, diverse, and inclusive. So don’t be discouraged if you don’t see yourself reflected in our team page for whatever reason and apply if the rest of this offer sounds like you could fit: we are committed to building a diverse organization because we truly believe it is the key to a better work environment, to making better decisions and to become better as a team, with a wider perspective and a more inclusive approach to everything we do. 

‍

What are we looking for?

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 that runs under the Tinybird covers. 

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:

• you have C++ experience and you are already working with/contributing to Clickhouse, or
• you have C++ experience in other type of products, but you are keen to become a Clickhouse internals expert
• you are an experienced programmer (in C++ or other) and have a deep understanding of how databases work internally.
  

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:

• You are fluent in english. If you speak spanish, russian or chinese also, that would be amazing and it would make us all wonder what have we done with our lives.
• You communicate well in writing. Not only because we favor asynchronous work, also because you will have to write documentation and guides and the occasional blog post.
• Ideally you are located somewhere in Europe, or at least, not too many time-zones away. This is not essential but would certainly make it easier as, for now, our team is entirely in the CET timezone.

‍

How would your day look like

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.

We use Basecamp 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.

‍

Some bits about the way we work

• We are a fully remote company, and not just because of COVID19. All of our previous companies were remote friendly companies. 
• We give you up to 2400€ to get the right setup at home if you need it. If you need more, just ask.
• We are just starting up so your work will impact everything we do. We also believe in full transparency and you will always know what is going on.
• No politics. 
  

Here you have our company principles.

‍

Compensation

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!

‍

How to apply

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