Test Engineer

About Linro

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.

The role

You would be our dedicated quality engineer, working with the engineering team. Linro runs across many plugins and integrations, and at its core a policy engine decides whether a cloud change is compliant. If it decides wrong, a customer either ships a change that fails their audit or gets blocked for no good reason. You build and own the process that proves it all works: the test strategy, an automated regression suite for the core engine and every plugin and integration, and the quality gates between AI-written code and production. Automation first, manual testing where it makes more sense.

What you will do

• Own the test strategy and the regression platform: nightly, pre-release and production runs against live installs, with reporting people trust and a clear line between environment noise and real regressions. We use Playwright today; the tooling is your call as long as it works and is easy to operate.

• Own the correctness of the policy engine: build a reference set of test cases with known expected results, plus property-based and differential tests, so policies evaluate the same way across past, present and simulated future state.

• Run the test environments: real sandbox cloud accounts, cloud emulators, capacity and cost per environment.

• Own the CI quality gates in GitHub Actions, and review the tests and changes our AI coding agents produce.

• Extend coverage across the web frontend (components and user flows), the plugins and integrations, the MCP server and the guardrails agents call, including basic security testing.