You own the ground everything else stands on. Azure is our primary platform and where most of this role lives: App Service, Functions, networking, identity, and infrastructure described in Bicep. AWS and GCP turn up on client workloads that already run there, so you will work across all three, but Azure is the one we go deepest on. Docker throughout, Kubernetes where it is genuinely warranted, Vercel for the frontend layer. You decide what that platform looks like and you keep it boring; boring infrastructure is the goal, not a compromise.
This is a crucial seat in the most literal sense: when the platform is down, nobody ships. You are the person who makes deployment a non-event, who spots the cost line growing before it becomes a conversation with a client, and who makes sure a security decision is made deliberately rather than inherited by accident.
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 consultants in Eindhoven, not as a separate supplier taking orders. We keep fixed overlap hours so standups, planning and feedback happen live instead of in a comment thread you read the next morning. There are at most two links between you and the client, which means you hear why something is being built and you can push back when the reasoning does not convince you. Our founders travel to Jakarta regularly, and the team travels to the Netherlands. 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.
Cloud & Platform Engineer
Questions about this role?
Talk to us