About

I’m a senior backend/platform engineer with 6+ years building distributed systems, event-driven workflows, and high-throughput APIs. I lead modernization efforts that turn legacy systems into cloud-native services with better latency, reliability, and operational visibility.

I stay close to delivery while setting technical direction through design reviews, operational standards, and pragmatic tradeoffs.

What I Do

Distributed systems and scalable APIs

Designing high-throughput systems with clear SLAs, predictable latency, and resilience under load

Event-driven architecture and microservices

Building decoupled, asynchronous workflows using EventBridge, Service Bus, and message queues

Cloud infrastructure and DevOps workflows

Implementing IaC with CDK, containerization with Docker/Kubernetes, and CI/CD pipelines

Observability and production readiness

Instrumenting systems with structured logging, distributed tracing, and actionable metrics

Modernization and architecture evolution

Transforming legacy monoliths into cloud-native architectures with minimal disruption

Technical leadership and mentorship

Leading architecture reviews, establishing coding standards, and elevating team capabilities

Work Experience

HungerRush — Senior Software Engineer

Oct 2023–Present

Reporting Domain Lead

  • Set reporting domain technical direction and shipped performance improvements, cutting p95 latency by 40%.
  • Standardized fact-grain schemas for critical domains across 5,000+ enterprise locations.

Menufy by HungerRush — Software Engineer II

2021–2023
  • Integrated third-party delivery platforms processing 10k+ daily orders with 99.5% delivery success.
  • Modernized POS services to .NET Core, reducing deploy time to 15 minutes and incidents by 60%.

Menufy — Software Engineer

2019–2021
  • Built analytics dashboards and internal tools that reduced support effort by 70%.
  • Delivered RBAC-driven admin tooling that cut access-related incidents by 80%.

Principles

Reliability first

Every system should be designed with failure modes in mind. I prioritize idempotency, retry strategies, and graceful degradation from day one.

Explicit tradeoffs

Architecture decisions involve tradeoffs. I document constraints, measure impact, and make decisions based on data rather than assumptions.

Strong observability

If you can't measure it, you can't improve it. I build systems with comprehensive instrumentation so teams can understand behavior in production.