Curriculum vitae
Software developer focused on architecture and AI infrastructure.
My path: a decade of industry work, then the study qualification, then informatics at HTL Leonding. That persistence goes into every system I design.
HTL Leonding — Department of InformaticsCollege for Informatics, specialisation in systems engineering. Diploma examination 2026, passed with distinction.
Diploma thesisDevelopment of an MCP Server with Semantic Search for LeoWikifull case study →
University entrance qualification, earned alongside full-time work; prepared at the University of Vienna (archaeology & prehistory track).
Scholarly writing and research methods, the STEOP module in historical-cultural reasoning, and the Latin supplementary exam.
HTBLuVA Waidhofen/Ybbs — Mechanical EngineeringHigher department for mechanical engineering; my first technical formation.
Before software came a decade of hands-on work. Keeping real-world processes running day after day taught me reliability, precision and process thinking, and it shaped what I expect software to deliver on a shop floor.
A year of direct responsibility for people; patience and reliability, learned early.
A decade of warehouse and shop-floor operations, six of those years in a single industrial plant. Processes, precision, accountability.
University entrance qualification alongside the job, then the informatics college full-time. Software is not an escape from operations; it is my way of improving them.
Designed and shipped a complete retrieval system: ingestion pipeline, vector DB, MCP interface, OAuth 2.1 security layer, deployed 24/7 on ARM hardware.
Five-model embedding benchmark with statistical tests; the production model followed a documented quality-vs-deployability trade-off. I measure before I decide, especially when models or prompts change.
I build and run a model-agnostic harness for AI agents with self-developed skills, plugins and hooks, using local LLMs alongside cloud APIs. Tool-calling, structured output and guardrails are everyday material for me, not buzzwords.
Formal test protocols, E2E suites, 98% branch coverage on my tooling core, and gap analyses that drive my own refactoring roadmaps.