I'm an IT engineer who likes making big, complicated systems calm and reliable. I've been doing this since 2018 — support, cloud, and everything that breaks at 3am — and 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 happily disappear into it until it makes sense. That curiosity turned into a career: from fixing a university's computers, to keeping telecom networks alive, to architecting cloud platforms for enterprise customers today.
Setting up and tuning enterprise software on AWS, Azure and on-prem so it fits real security and networking needs.
When production breaks under heavy load, I'm the calm one who finds the root cause — and makes sure it can't happen again.
I'm the bridge between customers and engineering — translating problems into fixes, and mentoring the team along the way.
I didn't plan a career in IT so much as fall into it, one broken thing at a time. Here's how it went.
My first real job was systems administrator at my own university's computing centre. No handbook, no onboarding — I just started fixing whatever was in front of me: computers, networking, the infrastructure the whole faculty relied on. I set up monitoring so we could finally see what was happening instead of guessing. Lesson one: good infrastructure is invisible, and writing down how you fixed it is half the job.
At GlobalLogic I supported telecom network equipment and its Linux systems for operators — where downtime means a lot of unhappy customers. I got good at digging through logs to find the real cause of a problem, owning incidents from start to finish, and cutting downtime. I grew from Junior to Senior, and found the part I love most: helping new engineers find their feet.
At Ciklum I moved into enterprise BI platforms, deploying and tuning them across AWS, Azure and on-prem for big customers. The work grew into architecture: shaping how an application should be built and deployed to fit a customer's security, scale and budget, then keeping it healthy under real-world load. In 2025 I stepped up to Principal.
Hence the name — mikro.tips. Is self-hosting a personal website on a router overkill? Completely. But it keeps my hands on the whole stack, and honestly, it's fun. It's been humming along quietly without a hiccup.
The photo up top is me somewhere in Patagonia, well away from any keyboard.
The home network is my playground — 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.
Deploy and tune enterprise BI platforms across AWS, Azure and on-prem under strict security rules. Troubleshoot high-load production, build tools to reproduce 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 and cut downtime, incident ownership end to end, and mentoring 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, I'll review it personally, and send you a one-time access code.
Enter your email — I'll approve it and send a code there.
When approved, I'll send a code to . Enter it below to unlock.
Paste the one-time code from your email to unlock.
Everything below is now visible.
🔒 The write-up, preview and repository appear once your access is approved.
Based in Montréal, open for propositions and happy to work remotely worldwide. I read everything and reply personally.
Email me