Teams ship with AI.
AI ships with Linro.
Infrastructure changes constantly, and increasingly it's AI agents making the changes.
Tools that scan snapshots and flag risk after the fact can't keep up.
Linro enforces intended state across the whole lifecycle instead, from commit to runtime: MCP and pre-commit hooks at commit time, blast-radius simulation that blocks bad changes before they ship, and real-time detection, enforcement and auto-remediation in production.
Most tools tell you what's wrong.
Linro stops it.
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 roleYou would be the engineer who gets Linro running inside a customer's real environment and keeps it running.
Our founders and go-to-market team win the customer and own the commercial relationship.
You own the technical side: you take a customer from signed agreement to a working install and the first blocked change, and stay on it after go-live for upgrades, incidents and tuning.
Part of this happens on-site: you may spend a few days at a customer's office to get an install running or to work through a problem with their team.
Everything you learn goes back to engineering and product.
This is an engineering role, not a support or sales role, and there is no quota.
What you will doRun customer onboarding end to end: connect the customer's cloud accounts, whichever provider they run on, deploy sensors (managed, or inside the customer's own cluster) and get to a first blocked change fast.
Write and tune SQL-based policies and policy packs mapped to each customer's frameworks (SOC 2, ISO 27001, NIS2, DORA), and kee.