AI Solutions Engineer · IT System Owner
I do the architecture, write the code, and run it afterwards. Public funding, EU procurement, disability law, university teaching. Two run on models, and in both the model is prevented from deciding anything on its own.
How I keep the rules from being forgotten
Written rules get forgotten, especially the security ones. So on these systems the rule that matters is a check that runs every time the code changes. On UM Schedule the code physically cannot reach the database except through the layer that checks permissions. If someone tries, the build fails and nobody has to catch it in review.
Five systems
Three are live right now. One was sold by my employer after I handed it over. One is still in development, and its page says so.
German public contracts are advertised across the EU tender database and more than a hundred separate regional portals, so companies simply miss the ones they could win. I built a service that checks those sources daily, compares each notice against what a company actually does using embeddings I host myself rather than a paid API, and shows them the ones worth bidding on with a score they can argue with. I designed it, built it and run it.
A German state funding programme needed more than 700 organisations to send documents to a public authority securely. I built the whole thing on my own: who may see what, how uploads are handled, and a full audit trail that I designed before it was asked for. It ran a year with no security incidents. My employer then sold it.
In my current job I am the IT system owner. When someone wants a new application, I work out what data it would touch and decide whether we can use it. I run Entra ID, Intune and Microsoft 365 for the company. When we rolled out Copilot I argued for training people on it. Blocking it would have pushed them onto their private accounts, where nobody can see what happens to company data.
Applying for German disability benefits is hard to get right, and a missing document costs people months. I am building a tool that uses a language model to help applicants submit a complete case. It never predicts the rating itself, because the law reserves that to a medical assessor. I made it impossible in the code, so nobody has to remember the rule. Every legal statement it makes cites the paragraph it came from.
A psychology department at Maastricht University was planning its teaching by hand in a shared spreadsheet. I built them a planning board and a calendar for each teacher, so a change made by the planner shows up for the affected teacher immediately.
Happy to walk through any of these in detail, including the parts that went wrong.