I design and run infrastructure that remains understandable under pressure. Across telco, banking and pharma, I combine cloud engineering, automation and operational discipline to make change safer and recovery faster.
Network administrator → incident & problem manager → DevOps & cloud engineer → team lead. The common thread: production should never be a mystery.
I learned operations where downtime actually hurts — across telco, banking and regulated pharma environments with real SLAs, incident bridges, controlled change and documentation discipline. Today I bring that mindset to systems of any size: cloud infrastructure, deployments, monitoring and the automation around them, down to the details that decide whether a thing actually works — DNS, certificates, logs, backups, and the path back when a deploy goes wrong.
This site is intentionally small: a card, a few principles and real work I can stand behind. No stock photos, no invented case studies.
Different industries, the same expectation: systems must be understandable, controlled and dependable when it matters.
My foundations are in network administration and production operations — connectivity, routing, DNS, monitoring, troubleshooting and incident response in an environment where availability is part of the product.
Cloud and DevOps delivery in a security-conscious environment: Azure, CI/CD, containers, controlled change, clear documentation and cooperation across technical teams.
Experience from a regulated environment where reliability, traceability and clear documentation matter as much as delivery speed. The focus is controlled change, validation and a clean operational handover.
If nobody can see what is running, ownership becomes guesswork. Monitoring comes before features.
One public entry point, clear routes, predictable certificates. Complexity lives behind the door, not in it.
The docs that matter are the ones you reach for during a tired 2 a.m. rollback.
Exciting infrastructure is a pager going off. I build the calm kind — repeatable, observable, repairable.
A career across telco, banking and pharmaceutical research and development shaped how I approach availability, change, migration and ownership today.
I started close to the infrastructure, where connectivity, routing and service availability were daily operational concerns. Incident management added the pressure of restoring service quickly, coordinating across teams and finding recurring causes. Moving into cloud administration shifted the focus from reactive fixes toward clearer ownership and more repeatable operations.
Migration perspective Service migrations meant understanding dependencies, coordinating cutovers and protecting availability while the platform changed underneath.
The work grew from designing and operating network infrastructure into leading technical teams and improving how systems are delivered. Moving into DevOps connected infrastructure, automation and team ownership into one delivery system — while keeping technical consequences visible in every decision.
Migration perspective Network and platform migrations required controlled change windows, dependency planning, coordinated execution and a credible rollback path.
This environment brings the full journey together: infrastructure thinking, cloud, automation, incident awareness and delivery ownership. New services must move beyond a successful build into a controlled, supportable and traceable operating model.
Migration perspective Preparing transitions means mapping dependencies, validating readiness and making sure the receiving teams can operate the service with confidence.
Inventory and operational workflow system for a non-profit workshop, taken from unclear daily processes to a containerized application that can be deployed, operated and improved.
Product shaping · Application delivery · Deployment · Operations
Public websites, contact flows, staging environments and monitoring brought under one understandable operating model with a simple edge and repeatable deployment path.
Architecture · Web delivery · Caddy edge · Monitoring
For a note, a question or collaboration — write me here or on LinkedIn. Commercial inquiries have a cleaner home at Sysrift.