CTO · Solution architect · AI engineering
Every system needs gravity.
Software behaves like a universe. It expands, it accumulates entropy, and the moment nothing holds the center, it drifts into dust. I am the mass at the middle: setting technical direction, drawing the architecture, designing the interface — and writing the code for all three.
01 · Gravity
Architecture is the force that keeps a codebase from flying apart. Clear domain boundaries, honest data flow, named failure modes — structure that fits the team you actually have, not the one on the org chart.
02 · Light
Nothing exists for a user until it emits light. Design systems, readable type, honest contrast, motion that stays out of the way. A screen is good when nobody notices it working.
03 · Time
Entropy only ever increases, so we ship against it. Weekly releases, decisions written down once, and a roadmap that survives first contact with reality.
Frequently asked
Before you write.
I am happily based at TSLearning GmbH and not actively looking — though a truly exceptional offer is always worth a conversation. What I am exploring is a consulting practice: building and growing teams, sharpening how they work, and shaping enterprise software that holds up in production. If that sounds useful, write me.
Not yet. This page is a first step: I am gauging interest before registering as a sole trader and publishing concrete offers. Register your interest below — it is free and non-binding, and you will be the first to hear when offers go live.
It is a core focus. I build automated pipelines, guardrails and quality gates that let AI write and ship the code — zero lines typed by humans, delivered automatically to production, with people reviewing outcomes instead of syntax. Done right, it is not a demo: it raised the output of internal teams by around 40%.
Whatever fits. I am a big fan of micro-frontends and micro-services — but a well-built monolith pays the bills. I do not over-engineer. Architecture is a decision for the organization: it has to suit the size of the team that runs it and the user base it serves.
No. My foundation is software engineering, studied at FH Hagenberg, but I am just as at home on the business side: pre-sales, requirements engineering, and shaping offers and solutions that genuinely fit the client. I translate between what a business needs and what a system can deliver — and price it honestly.
Legacy systems and their modernization. At TSLearning I led a real turnaround: taking over a codebase from off- and near-shore vendors, stabilizing it, and growing a strong in-house team to own it. Rebuilding knowledge, architecture and confidence at the same time — that is the work I know best. Before that, at Objectbay, I built tailored software across the whole range: for large enterprises with multiple teams in Large-Scale Scrum, and for startups arriving with nothing but an idea and the ambition to ship something exceptional. Same discipline at every scale.
Daily. I have never believed you can hold the center of a system you do not touch. Architecture decisions made from a slide deck drift; ones made with your hands in the repository hold.
From doing both ends. On most projects I designed and built the interface end to end — Figma for years, Claude Design today. The goal is user-centered: simple, intuitive UI that speeds up real processes and makes the work feel light.
Kotlin, TypeScript, Go and Python. Spring, React and SolidJS. PostgreSQL, Kafka and Debezium for data. Docker, Kubernetes, ArgoCD and Flux on AWS or Azure — and plenty more where a problem calls for it. The stack is a means; I pick what the team can operate at 3am, not what is new.
With trust, not micro-management. I work alongside people to understand their real needs and pain points, give them room to stretch to their limits, and make sure good work gets noticed. Loyalty and hard work should pay off — growing people is how a team grows.
End to end, without hand-offs. I set up processes that let teams and individuals deliver independently — no waiting on other teams, no ticket ping-pong. One team owns the whole path: architecture, UI/UX design, implementation, release, and real-time monitoring in production, for software used by thousands to millions of people.
Hybrid, and I value the flexibility. Two days a week in the office, within about 20 km of Oftering, Upper Austria — for the things that need a room: whiteboard sessions, architecture decisions, code reviews, retros, and lunch together. The rest remote, from anywhere.
Register interest
Would this help you?
No commitment and no sales pitch. Before I open a consulting practice, I want to know whether there is real demand. Tell me what you would need — if enough teams do, concrete offers follow, and you hear first.
