Our engineers build AI systems inside the operations of manufacturing, healthcare and finance clients. As an intern you work beside one of them on a system a client's finance or operations team depends on, and you join the calls where the business problem is explained.
You will write code that is reviewed line by line. You will also learn the part that courses leave out: why a finance team needs a payment matched in a certain way, what an auditor asks to see, and how to decide what not to build.
Each intake is limited in size, so every intern has a named senior engineer who reviews their work every week.
We ask for one thing up front: a GitHub repository of a project you built yourself, and a few lines on why you built it. We read the code and the reasoning. Both matter more to us than grades or the name of your university.
What you will do
- Work beside a senior engineer on one live client engagement, from the first workflow notes to a release
- Build and test scoped parts of a system: a document reader, a matching rule, an evaluation case, an integration with an ERP or a bank feed
- Join client conversations, first as a listener, then write up what the team asked for and why it matters to their business
- Write the tests and evaluation cases that show your part works on real, untidy data
- Present your work to the team: what you built, what broke and what you would change
- Finish with one piece of work you can point to, in a client system or in our shared tooling
What we look for
- A project of your own on GitHub that you can explain: what it does, why you built it, and which decision you would make differently today
- Working Python or TypeScript. You can read someone else's code and ask a precise question about it
- Curiosity about how a business runs, as well as how the code runs
- Clear written English. Most of our work is explained in writing
- You are studying, or you finished your studies within the last two years. A computer science degree is not required
- Six months, at least 30 hours a week, in hours that overlap with European working days
Nice to have
- You have used a language model API in a project and can say where it gave wrong answers
- Some exposure to finance, accounting, logistics or healthcare, through study or work
- A README or short write-up that explains something you built to a person who does not write code
- German or Dutch
Your first six months
- Month 1: get set up, read the code and notes of a live engagement, and ship your first reviewed change
- Month 3: own a scoped part of a client system, with tests, under your senior engineer's review
- Month 6: hand over a finished piece of work, present it to the team, and talk openly with us about what comes next