Find your next opportunity
Browse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert rolesBrowse expert rolesBrowse fresh openings from leading companies and apply with a resume tailored to the role.
Browse expert roles13208 openings
3465-3472 of 13208
Linro
Free to start · No card · 5 credits the moment you sign up
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 one of our first infrastructure hires, taking day-to-day operation of the platform off the CTO. Linro enforces policy on other people's cloud infrastructure, so our own has to be reliable, reproducible and auditable. You own production: how Linro runs for each customer, how it upgrades, and how we know it is unhealthy before a customer does.
Own production reliability: SLOs, alerting, on-call and blameless postmortems for the control plane and every customer installation.
Make the install fleet boring: provisioning, maintenance windows and safe auto-upgrades across SaaS and self-hosted installs.
Fix the open reliability work: sensor memory ceilings and OOM visibility, ClickHouse cost and capacity, and the health of Postgres, PGMQ and Temporal.
Evolve the platform: Terraform and Terragrunt, Helm, GitHub Actions with short-lived OIDC credentials, local development (Tilt, Coder), and staging and production environments, with guardrails for humans and AI agents alike.
Produce audit-ready operations: backups, disaster recovery and continuity tests with evidence for SOC 2 and ISO 27001.
Hands-on operation of AWS, GCP or Azure in production, AWS preferred. Not just deploying to it, actually running it: accounts and access management, networking and the failure modes. We run across several clouds, so you pick up the others quickly.
3+ years running production Kubernetes with Helm, including debugging OOMs, resource limits and failed rollouts.
Terraform in multi-environment setups, with CI/CD in GitHub Actions and short-lived credentials.
Go, or Python and a wish to learn Go. You read and write code in the services you operate.
Observability and SLOs: symptom-based alerting with Prometheus, Grafana or OpenTelemetry, and the discipline to delete noisy alerts.
Production Postgres: backups, point-in-time recovery, migrations and upgrades.
Incident ownership: on-call, leading incidents and writing postmortems that change something.
Security-minded operations: least privilege, secrets handling, access reviews and audit trails.
You work with AI agents every day, including for infrastructure changes, and know where to trust them and where to check their output.
Operating Temporal, queues or ClickHouse, including cost tuning.
Shipping and upgrading software in customer-run or self-hosted environments.
Compliance operations: SOC 2, ISO 27001 or PCI DSS evidence.
Using AI coding agents safely for infrastructure work.
Early-stage startup experience, or having been a founding infrastructure engineer.
We work remotely across Europe. On-call is part of this role. We will be open about how the rotation works and compensate it. 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.
Real ownership. You own production and the platform underneath it, with direct contact with the engineers and 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.
This is early. Our infrastructure is defined as code, but parts of it are still being moved into CI, runbooks are thin, and some environments are rougher than others. You would inherit something that works, not something polished. If you want a mature platform team with a clear roadmap for the next two years, this is not it. If you want to build the operational backbone of a security product from close to the start, and you like the idea of running the thing that keeps AI agents from breaking production, we should talk.
Compensation: €75K – €93K • Offers Equity
Start with a role or skill you want to use in your next job. Use the location and role filters to narrow the results, then open a listing to review the description. A title alone rarely explains the level of responsibility, working arrangement, or experience a team needs. Compare those details before deciding which opportunities deserve a tailored application.
Employers use different titles for similar work. If an exact phrase produces no results, try a shorter title, a core skill, or an alternative name for the role. Remove one filter at a time to understand which requirement is narrowing your search. A broader search can reveal suitable work without asking you to change your actual qualifications.
For each promising listing, read the responsibilities and separate essential requirements from preferences. Note the location, schedule, employment type, and compensation when provided. Missing details are questions to confirm with the employer. A remote opening may still require a particular country, work authorization, or time-zone overlap, so check the full posting before treating it as a location-independent opportunity.
Choose a few examples that demonstrate the skills this employer names. Explain your contribution and its outcome, using accurate numbers where available. Put the most relevant experience first and keep your resume easy to scan. Avoid adding technologies, qualifications, or achievements simply because they appear in a description. Your application should make your existing strengths easier to understand.
Follow the employer’s instructions for resumes, cover letters, work samples, and screening questions. Review the exported file before submitting it: confirm that contact details are correct, text can be selected, and links reach the intended pages. A resume check can help you spot unclear writing before you apply. Its feedback is advisory and does not predict a hiring decision.
Listings are collected from external sources and may change after they appear here. The employer or recruiting destination controls whether applications are open. If an original link is unavailable, check the company’s careers page for the title or move to another opening. An employer website link is a place to check current vacancies, rather than confirmation that a particular job is still accepting applications.
Keep a simple record of the company, role, job reference, application date, and documents you sent. Record any follow-up instructions and the next action you plan to take. This makes it easier to prepare for interviews, compare opportunities, and avoid applying repeatedly to the same opening through different boards. Review your shortlist as employers update their listings and prioritize opportunities with clear requirements that match the work you want to do.