Learn how to analyse TeraBytes of data in Real-Time with our "Principle of Real-Time Analytics" course
🚨 This position is closed now, thanks for reading ·
At Tinybird we strive to make Data Engineers and Developers’ lives easier through our products, in particular when it comes to generating value out of huge quantities of data.
We started Tinybird to address a challenge we had experienced many times in our previous jobs: that working with large amounts of data is hard and, as the amount of data grows, it gets exponentially harder.
We had a good idea of how to solve this and that's how we started to work on Tinybird Analytics, a SaaS product to create real-time analytics APIs over large amounts of data. One that is deeply focused on improving the developer experience.
So far we have kept the team pretty minimal, but as our list of clients grows, we are starting to feel the need to grow in several areas, from Product Development to Sales. In this particular occasion, we are looking for someone to help us as a Site Reliability Engineer.
We are a team of 7 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 make better decisions and that a diverse organization is a better organization.
Someone to help us with development and production deployments.
Tinybird Analytics is a set of applications and libraries interacting with a column-oriented OLAP database. Our core technologies include Linux, ClickHouse, and Python. Until now, we have automated as much as possible the CI/CD procedures, the infrastructure provisioning, and the cluster deployment.
However, we know our product could be much more efficient by improving the way we use our infrastructure, but we don't think that's possible by just having someone in the operations room. This won't be about running the service but also about building it.
As an SRE, you will:
An example of future developments is having an on-demand database cluster where we can dynamically—in seconds/minutes—increase and decrease the capacity of the platform based on usage patterns or customer needs.
We work with 6-weeks OKRs, which we revisit once per week. We believe this is a great way of sharing the strategic challenges we face but also of providing room for teams to generate initiatives autonomously.
We like to work asynchronously as much as possible and we have few internal meetings, but we ensure all of us meet at least twice per week. In these meetings, we normally discuss ongoing projects, share updates and discuss strategic initiatives that we normally start and follow up on asynchronously.
We believe in validating over debating. We still have a manageable amount of clients and we like to spend time with them, talking about ways to improve our product, or problems they are facing were we can help.
And we like having fun too!