Product Engineer

We’re looking for a product engineer who is comfortable with both front and back end programming, and wants to be involved in the full scope of what gets built. This means constantly improving our supply chain traceability, mass balance, and digital product passport platform, shaping requirements, talking to users, and seeing things through production.

We’re a fast-paced startup in a dynamic industry. Our engineers are required to deliver features from conception to final product, requiring good communication skills, organisation, and attention to detail. You’ll write product specs, make design and technical decisions, and take features from a problem brief all the way to production — with product managers available for strategy and context, but without them driving day-to-day decisions. 

In practice, a typical week looks like this: a 15-minute standup each morning, a product and engineering demo every two weeks, and otherwise uninterrupted time to build. The engineering team is small, and we talk directly to customers when needed. Here is what a typical calendar looks like:

• Build frontend and backend features — React components, REST API endpoints, database design — depending on what the feature needs.
• Take features from problem definition to production: scoping, building, testing, shipping.
• Work with customer success, sales, and product teams, and talk to users, to understand what to build before building it.
• Write code that is tested and readable.
• Review other people’s code to give and receive honest feedback.
• Come into our office in The Hague once a week.

• You’re a strong coder. The technologies matter less than your ability to read an unfamiliar codebase, find bugs, and write code other people can maintain.
• You’ve worked at a startup or early-stage company, or somewhere without much structure, and got things done.
• You think about users when you build things. You want to understand the problem, not just get to building.
• You say what you think. If you think something is being built the wrong way, you make the case.
• You communicate well with people across the team — engineers, product managers, and customers. A lot of that happens in writing, so being clear and concise matters.
• You’re based in the Netherlands or the EU and can get to The Hague roughly once a week (not a requirement).

Our current stack for reference. We don’t require prior experience with it — most of our engineers have switched languages or platforms before:

• TypeScript (frontend and backend)
• React and Next.js
• Node.js
• MySQL
• Git
• Styled components

Our interview process is three rounds:

• Introduction call with HR (30m)
• Technical live assessment with 2 developers (2h)
• Culture fit interview with 2 teammates (1h, can either be immediately after the technical stage or on a different day)