.Engineers are the backbone of all we do at Pleo. Without these wildly brilliant people, we don't have a thing. We are looking for experienced Backend Engineers to join one of our cross-functional product teams.As a Senior, we trust you to be an expert in server-side languages. Kotlin is 90%+ of our micro-services, so proficiency here is hugely beneficial. Beyond writing excellent, well-tested, maintainable code, you also practice the other aspects of being a strong technical leader. You give insightful PR reviews, are a trusted technical partner to teammates, know when/how to prioritize tech debt, proactively jump into P1/P2 incidents, lead post-mortems, and can generally upskill and unblock the team around you.But it's not just about being a master of your craft; it's about ownership and taking the lead on large projects. These could be new product launches, managing tricky migrations, and designing and building new microservices or components.As a scale-up, we sometimes need to shift focus. When that happens, your role is to be a steady hand to help the team navigate ambiguity and manage technical change.Mostly, we're looking for someone others can look up to and learn from. You'll set the standard for the team, not just with your code but in how you work and the culture you promote. At Pleo, our people and our culture are very important to us, and we value trust and transparency like you wouldn't believe.As we continue to grow at Pleo, we're excited to welcome talented Backend Engineers to join us across our various domains, including Platform and Services, Partnerships, SMB, Credit, and more. While the specific team you'll be working with will be decided later, our hiring process remains streamlined and consistent across all roles. This allows us to evaluate your skills and potential, ensuring a great fit for the team you eventually join. No matter which domain you land in, you will be part of a dynamic, collaborative environment where you'll tackle complex challenges, build reusable components, and contribute to shaping the future of our product.You know your way aroundServer-side languages (we mostly use Kotlin, with few services in TypeScript)Relational databases (e.G
