DevOps Engineer

Filics' mission is to reinvent intralogistics by creating autonomous mobile robots that fundamentally change how material moves. Our double-runner system makes Filics the first and only AMR able to drive through load carriers such as Euro pallets, breaking forklift logic and setting a new standard for efficiency. We are a small, focused team committed to solving hard problems with engineering excellence. All team members are expected to be hands‑on and to contribute directly to the company's mission. Leadership is given to those who show initiative and consistently deliver excellence. Work ethic and strong prioritization skills are important. All team members are expected to have strong communication skills. They should be able to concisely and accurately share knowledge with their teammates.

OUR CHALLENGE

Our ability to ship as a robotics company depends on the infrastructure underneath. And ours hasn't kept pace. We're not making optimal use of the compute we already have, field telemetry from our robots is scattered and hard to access, and there's no way to test software against real robot hardware inside CI.

You own the systems that close these gaps. You refactor the build infrastructure to make better use of available compute, you centralise the telemetry our robots generate in the field, and you bring real robot hardware into CI so the team can test earlier and fail faster.

YOUR ROLE

You own the developer platform end to end: the build system, the observability pipeline, and the cloud access layer that sits underneath them.

• Design and deploy Bazel RBE into our local cluster, so build capacity scales with the team and serves CI and developers from the same backend
• Build the data ingestion pipeline from robot to centralized storage, so operators can extract field data without manual steps and developers can query it without friction
• Stand up AWS credential management and cost monitoring across the engineering team, with clear ownership and visibility on spend
• Work directly with software engineers to surface build performance issues, observability gaps, and tooling friction, and prioritize fixes by where they unblock the most engineering time
• Partner with the infrastructure side of the team on hardware capacity planning, usage forecasts, and what we need to grow

Over the next 18 to 24 months, this role expands into robot deployment migration and end‑to‑end CI that validates changes all the way down to physical hardware.

REQUIREMENTS

• You have a degree in Computer Science, Software Engineering, or an equivalent track record in platform and build engineering
• You've worked hands‑on with Bazel or a comparable build system (Buck, Conan, CMake at scale) and at least one remote build execution backend (Buildbarn, EngFlow, BuildBuddy, or self‑built), including deployment and scaling
• You've built, migrated, or operated a CI system serving a sizeable engineering team
• You've designed data ingestion pipelines and the observability layer on top (dashboards, monitoring, alerting), ideally from physical devices or distributed systems
• You're strong on Linux and containerized workloads, and comfortable with hybrid on‑prem plus cloud (AWS) infrastructure
• You work directly with software engineers to scope tooling needs and explain infrastructure trade‑offs clearly to non‑platform peers