[Hiring] Test Engineer @Linro

Role Description

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
• 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.
• Own the correctness of the policy engine: build a reference set of test cases with known expected results, plus property-based and differential tests.
• 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.

Qualifications

• 4+ years in test or quality engineering for distributed backend or cloud products.
• You write and review real code. We use Go and TypeScript, but any language works.
• You use AI coding agents daily and have a view on how tests become the control layer when agents write the code.
• Strong written, async communication and the judgement to call a failure a product bug, a test bug or environment noise.
• End-to-end testing, built and operated.
• API, integration and frontend testing: gRPC or ConnectRPC services and the databases behind them, plus component and UI tests for a TypeScript web frontend.
• A strategy for correctness-critical logic: golden files, property-based and differential testing.
• Hands-on cloud, Terraform and Kubernetes with Helm, including ephemeral environments and keeping cloud cost in check.

Requirements

• You know how end-to-end tests really work across UI, APIs and the infrastructure underneath, and you have run them as pipelines yourself: nightly and pre-release runs against live environments, test data and environment setup, flaky-test handling and reporting that people trust. Playwright or similar tooling.

Nice to have

• Hands-on experience with Terraform, Kubernetes and Helm.
• Cloud control-plane or IAM knowledge, or a security testing background.
• Experience testing MCP servers or LLM-agent flows (non-deterministic evals).

Benefits

• Real ownership: you are the first dedicated quality hire, you design the strategy, own the platform and have a say in how we build.
• Meaningful equity: you are an early employee, and your stake reflects it.
• Competitive salary, benchmarked to the market.
• A quarterly European offsite, and a team that takes both the mission and each other's time seriously.

Company Description

Linro is a Berlin-based cloud security company building a real-time, agentic cloud-security platform. 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 honest version: This is early. Our regression platform is real but still being rebuilt: some environments are noisy, some tests are parked, and some coverage does not exist yet. There is no test plan waiting for you to execute. If you want a mature QA organisation with a stable framework and a ticket queue, this is not it. If you want to build the quality system for a product whose whole promise is being right, and you like the idea of keeping AI-written code honest, we should talk.