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 join the team as a Backend engineer that:
Tinybird is full of early birds (pum intended). We wake up early to read email and catch up with all the basecamp notifications, tickets and so on (other times some of us just go for a run).
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 like meetings but we don't like too many meetings, that's why a few meetings are open to everyone within the company (Customer success, product status and our bi-weely townhall) while we focus on creating small and productive teams for solving problems.
We talk about product 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 (that'd be you as well).
Our product design approach is quite simple: someone proposes a solution to a problem something, explains 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 also take time to write blog posts about how to do things with our product. 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...