Hello World, — I mean, Stranger
Welcome to my page in the world wide web
How it all started
fond memory
I still remember my first PC clearly: a Compaq running Windows 95. That is where it all began — and floppy disks.
Chip modding on the old PS2 came next. I started at ten years old, in 2005.
Track record
Work across the top, education below it to scale. Much of it ran in parallel.
Swiss army, single-stint service
Swiss Armed Forces
serviceSwitzerland11 months
- Staff orderly, assigned to the battalion commander
- Go-to person for Windows and Office questions
Customer Support, web hosting
cyon GmbH
workBaselone month
- Ticket and phone support for web hosting
- First production contact with Linux servers under customer load
ICT Supporter
Genossenschaft Migros Zürich
workZürichpart time
- Single point of contact, first-level for software and hardware
- Client machines, SAP, logistics systems and enterprise networks
- Project work on Office 365, Azure and SharePoint, plus on-call duty
Technical Team Lead SRE/DevOps
SV Group
workDübendorf ZHfull time
- Leading third-level operations since 2024
- Previously IT application manager, engineering added in 2023
- Interfaces, migrations and architecture for business-critical systems
scroll sideways
Education
2012 – 2015Commercial apprenticeship, EFZbfsl Langenthalgrade 4.8
2019 – 2022Professional Bachelor, Business Informaticsipso Bildunggrade 4.8
2023 – 2026BSc Business InformaticsFernfachhochschule Schweiz (FFHS)grade 4.9
Work
I lead a mixed team of internal staff and external partners, operating business-critical enterprise applications, developing the interfaces between them, and delivering migrations and upgrades without taking the business offline.
Lead
Team leadership across internal employees and external partners.
- Vendor and partner management
- SLA ownership and service management
- Coordination of application release deployments
- Advising and supporting key users
Operate
Third-level support. By the time an incident reaches my team, the obvious causes are already ruled out.
- Reading code, correlating logs across systems, reproducing under load
- Monitoring and assurance of application availability and performance
- Workarounds that hold until the real fix ships
- Keeping business-critical systems available during live change
Build
Full-stack engineering in Python and PHP.
- Interface development across REST, GraphQL, SSH, SFTP and FTP
- Database administration and tuning across MS SQL, MySQL, MariaDB and PostgreSQL
- Reverse engineering of undocumented systems
- Low-level execution analysis and software workflow design
Structure
The part I am best at, and the part hardest to put on a CV.
- Software architecture
- Application and interface portfolio ownership
- Specifications, runbooks and technical documentation
- Migration and upgrade leadership on critical stacks
- Threat analysis, forensic investigation and hardening
Inventory
- Languages
- Python · PHP · SQL · Bash · JavaScript · HTML/CSS
- Databases
- MS SQL Server · MySQL · MariaDB · PostgreSQL — administration, tuning, migration
- Operating systems
- Linux · Windows Server
- Integration
- REST API · GraphQL · SSH · SFTP · FTP
- Practices
- Application lifecycle management · ITIL-aligned third-level support · release and deployment coordination · incident and problem management · software architecture · reverse engineering · technical documentation
- Security
- Threat analysis · forensic investigation · hardening · security auditing
- Education
- BSc Wirtschaftsinformatik · Professional Bachelor Wirtschaftsinformatik · ICT Platform Development Specialist, eidg. Fachausweis
- Languages spoken
- German (native) · English (professional)
Background
I started hosting game servers at fifteen. That was the entry point — not a class, not a curriculum. A server that had to stay up, players who noticed within seconds when it did not, and no one to escalate to.
Everything followed from there. PHP and databases because the community site needed one. Linux because that is what the box ran. Network and security because the box got attacked. I learned the stack in the order the problems arrived, which is a slower start and a much more durable foundation than learning it in the order a syllabus presents it.
The scope kept growing and the pattern kept repeating: something breaks, nobody knows why, I go find out. Web development turned into application development. Application development turned into database administration, because the queries were the bottleneck. That turned into systems and infrastructure work, because the database was only as good as the machine underneath it. Interfaces between systems became a specialty almost by accident — they are where things break, and where nobody wants to look.
Somewhere in there I formalised it. The paper followed the practice, not the other way around.
How I work
- Down to the execution path
- A system is not understood until I know what it does at the low level — the actual sequence of operations, not the diagram someone drew in 2019.
- Documentation is infrastructure
- An undocumented interface is an outage with a delay fuse. Portfolios, specifications and runbooks are deliverable work, not overhead.
- Monitoring before promises
- You cannot commit to an SLA on a system you cannot observe. Instrumentation comes first.
- Chaos to structure
- Give me the system everyone avoids. That is the interesting one.
Hobbies
What happens outside work. The things built are under Projects.
Airsoft
Competitive airsoft as a sport, with safety standards, measurement and an official body behind it.
- A regulated sport with clear energy and safety limits
- Chronograph checks against legal limits
- The building side lives under Projects
Gaming
Where it started, and still ongoing. Hosting game servers at fifteen was the entry point into Linux, PHP, MySQL, networking and security — the entire foundation.