Back to jobs

Senior Forward Deployed Engineer - Germany

Pay
Pay not listed
Work setting
Hybrid — work setting source
How we work 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. What we offer
Location type: Hybrid
From the employer’s posting
Employment
Full-time — employment source
Employment type: Full-time
From the employer’s posting
Team
Engineering — team source
Department: Engineering
From the employer’s posting

What you’ll work on

Full posting
  • Deploy into customer clouds: connect the cloud org, set least-privilege access, and install sensors

  • Operate the install fleet: define health, alert on it, and run upgrades and maintenance windows

  • Lead incidents in customer environments and write postmortems

  • Turn one-off setups into repeatable Terraform modules, Helm values and runbooks

  • Write and tune SQL-based policies mapped to SOC 2, ISO 27001, NIS2 and DORA

From the employer’s posting
connect the customer's cloud organization, set up least-privilege access, deploy sensors
define what healthy means for each install, alert on it, and run upgrades and maintenance windows
Lead incidents in customer environments: debug across their network, identity and cluster setup
Turn one-off setups into repeatable ones: Terraform modules, Helm values, runbooks and install playbooks
Write and tune SQL-based policies and policy packs mapped to each customer's frameworks (SOC 2, ISO 27001, NIS2, DORA)

What you’ll bring

All qualifications

Core experience

  • 5+ years operating production cloud infrastructure as an SRE, platform or infrastructure engineer.
  • 3+ years of production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts in clusters you do not administer.
Qualification wording
5+ years operating production cloud infrastructure as an SRE, platform or infrastructure engineer. Part of that in environments you did not own: customer deployments, consulting, or a platform team serving many internal teams.
3+ years of production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts in clusters you do not administer.

Benefits in the posting

Full benefits wording
  • The honest version
  • 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.

From the employer’s posting.

About Linro

Linro is a Berlin-based cloud security company building a real-time, agentic cloud-security platform.

In the employer’s words · Read in context · Company website ↗

Apply at Linro

Posting record

Report an error

Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 20263 days ago
Recorded sightings
4
Last seen by us
Nov 21, 2026
Employer says posted
Oct 12, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 3

Similar jobs usually come down between day 3 and day 42.

From 633 similar postings that came down. Coming down is not always a hire.

Linro is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • AWS
  • Azure
  • GCP
  • Grafana
  • Kubernetes
  • Terraform
  • Go
Where the posting names them
- Restricted-network experience: proxies, private connectivity, data residency, self-hosted or in-cluster installs. - Go or Python. You write real code for tooling and integrations, read Go services, and are comfortable with SQL and APIs. - Observability and incident ownership: symptom-based alerting with Prometheus, Grafana or OpenTelemetry, and experience leading production incidents.
- Wire Linro guardrails into the customer's Terraform and CI/CD workflows, and into their AI coding agents through MCP. - 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. - Close the loop: structured feedback to product and engineering, and a seat in scoping calls so that what we promise is what installs.
- 5+ years operating production cloud infrastructure as an SRE, platform or infrastructure engineer. Part of that in environments you did not own: customer deployments, consulting, or a platform team serving many internal teams. - Deep, hands-on operation of at least one of AWS, GCP or Azure, and working knowledge of a second. Deep means you have run it, not just deployed to it: organization and account structure, cross-account identity and access, private networking, audit logging, and the failure modes. You can justify every permission you ask a customer for. We go into depth on this in the interviews. - 3+ years of production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts in clusters you do not administer.
Nice to have - Production experience on more than one of AWS, GCP and Azure. - Shipping and upgrading software in customer-run environments as a vendor.
- Go or Python. You write real code for tooling and integrations, read Go services, and are comfortable with SQL and APIs. - Observability and incident ownership: symptom-based alerting with Prometheus, Grafana or OpenTelemetry, and experience leading production incidents. - You can work with customers. You explain trade-offs clearly to engineers and executives, set honest expectations, and understand change management, approvals and audit processes well enough to fit Linro into them. Fluent English.
- Deep, hands-on operation of at least one of AWS, GCP or Azure, and working knowledge of a second. Deep means you have run it, not just deployed to it: organization and account structure, cross-account identity and access, private networking, audit logging, and the failure modes. You can justify every permission you ask a customer for. We go into depth on this in the interviews. - 3+ years of production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts in clusters you do not administer. - Terraform in multi-account, multi-environment setups, with CI/CD and short-lived credentials.
- Lead incidents in customer environments: debug across their network, identity and cluster setup, often with limited access. Fix what you can, hand reproducible findings to engineering, and write postmortems that change something. - Turn one-off setups into repeatable ones: Terraform modules, Helm values, runbooks and install playbooks, so each new customer takes less effort than the last. - Wire Linro guardrails into the customer's Terraform and CI/CD workflows, and into their AI coding agents through MCP.
- Turn one-off setups into repeatable ones: Terraform modules, Helm values, runbooks and install playbooks, so each new customer takes less effort than the last. - Wire Linro guardrails into the customer's Terraform and CI/CD workflows, and into their AI coding agents through MCP. - 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.
- 3+ years of production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts in clusters you do not administer. - Terraform in multi-account, multi-environment setups, with CI/CD and short-lived credentials. - Restricted-network experience: proxies, private connectivity, data residency, self-hosted or in-cluster installs.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

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, with an office in Berlin and a team across Europe, Linro has a platform that's real and working, with plenty still to shape.

