🚨 This position is closed now, thanks for reading ·
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 as a Field engineer.
We are a team of 14 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.
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.