Live in production
CheckPulse
Multi-region uptime, DNS, and SSL monitoring for agencies. Deployed, public, and handling real traffic.
Solo, Mar 2026 to present
- 3
- Regions
- 2+
- Consensus
FastAPIPostgreSQLRedisCelery
B
Available for opportunities
Backend, Platform & SRE Engineer
I build and operate systems end to end: a monitoring SaaS live in production, three Kubernetes environments, an observability stack and a fleet watchdog, all on a seven-host vSphere cluster I administer myself. Looking for backend, platform, infrastructure, SRE or DevOps roles.
- Location:
- Plano, TX. Open to relocating anywhere in the US, including hybrid and on-site.
- Work authorization:
- US work authorization, no sponsorship needed
- Availability:
- Available to start immediately
- Education:
- BS Computer Science, UT Dallas, August 2025
At a glance
Each figure names how and when it was read, and links to the page that backs it.
- 7 hosts / 40 VMs
- vSphere estate I administer
- Source: vCenter API, 7 Oct 2026
- 3 clusters, 15 nodes
- Kubernetes environments (dev, staging, prod)
- Source: kubectl get nodes, 7 Oct 2026
- 115
- monitored signals in a watchdog I wrote
- Source: the watchdog's signal registry, 8 Oct 2026
- 77
- scrape targets, 23.6M rows/hr ingested
- Source: vmagent targets API, 7 Oct 2026
- 9
- project pages with a root-caused incident write-up
- Source: counted on this site, 7 Oct 2026; 3 more incidents are blog posts
- 9,849
- rows read back from a restore-tested backup
- Source: scripted restore, 18 Sep 2026
Skills, with the proof
Only skills that something on this site demonstrates. Each one links to the work.
Kubernetes
Linux
Python
Go
PostgreSQL
Prometheus / VictoriaMetrics / Grafana
Incident response and root cause analysis
Alerting and on-call design
CI/CD
Terraform
DNS and networking
Backup and restore
TLS / PKI
Cloudflare
Docker
VMware vSphere
AWS
Kafka
Featured Projects
The work I would want a hiring manager to read first. All of it is mine, end to end.
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.
Solo, Sep 2026 to present
- 970
- Silent failure streak
- 4
- Same bug, different layers
PythonSystem cronSSHWebhook alerts
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.
Solo, Jan 2025
- 3.3 GB
- Input size
- 10M+
- Lines
GogRPCGoroutines / channelsDocker
Complete
API Gateway
A Go gateway written from scratch: JWT auth with RBAC, layered rate limiting, round-robin load balancing, Prometheus metrics.
Solo, Feb 2026
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.
Solo, Sep 2026 to present
- 3
- Clusters
- 15/15
- Nodes Ready
RKE2 v1.36.4kube-vipCiliumingress-nginx
Live in production
Alert-to-Runbook Responder
A scheduled responder that turns a watchdog alert into a diagnosis and an allowlisted runbook, with the only auto-applied fix chosen because its failure mode was 970 silent skips.
Solo, Sep 2026 to present
- 2,658
- Ticks recorded
- 189
- Incidents
PythonPostgreSQLSystem cronSSH
Live in production
GitOps and a Signed-Image Gate on Three Clusters
Flux reconciling dev, staging and production from one public repo, with Kyverno refusing any image not signed by a GitHub Actions workflow in my org. Every gate was proven able to fail before it was trusted.
Solo, Oct 2026 to present
- 3/3
- Clusters under Flux
- 3 s
- Drift repaired
Flux v2.9KustomizeKyverno v1.19cosign (keyless)
Blog Series
Deep dives into infrastructure, DevOps, and building real systems.
1 part
Kubernetes in Production
Planning and operating production Kubernetes: cluster architecture decisions and declarative GitOps delivery with ArgoCD.
Start reading
1 part
Log Aggregation Deep Dive
Designing a centralized logging architecture with the ELK stack: what to collect, where it lands, and what it costs to keep.
Start reading
2 parts
DevOps Best Practices
Patterns I use for CI/CD pipeline design and Terraform at scale.
Start reading
5 parts
Checks That Lied
Five times a green signal meant nothing: a backup that restored an empty file, a failover test that proved the opposite of what it claimed, a runbook that had never once worked, a monitor that said the API was fine through a VIP it never used, and a renewal timer that ran 40 times while the certificate sat expired.
Start reading
About Me
I'm a backend and platform engineer who has drifted toward reliability work. CS graduate from UT Dallas (August 2025), most useful in Python and Go, 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. These are projects, not employment: I have not held a professional engineering role yet, and the site does not pretend otherwise.
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 and the page says how. The write-ups include the incidents too. The abuse of a signup endpoint on CheckPulse taught me more than any of the features did.
What I'm Looking For
- Backend, platform, infrastructure, SRE or DevOps roles
- Remote, hybrid or on-site anywhere in the US; based in Plano, TX
- Teams where I would be close to production
- Teams that value craft and documentation
Current Focus
- Operating three Kubernetes environments, an observability stack and an internal CA on vSphere
- Closing the offsite-backup gap: every copy is still in one building
- 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.