System & Infrastructure Engineer

Hybrid

• Ghent, Belgium

Polysense builds operational intelligence software for food manufacturers. Companies like Agristo, Lotus Biscoff, and La Lorraine already run on it.

Our engineers build that on infrastructure we run ourselves: on-prem CPU and GPU servers, a basic Kubernetes cluster, our own CI and ML training runners, and cloud VMs on AWS and Azure. On top of that runs a lot of internal tooling, some built by us and some open source.

It grew fast. Now it needs an owner.

That's you. You own our infrastructure end to end, fix things properly instead of patching them, and lay the security foundations along the way. You report directly to the CTO/co-founder, and the learning curve is as steep as you want it to be.

Mission: own Polysense's infrastructure end to end, so engineering stops firefighting and gets back to building.

What You'll Be Doing

• Own the infrastructure, top priority: servers, CI and training runners, cloud VMs, and the internal tools – including spinning up extra compute when a big training run or GenAI experiment needs it. When something breaks, it's yours, and you make sure it never breaks the same way twice.
• From firefighting to fixing: a training runner’s disk fills up and nobody can train models. A kernel update breaks GPU drivers. Right now both get a quick manual fix – you solve why they keep happening.
• Automate, AI-first: scripts, Terraform, Ansible, AI agents – repeatability and automation are your defaults for anything repetitive. You can fully offload eng-to-end tasks to agents, but also know when something is still too risky to hand off.
• Access, organized: GitHub and Azure access is managed by hand today. You build a clear role structure, so granting or revoking access takes minutes and nobody is left waiting.
• Security foundations: you help build the real technical controls behind our ISO 27001 and SOC 2 path. You’re the builder, not the auditor.

Not in scope: day-to-day laptop setup and new-hire onboarding. That's a pre‑configured IT pipeline, not yours.

Key point: we’re not looking for someone who’s seen it all. We’re looking for someone who wants to own it all, and learns fast doing it.

What You Bring

• A solid technical base: Linux, the command line, scripting in Bash or Python. You can debug and chase a root cause.
• Some hands‑on experience keeping systems running. A first job, an internship, side projects, a homelab you’re slightly too proud of: it all counts.
• Experience with, or real curiosity about, Docker, Kubernetes, cloud (AWS/Azure) and infrastructure‑as‑code like Ansible.
• An AI‑native way of working: setting up agents and automation to handle tasks is your default.
• Early career is fine: roughly 0–3 years of experience.
• Bonus points: exposure to ISO 27001 or SOC 2, a compliance platform like Vanta, GPU servers and Nvidia drivers, virtualization or storage setups, or networking basics.
• Not required: senior‑level experience, certifications, or audit and legal compliance work.

Mindset & way of working

• Ownership by default: when something breaks, you don’t wait for someone to assign it to you.
• Hungry for the steep curve: you want a fast-paced environment where you learn something new every week. That energizes you, it doesn’t scare you.
• Fix it, then fix why: a band aid never quite satisfies you. You want the real fix.

There's real room to grow here: toward senior infrastructure or platform work, or deeper into security. We're not locking you into one lane.

What Success Looks Like

• Month 1: you know the landscape. Every server, runner and VM, and where the docs are missing.
• Day 60: the recurring fires, like full disks and broken GPU drivers, have a real fix instead of manual cleanup.
• Day 90: engineering comes to you first with infra questions, and fewer of them reach engineering leadership.
• GitHub and Azure access has a clear role structure. Granting or revoking it is quick.
• Year 1: the firefighting load has clearly dropped, and you've got your own read on what to build or own next.

The Perks, What's in it for you?

• Real ownership: it's your infrastructure, not a ticket queue.
• A steep learning curve: GPU servers, Kubernetes, cloud and security in one role, with a team that backs you while you figure it out.
• Direct line to the CTO/co-founder: no layers between you and the people deciding where this goes.
• Ambitious, no-ego team: people aim high, dare to fail, and pick up whatever needs doing.
• Competitive salary in line with industry benchmarks, a full benefits package and a company car.

Why Polysense?

People join a company like Polysense for the impact they can hav