What are we looking for?

We are looking for someone to join the team as a Backend engineer that:

• Is a highly-experienced Backend engineer building complex web applications. The language is not important, we use Python and C++ today, but we are not tied to anything.
• Write code for web-based applications, create fast, easy-to-use, high volume production applications, and engineer prototypes quickly. Speed always wins.
• Contributes to engineering efforts from planning and organization, to execution and delivery to solve complex engineering problems.
• Loves data and SQL

Where will you work at?

Currently, we are looking for engineers for our Core team at Tinybird. The Core team is part of the Developer Experience Product team and is responsible for building and tuning some of the most relevant pieces of the service other teams use to provide a top-notch service to our customers.

Some examples of the areas the Core team manages are:

• Billing: how our customers are being charged for what they are building, from a self-service customer to an Enterprise one
• Observability: we provide several tools for monitoring all the operations and how their API Endpoints are performing, we call them Service Data Sources, where you can build your own alerts
• Authentication: every operation in Tinybird is managed by a token, from browsing our UI to creating a new Pipe using the CLI

How could your typical day look like

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.

‍Some bits about the way we work

• We are a fully remote company, and not just because of COVID19. All of our previous companies were remote friendly companies.
• We give you up to 2400€ to get the right setup at home if you need it
• We are just starting up so your work will impact everything we do. We also believe in full transparency and you will always know what is going on

Here you have our company principles.

‍The Process

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):

• First contact meeting: where you will meet two other Tinybird backend engineers.
• Test: simple async test, where there is no limited time (although we encourage to not spend more than 4 hours).
• Second meeting: meet other founders and/or members of the team.
• We make you an offer.
• That's it!

‍Compensation

• A competitive package, including Stock Options.
• Up to 73K depending on experience.
• 22 days of holiday a year (plus your birthday and public holidays), but… who's counting?
• Freedom to work from wherever suits you best. This time, we are looking for people based in the time zone range: UTC -2 to UTC +3.

How to apply

Apply telling us a bit about yourself and ask us whatever you need to know about the problem we are trying to solve, the company, your role, etc.

‍