Azure Infrastructure Consolidation
Work46 cloud resources optimized. Targeting ~60% cost reduction.
- Resources Managed: 46
- Cost Target: ~60% reduction
- Azure
- Terraform
- IaC
- DevOps
Software Engineer
I don't work for duty or money. I work to build something I'm proud of.
I see architectures where others see tasks.
I'm a Software Engineer who thinks in systems. I don't just complete tasks -- I ask what would really make a difference. When I see fragmented tools, I build a unified platform. When I see a recurring manual process, I automate it structurally.
I have ADHD. That means I bring radical curiosity to every problem, hyperfocus when something genuinely interests me, and the ability to see the whole system while others are looking at a single component. It also means I've learned to organize my thinking deliberately -- which makes me a better engineer, not a worse one.
I choose technologies based on the problem, not based on what I already know or feel comfortable with. If the problem calls for Swift, I learn Swift. If it calls for Terraform, I learn Terraform. The tool serves the solution, never the other way around.
I read philosophy -- different authors, different schools of thought. It's trained me to reason about complex problems, question assumptions, and think at multiple levels: from the technical implementation to the broader purpose of what I'm building.
I value honesty, simplicity, and people who put humanity first. I don't work for money or duty -- I work to build something I'm proud of. I expect mutual respect as a baseline, and I don't compromise on that for any amount of money.
I'm looking for a remote-first team where ownership matters, quality is non-negotiable, and I can have real impact on architectural decisions. Small, growing teams that value thinking over ticket velocity.
Each project below is a case study — not what I built, but how I thought about it.
46 cloud resources optimized. Targeting ~60% cost reduction.
Enterprise platform built right. TDD >90%. Hexagonal Architecture.
First time on iOS. Swift chosen for the problem, not for comfort.
Low-level graphics exploration. Understanding rendering from scratch.
Exploring a completely different domain. Game development as learning.
Whether you're looking for a new team member or a freelance collaborator — I'm open to both. Let's start a conversation.