Senior Software Engineer focused on distributed systems, platform engineering, and cloud-native infrastructure.
I build systems where cost, latency, reliability, and failure modes are first-class design constraints—not afterthoughts.

My work sits at the intersection of application development, platform architecture, and real-world operational constraints, spanning enterprise cloud environments and resource-constrained edge systems.

• Cloud & Platform: Azure, Kubernetes (AKS), GitOps, Infrastructure as Code
• Distributed Systems: multi-tenant architectures, caching strategies, failure-mode design
• Edge & Hybrid: Raspberry Pi 5 edge nodes paired with Azure control planes
• Observability & Reliability: Prometheus, Grafana, OpenTelemetry
• Application Engineering: React, TypeScript, Node.js, PostgreSQL, WebSockets

A hybrid platform pairing Raspberry Pi 5 edge nodes with Azure-based cloud services, intentionally designed to surface real-world challenges such as:

• intermittent connectivity
• constrained compute
• partial failure
• latency variability

This lab mirrors failure patterns I’ve seen in production systems and serves as a proving ground for platform, reliability, and recovery decisions.

https://github.com/doctacloak/homelab (update with actual repo)

A multi-tenant civic intelligence platform focused on cost-efficient data access, strict tenant isolation, and scalable ingestion.

Key outcomes:

• Order-of-magnitude API cost reduction through architectural caching and request optimization

• Sub-millisecond response paths where latency matters

• Clear blast-radius boundaries and zero data leakage across tenants

• Kubernetes operations and troubleshooting
• GitOps workflows (Argo CD)
• Infrastructure automation and policy enforcement
• Observability-driven reliability engineering
• Hybrid cloud failure-mode testing

This year I’m going deep into Unreal Engine 5 from the ground up, with a deliberate focus on:

• C++ systems programming inside a large-scale engine
• Engine architecture, memory ownership, and performance tradeoffs
• Real-time simulation constraints (latency, determinism, resource budgets)
• Bridging engine-level systems thinking with distributed and platform concepts

The goal is not game “content,” but a deeper understanding of real-time systems, performance-critical C++ codebases, and engine-level architecture.

Progress, experiments, and notes will live here as they mature.

I document what I build and learn—especially the parts that break—so others can learn from real constraints instead of idealized diagrams.

Common themes:

• Hybrid cloud & edge architecture
• Platform reliability and observability
• Kubernetes operations at scale
• Azure platform patterns
• Real-time systems and performance tradeoffs

“Once you decide on your occupation, you must immerse yourself in your work. You have to fall in love with your work. Never complain about your job. You must dedicate your life to mastering your skill. That’s the secret of success and is the key to being regarded honorably.”

Jiro

I care deeply about craftsmanship and long-term systems health.

Build boring systems that fail predictably.
Optimize for clarity, blast radius, and recovery—not novelty.

If you’re working on mission-critical systems, platform engineering, distributed infrastructure, or real-time systems, we’ll probably have good conversations.

📫 Connect

• LinkedIn: https://www.linkedin.com/in/doctacloak/
• GitHub: https://github.com/doctacloak