We started Tinybird because we had a problem. Dealing with large amounts of data is hard and, as the amount of data grows, it gets exponentially harder. We thought we had enough experience to create a product to fix that problem.
Tinybird is a SaaS product to create real-time analytics APIs over large amounts of data. And it's deeply focused on improving the developer experience.
Long story short, after some months, the list of clients using our product is growing but our team isn't growing quite as fast. And as you might guess, that is starting to hurt, and that's why we are looking for someone to help us.
We are a team of 9 with extensive experience building and growing companies (and sometimes selling them), all of us have a technical background. We like simplicity and speed. We believe data-driven real-time applications have the potential to change entire industries.
We firmly believe in equal opportunities and in a workplace which is safe, diverse, and inclusive. We also believe that diversity will lead us to making better decisions, and that a diverse organization is 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...