.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.Writes code for web-based applications, creates fast, easy-to-use, high volume production applications, and engineers 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.Some other things that are important to us:You are fluent in English. If you speak Spanish, Russian, or Mandarin also, that would be amazing.You communicate well in writing. This is important not only because we favor asynchronous work but also because you will have to write documentation, guides, and the occasional blog post.Someone who participates as part of the on-call team, to understand not only our product but also the issues our clients face.You are located somewhere in Spain.How could your typical day look likeIn this company, everyone is part of the product team. While your focus will be on Backend development, the priorities of what you tackle will be mostly driven by the things we want to accomplish with the product.Depending on the week, you could be working on the priorities for the Backend team: which means, working on new additions for our observability, ingesting or integrating a new connector, fixing problems on parts of the product already identified, or adding new capabilities for any user-facing analytics use case. Or, working at the Fast Responders team, which is a team where different members of the Product team work on fixing problems reported by our customers, improving or monitoring features we have just released, or removing some technical debt we identified.We discuss the product pretty much every day. It needs to balance today's problems with tomorrow's, so the vision of someone working with the product to fix real problems is crucial, but the outlook of someone who knows the internals is invaluable to making the right long-term decisions.Our product design approach is to work backward: someone proposes a solution to a problem, explains why it's important, describes how it would work, and writes (but doesn't yet publish) the announcement blog post. Then, everyone else reads it, asks questions, and we decide if that makes sense or not. You'll be part of this, of course. Typically, we build what we call an MSP ("Minimum Shitty Prototype") that enables us to see very roughly how it would work and to understand the real effort involved in actually shipping it.Some bits about the way we workWe are a fully remote company, all of our previous companies were remote-friendly companies, and we intend to remain a remote company.Our head office is located in Madrid; we love to see each other and work face to face regularly, feel free to go whenever it suits you