This is not a research role and it is not model training. You build the layer that turns a language model into something a business can rely on: retrieval over a client's own documents, agents that finish a task, evaluations that prove it works, and explicit boundaries on what a model may assume. We focus on four models: Claude, OpenAI, Gemini and Mistral, and we keep testing which one fits a given task rather than assuming it.
The Eindhoven side of this role has a second half: you sit close to the client. You are in the room when a business problem is described, you judge whether AI is genuinely the right answer, and you say so when it is not. Then you build it together with the engineers in Jakarta. The seat exists because translating a business problem into a system that behaves predictably is the part nobody can outsource.
We care more about the foundation of a solution than about the speed of the first demo. That means data models and architecture that still hold up in three years. It also means governance, compliance and traceability are designed in from the start instead of bolted on afterwards. When we put agents to work, we record what they did and why, so a decision can always be reconstructed and a client can always be shown the trail. Anyone can get a prototype running. Building something a business can still rely on in two years is the actual job.
Concretely, and starting from the client rather than from us: what we build on depends on the stack they already run and on what will integrate cleanly with it. Where we are free to choose, the default is a TypeScript and Node.js application layer, with the Vercel AI SDK and direct provider APIs on top of Claude, OpenAI, Gemini and Mistral. Azure AI Foundry is what we build business and enterprise applications on, because that is where governance and stability have to be guaranteed rather than argued for afterwards. Python turns up wherever a data or evaluation job is better served by it, PostgreSQL with vector search sits behind retrieval, and React with TypeScript and Tailwind covers the front end. Automation that does not deserve a codebase runs on n8n. You will not have touched all of it, nobody here has, and part of the job is judging when our default is the wrong answer for a particular client.
You work in one team with our engineers in Jakarta, with fixed overlap hours so the working day is genuinely shared rather than handed over. That means your job is never to write a specification and throw it across a timezone: you build alongside them. Lines are short, with no account managers, no steering committees, and direct contact with the founders on the decisions that matter. Travelling to Jakarta to work with the team on site is a normal part of the role, not a reward. We hold ourselves to the same standard we sell: our own daily operations get improved alongside client work, and when something we built ourselves stops holding up we rebuild it rather than patch around it.
Where we are right now, so you can judge what you are joining: the Jakarta hub is expanding, and our clients are in the Benelux and the wider EU. That is where the focus sits. Our Dutch engineers sit with the client and build the work together with the team in Jakarta, on the same day rather than across a handover, because what we are working towards is being the technology partner a client trusts with the things that matter rather than a supplier you send a specification to. Growing into the Indonesian market comes after that, and the first commercial seat in Jakarta is where it starts. You arrive while all of this is still taking shape.
You speak with the people you would actually work with, not a screening layer that passes you on. The process is the same in Eindhoven and in Jakarta, and from your application to an offer takes three to four weeks.
The founders
Why us, why you, and whether we mean the same thing.
The Tech Lead
The work itself: the substance of the role, and what you would actually be doing in it.
A teammate
Someone you would work with daily, not the person who would manage you.
Bring something you built to that second conversation and walk us through it. It is not an extra round and not a puzzle we invented: it is that conversation. A side project, something from work you are allowed to show, a repository you are proud of. If everything you have built sits behind an NDA, tell us and we will find another way.
AI Application Engineer
Questions about this role?
Talk to us