Senior Platform Engineer (F/H)
We are looking for a Senior Platform Engineer to own and shape the infrastructure behind Fabriq, used every day on more than 600 industrial sites in 43 countries.
The Platform team runs this infrastructure end to end, with a strong DevOps and SRE culture. Product engineers deploy their code and own what runs in production. The team builds everything underneath, so that every service deploys automatically, scales automatically and simply works. You will work on a modern stack (Kubernetes on AWS, Pulumi, GitOps, OpenTelemetry), with real freedom to make it even better.
The next chapters are exciting. The team will bring its GitOps setup to state of the art and extend ephemeral environments to every pull request across the whole stack. Within the next 12 months, it will also run AI agents in production on Fabriq's own cloud, both inside the product and for internal needs.
As a senior individual contributor, you will own major projects end to end, from spotting a problem to delivering the solution. You will share responsibility for reliability, security, performance and cost, and your expertise will directly shape the team's technical choices. At Fabriq, a good idea backed by expertise gets implemented, and fast.
Your team
You will join a small team of experienced platform engineers, currently managed by Yacine, our VP Technology.
The team works with a high level of delegation. The manager acts as an advisor, and engineers make the decisions on their own scope. The only rule is to ask for advice and keep people informed. We value engineers who bring expertise and share their opinions, and those opinions are usually followed.
The team works on the same rhythm as our product units: dailies, monthly cycles and retrospectives. Fabriq is growing and its organization keeps evolving. That gives strong engineers real room to grow toward technical leadership or management.
Our stack
Back-end Our backend is primarily implemented in TypeScript and in Python (with the framework Django). The database technology is AWS Aurora with Postgres compatibility, for both TypeScript and Django servers. With TypeScript, we use Drizzle as a lightweight ORM. Our coding style in TypeScript is inspired by data-oriented programming. For observability, we use Honeycomb and Sentry.
Front-end Our web app is a single-page application in Vue.js, written in TypeScript. The front-end application is continuously deployed with Cloudflare Pages, which allows for preview URLs on pull requests. We use Claap to share videos of our work and Sentry to log errors. We also have a mobile application, developed with Vue.js and Capacitor. We have our own components library, based on our design system, called Forma.
Infrastructure The servers run as containers on Kubernetes, specifically EKS on AWS. Deployments follow a GitOps approach. Resources outside Kubernetes are managed with Pulumi, with some legacy on CDKTF (we migrate resources from CDKTF to Pulumi when we need to change them). A small number of customers have dedicated infrastructures. We also support on-premise deployments using Kubernetes operators, alongside a deployment toolkit built with Nix. For monitoring the infrastructure, we also use Honeycomb, built on OpenTelemetry.
What we expect from the role
Building the infrastructure
Design, implement and operate infrastructure on AWS through automation and infrastructure-as-code Bring our GitOps setup to state of the art, which is the team's short-term focus Extend ephemeral environments on pull requests to the whole stack, so every engineer can test a change end to end before merging it Prepare our cloud to run AI agents in production within the next 12 months, both inside the Fabriq product and for our internal needs Drive operational excellence over the long run, with everything automated, reliable and observable
Owning production
Own the reliability, security, performance and cost of our infrastructure, together with the team Strengthen monitoring, alerting and observability, and take part in troubleshooting production issues Design with on-premise constraints in mind: supporting on-premise customers means we self-host and run in-house many components we could otherwise buy as SaaS
Working with the team and the org
Own topics end to end: spot problems, propose solutions and deliver them Review your teammates' work and pair program with them, as pairing is part of our daily engineering culture Make infrastructure understandable for the rest of the engineering department, through clear documentation and technical decisions Bring new ideas: when you know a better tool or practice, you champion it