B

Available for opportunities

Backend & Platform Engineer

I build and operate backend systems end to end: a monitoring SaaS live in production, a Go gateway and a distributed log analyzer, all running on a seven-host vSphere cluster I administer myself.

CI/CD
Infrastructure as Code
Data Pipelines
Networking
Observability
Containerization
Cloud (AWS)
System Design

Featured Projects

Flagship work demonstrating system design and engineering depth.

Live in production

CheckPulse

Multi-region uptime, DNS, and SSL monitoring for agencies. Deployed, public, and handling real traffic.

FastAPIPostgreSQLRedisCelery
Live in production

Fleet Watchdog

A ~250-line Python watchdog that runs on a different host from the agent fleet it watches, built after a cron job failed 970 times in four days and alerted exactly once.

PythonSystem cronSSHDiscord webhooks
Complete

Distributed Log Analyzer

Go master-worker system that parses a 3.3 GB, 10M-line access log. 36s single worker, 6s at 8-11 workers.

GogRPCGoroutines / channelsDocker
Complete

API Gateway

A Go gateway written from scratch: JWT auth with RBAC, layered rate limiting, round-robin load balancing, Prometheus metrics.

GoRedisJWTPrometheus
Live in production

Three-Environment Kubernetes Platform

dev, staging and production RKE2 clusters on bare vSphere, with VIP failover proved by forcing a leadership transfer rather than assuming one.

RKE2 v1.36.4kube-vipCiliumingress-nginx

Blog Series

Deep dives into infrastructure, DevOps, and building real systems.

About Me

I'm a backend and platform engineer. CS graduate from UT Dallas, most useful in Go and Python, and happiest somewhere near the line between an application and the infrastructure it runs on.

Most of what I know came from running things rather than reading about them. I operate a seven-host vSphere cluster at home, and the projects on this site are deployed on it or on a VPS I pay for. which means I am also the one who gets paged when they break.

I try to keep the claims on this site matched to what the code actually does. Where a project is unfinished, its page says so; where there is a number, it was measured. The write-ups include the incidents too, including the abuse of a signup endpoint on CheckPulse taught me more than any of the features did.

What I'm Looking For

  • Entry-level backend, platform, or infrastructure roles
  • Remote, or on-site anywhere in the US
  • Teams where I would be close to production
  • Teams that value craft and documentation

Current Focus

  • Bringing up three Talos Kubernetes clusters on vSphere
  • Hardening CheckPulse and getting it in front of agencies
  • Load-testing the Go gateway so its numbers can go on the page

Let's Connect

I'm always interested in discussing new opportunities, technical challenges, or just chatting about infrastructure.