🚨 This position is closed now, thanks for reading ·
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.
We are a team of 14. We have a long experience of 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. And that diversity will lead us to making better decisions and to creating a better organization.
We are looking for someone to help us with our product on the Frontend side. Let us explain what we need from you:
I try to review what users have done with Tinybird the previous week, paying special attention to those features that we have launched recently, checking if they are working as we expected, and if they are understood as we designed them.
Then I keep working on the issues related to our quarterly OKRs. Our product design approach is: we identify a project, we create a small team who will explain why it's important and describes how it would work. Then, everyone else asks questions and we decide if that makes sense or not. You'll be part of this, of course.
We believe that support is as much part of the product and services as is the API, the UI, or the documentation. That is why we want to provide the best possible support to our customers, and why we alternate the support responsibility amongst all of us and each of us spends one-week turns as the Support Owner. Also,
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.
We also take time to contribute to blog posts about how things work, product updates,.... It's hard to keep up with the pace, especially if we have a problem or an unexpected client request, but writing those helps us a lot.
Here you have our company principles.
We try to simplify the process as much as we can, and we don't like to extend it with any candidate more than two weeks (if the whole process is completed):
Fill up the form at the end or send us an email telling us a bit about yourself, and asking us whatever you need to know about the problem we are trying to solve, the company, your role, etc...