About Pelico

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, 83North, 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 Platform squads

Pelico is a configuration-driven, AI-native platform: a field engineer stands up a running factory application by authoring YAML — schema, algorithms, widgets, actions, agents — instead of writing code. The Platform squads build the reusable blocks that make that possible, and we run them as a product: our customers are other engineers — the Solution squads, our Regional Solution Engineering pods, and customer AI teams building on top of us.

You'll lead one squad — the configurability framework, the compute layer, the widget surface, the agent-development substrate (MCP/LSP/harness/BYOM), the integration layer, or the end-user Copilot — owning a capability cluster the whole company builds on.

Your mission

You'll own a platform capability end to end — and ship it yourself:

1. Build the substrate. Author the framework, SPI, runtime, or AI tooling other squads depend on, and review the rest at architectural depth.

2. Run it as a product. Own the roadmap, the contracts your consumers rely on, the adoption metric, and the deprecation policy that keeps the surface clean.

3. Set the bar. Author specs, run the spec-driven workflow, and stand up the eval and review gates that make agent-authored code trustworthy.

4. Harvest the field. Turn recurring customer patterns into platform capabilities, so learning compounds instead of fragmenting into bespoke forks.