Forward Deployed Engineer (all genders) - Remote Germany or Hungary
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 2h ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 3h ago
The date the source published, not the day we noticed it (2026-10-12). Last seen at its source just now.
Is it remote?
Marked remote on the employer's board
Their board carries a remote setting on this posting — a field they filled in, not wording we read. The location field names somewhere specific, which is usually where the team or the entity sits.
Who may apply?
Germany, Hungary
The description states no restriction of its own. This is the source's own tag.
Pay not stated
Similar roles pay €91k–132.5k/yr
Middle 50% of 35 listings that do state pay — Engineering · all levels · Germany · EUR/year. This employer has published no salary; this is what comparable listings we hold disclose, never converted between currencies or periods. How this is calculated.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Ashby employer's own board first seen 2h ago · last seen just now
The listing
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 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 do
Run 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 keep false positives low.
Wire Linro guardrails into the customer's Terraform and CI/CD workflows and into their AI coding agents through MCP.
Run Linro in production at the customer: monitor, upgrade and respond when it breaks. Debug inside their environment, hand reproducible findings to engineering, and fix what you can yourself.
Close the loop: structured feedback to product and engineering, reusable playbooks for the next customer, and a seat in scoping calls so that what we promise is what installs.
What we are looking for
5 to 6+ years of customer-facing technical delivery (forward deployed or solutions engineering, SRE or platform consulting), deploying infrastructure or security software in customer environments and keeping it running afterwards.
Hands-on cloud experience: you have run real workloads, identity and access, networking and audit logging on at least one major cloud, and you pick up the others quickly.
You are a solid engineer. You write real code in Go or Python for integrations and tooling, read Go services, and are comfortable with SQL and APIs.
You use AI coding agents daily, such as Claude Code, Cursor or Codex, and have hands-on MCP experience.
You understand how companies work: change management, approvals, release and audit processes, and how to fit Linro into them.
Restricted-network experience: proxies, private networking, data residency, self-hosted or in-cluster installs.
Communication and comfort with ambiguity. You explain trade-offs clearly to engineers and executives, set honest expectations, and keep making progress when requirements are still unclear. Fluent English.
Open to travel. To customers across Europe and the US, up to roughly a quarter of your time.
Nice to have
Turning compliance frameworks (e.g. SOC 2, ISO 27001) into concrete controls.
Policy-as-code (OPA/Rego, Sentinel, Cedar) or CSPM tooling.
How we work
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 things down, and protect people's focus time.
What we offer
Real ownership. You own every customer deployment from day one, with direct access to the founders and to the engineers who built what you are deploying.
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.
The honest version
This is early. You will often be the first person to run Linro in a customer's environment, and you will write the playbooks as you go. If you want a polished onboarding process and a stable product surface, this is not it. If you want to sit between a new category and the customers who need it, and you like the idea of deploying the thing that keeps AI agents from breaking production, we should talk.