At Tinybird, we enable developers and data teams to build Realtime Data Products at any scale. We help companies ingest millions of rows per second and power their analytical applications via low-latency, high-concurrency SQL based APIs.
Our founding team has a combined experience of over 60 years building cloud and data intensive products serving organisations all over the world, and we are backed by investors who have built or are building some of the most relevant developer tools out there, like Nat Friedman (GitHub CEO), Nicolas Dessaigne (Algolia co-founder) or Guillermo Rauch (Vercel CEO), among many others.
Being a remote friendly company, with over 20 birdies from different nationalities we share the company values such as, open-minded, accountability driven, transparent and ego-free. We want to achieve great things together. Our strength lies in a diverse team where everyone feels respected. We truly believe it is the key to a better work environment, to making better products and taking better decisions, with a broader and more inclusive approach to everything we do. We have a deep interest in you as a person!
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...