AI Engineer

Before you read further

Hello Print is on a mission to become the world's leading infrastructure for customizable printed products. From our offices in Rotterdam and Valencia, 120+ professionals from 20+ nationalities are building an AI-first company that scales output faster than headcount. We're at EUR 100M revenue and aiming to disrupt a trillion-dollar industry. Every hire we make needs to help get us there.

• Commercial instinct first, engineering second. You think about what something is worth before you think about how to build it.
• Full-time in Rotterdam. Five days a week, in the building where the transformation is happening. This is not negotiable.
• Always on mentality. This is not a 40-hour job; it’s a deliberate choice into something big that requires “what it takes”
• You have been building since before it was a career. Side projects, tools, systems nobody asked for. The obsession came first.
• You ship continuously. You ship fast and you ship real systems. Not prototypes, not demos.

We're rebuilding the entire platform: new frontend, new pricing engine, new content engine, new product engine, everything ready for an agentic future. No one on the team writes code manually for what these systems handle. You'll work inside this rebuild, under the direction of our founding team (Hans, CEO, and Michael, CIO/Chief AI Officer), executing on high-leverage AI problems with real commercial impact, visible immediately in revenue or cost.

There's no management layer between you and the outcome. You build, you ship, you measure, you move to the next problem.

This role is not for people who got into AI because it became important. It is for people who have been building since before anyone called it a career. The kind of person who coded as a teenager, shipped their first thing before anyone asked, and has never really stopped. Who finds it genuinely difficult to explain why they build: it is just what they do.

Who would rather spend a Sunday solving a hard systems problem than almost anything else. If you have to think about whether that description fits you, it probably does not.

This role will resonate with a specific kind of person. You will recognise yourself in one of these profiles:

• You are a strong engineer inside a startup or scale-up, shipping real features and systems, but three or four layers removed from the business decisions your work actually drives. You want to be closer to the number your code moves, not further away from it.
• Or you are building on your own: side projects, freelance work, an AI SaaS or open-source tool nobody asked you to build. You've proven you can ship alone, but you're doing it without the customer base, the data, or the stability to make it count lo Print gives you 600,000 customers to build on immediately.
• Or you are early in your career but not in your building. You've been writing code since before it paid you to, you've got real production work behind you already, and you're looking for the place that lets that intensity be the job instead of something you do around it.

The opportunity surface is large: 14 markets, 600,000 customers, a platform being rebuilt in parallel across four core engines. You'll work on problems from areas like:

• Dynamic pricing and margin optimization across markets.
• Agentic procurement: supplier selection, ordering, quality management.
• Customer journey automation from configuration to post-delivery.
• Intelligent content and SEO infrastructure at platform scale.
• Predictive demand and inventory across the supplier network.
• Internal tooling that multiplies the output of every team.

You’ve built and shipped real production systems, not just contributed to someone else’s. You’re comfortable with ambiguity and don't need a fully specified brief to start. You care about what your work is worth, not just whether it works. You want to build inside a company that’s already proven, not another 0-to-1 bet. You do not think of yourself as an AI engineer.

You think of yourself as someone who solves hard problems and builds the systems to prove it. The engineering is the method. The obsession is the identity.