Erhalte mehr Antworten von Arbeitgebern
Versende in nur wenigen Minuten einen passgenauen Lebenslauf.
WhyBrilliant is sourcing applicants for a Senior Platform Engineer in Berlin (Hybrid) for an AI-first software platform in manufacturing. You will own the infrastructure, focusing on developer experience, GPU workloads, streaming video pipelines, and MLOps.
The role requires 8–10 years in DevOps/SRE/platform engineering, strong AWS and Terraform skills, and Kubernetes in production. Collaboration with distributed teams is essential.
WhyBrilliant is sourcing applicants for this role on behalf of a confidential company in the AI-for-manufacturing space.
Senior Platform Engineer | Berlin (Hybrid) (Also known as: Senior DevOps Engineer, Site Reliability Engineer (SRE), Infrastructure Engineer. Originally posted as "Platform Engineer (m/f/d)")
We're looking for a (Senior) Platform Engineer to own and evolve the infrastructure behind an AI-first software platform built for modern manufacturing — with a strong focus on developer experience and hands‑on work with GPU workloads, streaming video pipelines, and MLOps.
The company is building the AI-first software layer for modern manufacturing, and needs infrastructure that's both highly resilient and developer‑friendly. As Platform Engineer, you'll bridge cutting‑edge AI systems, complex video processing, and robust cloud infrastructure — keeping the engineering team shipping and debugging at high velocity. Without you, they can't scale Kubernetes clusters, optimize CDNs, or integrate MLOps workflows to support rapid growth.
Deep ownership and flexibility — engineers own outcomes without micromanagement or clock‑watching, and set their own schedule. The role is hybrid in Berlin, though most of the dev team is distributed elsewhere, so intentional remote collaboration matters. Decisions are made collaboratively with a team of staff‑level peers; the Head of Software facilitates, with the CTO looped in only for major architectural calls. Proactive builders thrive here; passive caretakers don't.
This probably isn't for you if you prefer waiting for tickets rather than proactively fixing infrastructure bottlenecks, need rigid 9-to-5 hours or hand-holding, or prefer working in isolation rather than tight cross‑team collaboration.