I'm an IT engineer who makes big, complicated systems calm and predictable. Since 2018 that has meant support, cloud, and everything that breaks at 3am. I still enjoy the hard problems.
A machine that won't boot, a network that keeps dropping, a report nobody can explain. Hand it to me and I'll disappear into it until it makes sense. That habit turned into a career, from fixing a university's computers to keeping telecom networks alive to architecting cloud platforms for enterprise customers.
I deploy and tune enterprise software on AWS, Azure and on-prem, shaped around each customer's security and networking constraints.
When production breaks under heavy load, I find the root cause and make sure the same failure can't happen twice.
I sit between customers and engineering, turning vague problems into concrete fixes and mentoring the team along the way.
My passion for IT started back in school, long before university or any job title. It never switched off, and this is where it's taken me since, most recent first.
At Ciklum I moved into enterprise BI platforms, deploying and tuning them across AWS, Azure and on-prem for large customers. Over time the work grew into architecture. I shape how an application should be built and deployed to fit a customer's security, scale and budget, then keep it healthy under real-world load. In 2025 I stepped up to Principal.
At GlobalLogic I supported telecom network equipment and the Linux systems underneath it, the kind of environment where downtime turns into unhappy customers within minutes. I learned to dig through logs until the real cause surfaced, to own incidents from first alert to final fix, and to cut downtime instead of just reacting to it. I grew from Junior to Senior and found the part of the job I love most, helping new engineers find their feet.
My first real job was systems administrator at my own university's computing centre. There was no handbook and no onboarding. I started fixing whatever was in front of me, from workstations to networking to the infrastructure the whole faculty relied on, and set up monitoring so we could finally see what was happening instead of guessing. It taught me the two lessons I still lean on. Good infrastructure is invisible, and writing down how you fixed something is half the job.
Hence the name, mikro.tips. Is self-hosting a personal site on a router overkill? Absolutely. But it keeps my hands on the whole stack and, I'll admit, it's fun. So far it hasn't skipped a beat.
The photo up top is me somewhere in Patagonia, well away from any keyboard.
The home network is my playground, and it's usually more elaborate than it needs to be.
Understand why it broke, document the fix, make sure it can't break the same way twice.
I deploy and tune enterprise BI platforms across AWS, Azure and on-prem under strict security requirements. I troubleshoot high-load production issues, build tooling that reproduces tricky bugs, act as the bridge between customers and engineering, and mentor the team through talks and documentation.
Supported telecom network equipment and its Linux systems for operators, keeping servers and network infrastructure stable in production. Deep log investigations to find root causes, incident ownership from first alert to final fix, and mentoring for new engineers.
Built and maintained the faculty's core IT infrastructure, networking and workstations, and set up monitoring.
The details here are available on request. Leave your email and I'll send you a one-time code that unlocks this section.
Enter your email and I'll send a one-time code there. It unlocks everything on this page.
Used only to send your code, then discarded. Not shared, never added to a list.
I've emailed a one-time code to . Enter it below to unlock. It expires in 3 hours.
Paste the one-time code from your email to unlock.
Everything below is now visible.
🔒 The write-up, preview and repository appear once you unlock with your code.
Based in Montréal, open to opportunities, and happy to work remotely worldwide. I read everything and reply personally.
Email me