Paste your résumé. You get a résumé and a cover letter for this job, from only the facts in your résumé. Then you apply on the Linro site.
Every customer runs their cloud differently: different providers, account structures, network boundaries and change processes. Linro has to run reliably inside all of them. You take a customer from signed agreement to a working install and the first blocked change, then you operate that install: upgrades, health, incidents and tuning. It is SRE work where production is a fleet of customer environments, none of them alike, instead of one platform you control.
Our founders and go-to-market team own the commercial relationship. You own the technical one. Part of this happens on-site, where you may spend a few days at a customer's office to get an install running or work through a problem with their team. This is an engineering role, not a support or sales role, and there is no quota.
This is early. You will often be the first person to run Linro in a given kind of environment, and no two customers look alike. Runbooks are thin and you will write most of them. You will sometimes debug with less access than you want, on someone else's change calendar. If you want one production environment you fully control, or a polished onboarding process, this is not it. If you like making a security product work in messy real-world setups, and you like the idea of deploying the thing that keeps AI agents from breaking production, we should talk.
Linro is a Berlin-based cloud security company building a real-time, agentic cloud-security platform. 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, with an office in Berlin and a team across Europe, Linro has a platform that's real and working, with plenty still to shape.
This role is a hybrid setup, based in Germany. Our home is a brand-new, modern office close to Alexanderplatz in Berlin, easy to reach and built for working together. We expect you to be there from time to time. It is where we solve the hard problems at one table, and where the team gets to know each other beyond a screen. The rest of the time you work remotely or on-site with customers. Part of the team works from other European countries, and once a quarter we bring everyone together in person somewhere in Europe for a few days. We work async by default, write things down, and protect people's focus time.
€100K–€150K / yr
Posted Jul 13, 2026
Pay not posted
Posted May 21, 2026
Pay not posted
Posted today
Pay not posted
Posted Aug 21, 2026
Source: the Linro Ashby job board. We last checked this job 3 h ago. We first saw it 12 days ago. A job on a job board does not always mean that the team interviews people now. We found this job board in a public list. We did not yet compare it with the careers page of the company.
LangdockBerlin
€100K–€150K / yr
Posted Oct 16, 2026
€123K–€169K / yr
Posted Sep 23, 2026
No one has reported an interview at Linro yet. Did you interview there? Add the questions.