Backend Engineer

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 operating and running at least one major cloud (AWS, GCP or Azure). Not just deploying to it, actually running it: access management, networking or the failure modes.
• Hands-on with Terraform or Pulumi, and an understanding of how infrastructure-as-code actually behaves in practice.
• You build with AI coding tools as a normal part of your workflow and have a point of view on where they help and where they don't. We build guardrails for these tools, so we want engineers with deep, hands-on experience in agentic development.

Nice to have

• Background in cloud or cyber security, CSPM, CNAPP, or compliance (e.g. SOC 2, PCI, ISO 27001, GDPR).
• Experience building policy or rule engines.
• Experience with high-availability, scaling, and eventually-consistent, event-driven system design.
• Production experience running Kubernetes clusters.
• Early-stage startup experience, or having been a founding engineer before.

How we work

We are 100% remote across Europe and hire anywhere within roughly two hours of Central European Time (CEST). We get the whole team together in person somewhere in Europe once a quarter for a few days. We work async by default, write things down, and protect people's focus time.

What we offer

• Real ownership.As an early engineer you design, ship, run and own a genuine surface area of the product, with direct contact with users and a say in how we build.
• Meaningful equity. You are an early employee, and your stake reflects it.
• Competitive salary,benchmarked to the market.
• A quarterly European offsite, and a team that takes both the mission and each other’s time seriously.

The honest version

This is early. Priorities will shift, and some of what you build early will change as we learn. There is no playbook waiting for you. If you want a highly structured environment with a mature codebase and a clear roadmap for the next two years, this is not it. If you want to shape a product and a category from close to the start, and you like the idea of building the thing that keeps AI agents from breaking production, we should talk.