About this role

Backend Engineer Linro GmbH Daily tasks: - 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.

Musts: Golang, SQL 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. 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.

Source listing: nofluffjobs_main