Lead DevOps Engineer

Traditional industrial manufacturing systems were built for predictability. Supply chains no longer are. Today, real-time data is buried in legacy tools that weren't designed for constant disruption. By the time an issue surfaces, it has already snowballed, sending everyone into firefighting mode. Pelico exists to close the gap between production plans and the daily reality on the factory floor.

We've built the manufacturing orchestration platform trusted by the world's most complex industrial operations : companies like Airbus, Boeing, Safran, Eaton, and Cartier. Our AI connects fragmented supply chain, production, and quality data into a single live operational picture — then puts AI agents to work anticipating disruptions, simulating recovery options, and keeping every team aligned before small problems become expensive ones.

Founded in 2019 and backed by General Catalyst, 83

North, and Serena, we've raised $72M and are growing fast — 300% year-over-year revenue growth, deployed in 15+ countries, and supporting factories worldwide. We're headquartered in Paris, with offices in Miami, London and Amsterdam, and we're just getting started.

This is a rare chance to join a company that's redefining an industry that hasn't been disrupted in decades — from the inside.

About the Role

• Pelico runs as an elegant set of ~20 microservices that deploy on a single VM — and scale to Kubernetes for the enterprise. As we grow in the US, our most important deployments are also our hardest: aerospace and defense customers who run Pelico on their own air-gapped, on‑premise infrastructure — where their IT team operates the product and we have no access to the cluster, the logs, or the data.

• You'll own that frontier. You'll lead a small Dev Ops team (≈3–5) and own how Pelico is packaged, deployed, and operated in environments we can't see — so a customer's IT team can stand it up, run it, diagnose it, and recover it on their own, while we still hit every commitment we make. This is a player‑coach role: hands‑on in the infrastructure, in the room with customer IT, and accountable for delivery.

• Over the next 12–18 months you'll drive two co-primary tracks: the on‑prem deployment frontier — tooling and packaging that get Pelico's current and committed enterprise customers live and self‑operable, repeatably, not bespoke — and a federal posture, standing up Gov Cloud / FedRAMP (controls as code) so Pelico can serve federal and defense customers on certified infrastructure. The federal track is the most probable near‑term direction, not a distant maybe.

Your Mission

• Make it operable without us. Design the observability and self‑remediation story for air‑gapped, customer‑run environments — shipped diagnostics, remediation playbooks, health checks, alert auto‑classification. Go deep: auto‑diagnose and auto‑remediate, not just "rerun the pipeline."

• Package it for any environment. Build the Helm charts, Compose stacks, and Terraform/IaC for Pelico's real deployment variants — on‑prem single-VM, air‑gapped Kubernetes, and private‑cloud (GKE/GKS, EKS, AKS) — deployable by customer IT with clean runbooks.

• Deliver on the commitment. Turn an enterprise deliverable — "ship a GKS Helm chart in a month, with three people" — into a roadmap with weekly checkpoints, MVP scope, and a date you hit.

• Make it repeatable — and federal‑ready. Turn bespoke deployments into repeatable tooling that gets current and committed customers live without heroics — and stand up Pelico's federal posture (Gov Cloud / FedRAMP, controls as code), now a co‑primary track and the most probable near‑term direction.

• Set the boundary. Sit with customer IT and security months ahead, agree the RACI and SLAs, and draw an unambiguous line between what's…