Product Manager (all genders) - Remote Germany

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 and built fully remote across Europe, Linro has a platform that's real and working, with plenty still to shape.

You would be our first dedicated product manager, working closely with the founders and the engineering team. You decide what we build next and in which order, across the whole product, and you ground those decisions in regular conversations with customers, from the first discovery call to the roadmap review. Clear priorities are the heart of this role: with a small team, picking the few things that matter most is what moves the product forward.

• Talk to customers and prospects yourself (CISOs, security and platform leads): run discovery calls, demo what exists, take the objections and turn feedback into a clear, ordered roadmap.

• Own priorities and the backlog: keep one ranked list across the whole product and the tools around it, decide what gets built next and what does not using explicit criteria (customer pain, pilot and revenue impact, compliance relevance, engineering cost), and re-rank it with the founders every cycle. Write the PRDs and decision memos engineers build from, and check what ships against what you promised.

• Translate what customers need into clear requirements for engineers, including how our guardrails should behave when the user is an AI coding agent: tool design, failure modes, and what an agent may change on its own.

• Own releases end to end: plan them with engineering, define what done means, write clear release notes and make sure customers understand what changed and why.

• Be the product voice in front of customers: join sales and buyer calls, present the roadmap and handle security and compliance questions (e.g. SOC 2, ISO 27001, PCI). Set success metrics and launch criteria.
  

• 5+ years as a product manager (or a founder or engineer who moved into product) on B2B infrastructure, security or developer products sold to enterprises.

• Technical fluency. You can read a Terraform plan, you have a solid grasp of databases and SQL, you understand APIs at least at a high level, and you hold your own with engineers on trade-offs.

• Hands-on customer discovery. Customer interviews and pilots you ran yourself, and a record of turning that into a few sharp bets instead of a long list.

• Prioritization and written clarity. A record of ranking competing demands with a small engineering team, using explicit criteria, and of explaining those trade-offs clearly to customers and founders. Specs and decision memos that stand on their own.

• You know the buyer: CISOs and platform leads. You are comfortable in front of customers and executives: you can run a discovery call, a demo or a roadmap session on your own and earn the room. You can map features to compliance frameworks at product level, not auditor level.

• You use AI tools daily for research, synthesis and prototyping, and have a point of view on designing for LLM agents as users.

• Policy-as-code (OPA/Rego, Sentinel, Cedar), or time at a CSPM, IaC or CI/CD vendor.

• Zero-to-one product work at an early-stage startup.

We work remotely across Europe. We get the whole team together in person somewhere in Europe once a quarter for a few days. We work async by default, write decisions down, and protect people's focus time. We use AI coding agents ourselves, so specs need to be precise enough for a person or an agent to build from.

• Real ownership. You are the first product hire, with direct contact with users and a real say in what we build and what we refuse to build.

• Meaningful equity. You are an early employee, and your stake reflects it.

• Competitive salary, benchmarked to the market (range above).

• A quarterly European offsite, and a team that takes both the mission and each other's time seriously.

This is early. You would build the product function from scratch: the roadmap process, the analytics and the way we decide are yours to shape. The founders care a lot about the product, and they want a partner who pushes back and sharpens the calls with them. Some of what you decide early will change as we learn. If you want a mature product organisation with clear processes, this is not it. If you want to define a product and a category from close to the start, and you like the idea of owning the thing that keeps AI agents from breaking production, we should talk.