The role

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.

What you will do

  • Deploy into environments you did not design: connect the customer's cloud organization, set up least-privilege access, deploy sensors (managed, or inside the customer's own cluster) and get to a first blocked change fast.

  • Operate the install fleet: define what healthy means for each install, alert on it, and run upgrades and maintenance windows that fit the customer's change process. You know an install is unhealthy before the customer does.

  • Lead incidents in customer environments: debug across their network, identity and cluster setup, often with limited access. Fix what you can, hand reproducible findings to engineering, and write postmortems that change something.

  • Turn one-off setups into repeatable ones: Terraform modules, Helm values, runbooks and install playbooks, so each new customer takes less effort than the last.

  • Wire Linro guardrails into the customer's Terraform and CI/CD workflows, and into their AI coding agents through MCP.

  • 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.

  • Close the loop: structured feedback to product and engineering, and a seat in scoping calls so that what we promise is what installs.

What we are looking for

  • 5+ years operating production cloud infrastructure as an SRE, platform or infrastructure engineer. Part of that in environments you did not own: customer deployments, consulting, or a platform team serving many internal teams.

  • Deep, hands-on operation of at least one of AWS, GCP or Azure, and working knowledge of a second. Deep means you have run it, not just deployed to it: organization and account structure, cross-account identity and access, private networking, audit logging, and the failure modes. You can justify every permission you ask a customer for. We go into depth on this in the interviews.

  • 3+ years of production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts in clusters you do not administer.

  • Terraform in multi-account, multi-environment setups, with CI/CD and short-lived credentials.

  • Restricted-network experience: proxies, private connectivity, data residency, self-hosted or in-cluster installs.

  • Go or Python. You write real code for tooling and integrations, read Go services, and are comfortable with SQL and APIs.

  • Observability and incident ownership: symptom-based alerting with Prometheus, Grafana or OpenTelemetry, and experience leading production incidents.

  • You can work with customers. You explain trade-offs clearly to engineers and executives, set honest expectations, and understand change management, approvals and audit processes well enough to fit Linro into them. Fluent English.

  • You use AI coding agents daily, including for infrastructure changes, have hands-on MCP experience, and know where to trust them and where to check their output.

  • Open to travel to customers across Europe and the US, up to roughly a quarter of your time.

Nice to have

  • Production experience on more than one of AWS, GCP and Azure.

  • Shipping and upgrading software in customer-run environments as a vendor.

  • Turning compliance frameworks (SOC 2, ISO 27001, NIS2, DORA) into concrete controls.

  • Policy-as-code (OPA/Rego, Sentinel, Cedar) or CSPM tooling.

  • Previous forward deployed, solutions engineering or consulting work.

How we work

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.

What we offer

  • Real ownership. You own every customer deployment and how it runs, with direct access to the founders and to the engineers who built what you are operating.

  • 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 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.

Demand for Forward Deployed Engineer roles

New Forward Deployed Engineer postings at the employers we follow are up 225% over the last 6 weeks compared with the 6 before.

Weekly new Forward Deployed Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 51, the most 267, and the latest week had 217.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Forward Deployed Engineer, by the work the posting describes.

Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.

Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.

An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Germany

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. What you will do
More source context
How we work 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. What we offer
Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.