FullstackDevOpsCloudInfrastructure
Building reliable and scalable applications
DevOps & Software Engineer
Hagenberg im Mühlkreis, Upper Austria, AustriaEnglish, French, Arabic
Johannes Kepler Universität Linz
Open to part-time, remote or student roles
About
I build software that is designed to run well in the real world.
From application workflows and secure APIs to containerized deployment, monitoring, and recovery planning, I turn complex operational needs into reliable systems.
01
Desktop applications, HTTPS APIs and admin portals with typed contracts, schema migrations and tests — delivered as whole systems, not isolated features.
02
Loopback-only services, constrained control planes, role-aware rate limits and audit trails, designed in before the first deployment.
03
Health checks, structured logs, backups taken before risky steps, and signed updates that make recovery a routine operation.
Selected work
Each case study covers the problem, the architecture, the decisions and their trade-offs, and how the system is delivered and run.
Desktop platform implemented · cloud control plane partially built
A Windows back-office platform designed for travel agencies that must keep working when the internet does not. The system combines local-first data, a secure LAN deployment mode, bilingual workflows, and recovery-aware operations.
Read the case study
Migration completed July 2026 · containerized deployment
A Node.js HTTPS API that replaced FTP as the way a legacy desktop client talks to its back office, rolled out client by client, paired with a protected admin portal for service health, storage, backups, diagnostics and controlled operations.
Read the case study
How I work
Software engineering and operations are one loop. What is learned running a system feeds the next design decision.
Step 01
Map the real workflow and the constraints nobody wrote down: connectivity, hardware, who operates the system and what happens when it fails.
Step 02
Draw the data and security boundaries first, then record each decision as constraint, choice and accepted trade-off.
Step 03
Ship through repeatable builds — migrations, containers or signed installers — with checks that fail closed instead of warning.
Step 04
Make the system explain itself with health checks, structured logs and audit trails, and treat restore as the drill that matters.
Capabilities
Tools matter less than what they are used for. These are the ones the case studies rely on.
Product workflows from the interface to the API
Durable records and safe schema change
Repeatable builds and releases
Systems that can be observed, defended and recovered
Architecture that fits how the system is really used
About
I work across the line between writing software and running it. The two systems on this site show the pattern: a Windows desktop platform I co-founded, which has to keep trading without the internet, and the migration of a live client base from FTP to a containerized HTTPS API.
In both, the most important work was not the feature list but the boundaries — where data lives, what is allowed to reach what, and how the system is updated, observed and recovered.
Contact
I’m glad to talk about engineering roles, delivery and operations work, or a system you need to make more reliable. Email is the fastest way to reach me.
Open to part-time, remote or student roles