Senior AI Product Engineer (Full-Stack)

Amsterdam - Hybrid (minimum 50% at the office)

⏱ 36-40 hours per week

€4,900–€5,600 gross per month, based on 40 hours and depending on experience

Futurewhiz is a B Corp

Just a small heads-up regarding logistics: we aren't able to offer visa sponsorship for this role, so we can only consider candidates who already hold a valid work permit for the Netherlands or the EU.

Generative AI can create textbook content in seconds. Producing content that is accurate, curriculum-aligned, editable and trusted by authors and editors, and doing so reliably at scale, is much harder. That is the challenge you will help us solve.

Futurewhiz is looking for a Senior AI Product Engineer to help turn promising AI experiments into dependable software for real publishing workflows. You will remain deeply hands-on while taking broader responsibility for technical direction, architecture and the path from an uncertain opportunity to a durable product.

This is not a role where product decisions arrive as fully specified tickets. You will work with editorial and technical colleagues to frame problems, test assumptions and decide what is worth building. Seniority here means sound judgement, independent ownership and the ability to make the wider team more effective—not status, people management or knowing every technology in advance.

About Futurewhiz

For nearly 15 years, Futurewhiz has been the market leader in EdTech in the Netherlands. Our brands – including Squla and StudyGo – help children and teenagers aged 3 to 18 learn and grow at their own level and pace. Our mission is clear: "Empowering every child to grow." We’ve been a certified B Corp since 2020, which means we strive for a strong balance between purpose and profit.

What will you do?

You will join the Futurewhiz Content Automation team and work closely with software engineers, editorial specialists and colleagues at a major educational publisher. Together, you will improve the workflows used to create and maintain high-quality learning materials, including textbooks and digital content.

Each cross-functional team focuses on a particular part of the publishing workflow. The team studies where time, quality or cost is being lost; tests possible improvements with users; and builds the solutions that show the most promise. Once the best opportunities in one area have been addressed, the team may move to another part of the workflow.

Your editorial colleague will lead much of the specialist research, such as interviewing authors and editors, testing editorial concepts and mapping publishing workflows. You will participate where technical insight, feasibility testing or rapid prototyping is valuable, while owning the technical approach and ensuring the resulting software can succeed beyond the prototype stage.

Specifically, you will:

• Own the technical direction for an AI-assisted product area from early discovery through production operation
• Build across the stack: Python services and APIs, data flows, user-facing interfaces and the infrastructure needed to run them
• Design robust LLM and agent-based workflows, including prompts, evaluations, feedback loops, observability and safeguards
• Translate editorial research and user feedback into technical options, trade-offs and testable plans
• Identify the smallest useful experiments that can resolve important technical or product uncertainty
• Create architectures that support rapid learning now without preventing the strongest ideas from becoming durable products
• Develop reusable platform capabilities and integration patterns that can support multiple content workflows
• Set pragmatic standards for reliability, security, maintainability, quality and cost—and help the team apply them
• Use AI coding tools fluently while critically reviewing their output and remaining accountable for the software you ship
• Anticipate dependencies, investigate difficult failures across components and keep production systems effective as usage grows
• Raise the engineering bar through design discussions, code reviews, pairing and informal mentoring
• Navigate technical trade-offs with both technical and non-technical stakeholders, including when priorities or perspectives differ
• Travel to Groningen for one or two days approximately once every two months to work with colleagues there

There is no separate team waiting to take over UX, infrastructure or operations. You will have colleagues to consult, but the product team owns its solutions end to end. Part of your role is helping the team keep that ownership manageable through simple architecture and good engineering choices.

What success looks like

In your first three months, we would expect you to:

• Build a strong understanding of the users, workflow, technical environment and existing experiments in your initial problem area
• Establish a clear technical direction based on the most important evidence and uncertainties
• Ship and …