Backend Engineer - Remote Germany

Job description

About Linro is a cloud security company building a real-time, agentic cloud-security platform. Teams ship with AI. AI ships with Linro. Cloud infrastructure changes constantly, and increasingly it's AI agents making those changes, not people. Most security tools only catch problems after the fact. Linro works differently. We enforce what's allowed at every stage, from commit to production. We stop bad changes before they ship, and fix problems in real time once they're live. We have each been on the receiving end of this problem: running cloud security at scale, building the platforms underneath it, and shipping in regulated systems where a wrong change isn't an option. Founded in Berlin in 2026 and built fully remote across Europe, Linro has a platform that's real and working, with plenty still to shape. The role You would be one of our first engineers, building alongside the founding team. At the heart of the product is a stream-first policy engine that evaluates compliance as SQL across past, present and future infrastructure state. It has to be fast, correct and impossible to route around. You'd own large parts of it outright. What you will do Design and build core backend services in Go that evaluate policy against cloud infrastructure changes in real time. Take a core area of the platform and own it end to end, from first design through running it in production. Build the simulation and enforcement path that blocks or auto-remediates non-compliant changes before they reach production. Stay close to customers, see how your work lands in the real world, and fold what you learn back into the product. What we are looking for Strong backend engineering experience in a compiled, statically typed language (Go, Rust, Java, C++, C#, or similar). We build in Go , so you are either already a Go engineer or someone who will get into it quickly. You know SQL well and think naturally in relational and columnar data models. It’s central to how our engine works. A product mindset. You care about the user and the problem, not only the ticket, and you have opinions about what to build, not just how. A problem-to-solution instinct. You can take an ambiguous problem, find the simple core, and ship something that solves it. End-to-end ownership. You own a problem from design through production and operation, and you see the hard parts through. Hands-on experience operatin…