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