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.
Someone to define data architecture for some of our clients. We don't know exactly what's the perfect role name for this, so we prefer to explain what we need from you, so you can pick the right name just in case you don't like the one we've chosen
These days are a little bit different because of the COVID situation but you can get an idea of what's the typical day at Tinybird. I wake up early to read email and catch up with all the basecamp notifications, tickets and so on (other times I go for a run). After that I take care take of my daughter during the mornings and after that I spend the afternoon doing all the work that requires focus. If you are in a similar situation, don't worry, we totally understand that.
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.
At this stage, what I like the most is to read emails from users who find problems using the platform. Yes, it sounds weird, but you only find real problems when you actually use the product. In general most of those emails are problems that can be solved with an option or a different way to do the same (but update our docs to avoid other user hits the same problem, of course), sometimes it needs a bug fix or add a small feature and other just write a guide. That'd be part of your job too.
I usually attend client meetings with Sancha. Before the technical meeting, Jorge has already introduced the product to them, so we just go to the point. We propose a technical solution (and yes, that'd be part of your job too) and send them a proposal. We have a framework to understand our clients' needs, so you'll have a guide to start doing this.
We discuss the 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: 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.
I also write code, do some pull requests, my peers review them and when I merge it, the code goes to production. After a release, we publish a blog post and go and tell our users about what we’ve recently launched to gather feedback.
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.