Software Engineer · Houston, TX

I build backends that stay up under load.

Engineering scalable, distributed systems in Python and Java — FastAPI, Spring Boot, Kafka event pipelines, and cloud-native deployments on GCP and Oracle Cloud. Currently shipping creator-facing microservices at YouTube.

  • High volume daily requests served
  • Reliable uptime sustained
  • Faster release cycles

Experience

My engineering timeline

A progression from enterprise platforms to creator-facing distributed systems.

YouTube Software Engineer Present · TX Current

Scalable Python microservices on FastAPI, AsyncIO and gRPC inside an event-driven architecture — sustaining high-volume traffic with reliable uptime while cutting response latency.

  • Integrated ML and generative-AI endpoints for content recommendation, moderation and metadata summarization into backend services over REST, streamlining inference handling across creator-facing apps.
  • Built caching and persistence layers with Redis, PostgreSQL and Cloud Storage for high-volume retrieval APIs — less database load and lower average query latency.
  • Automated cloud-native delivery on GCP with Docker, Kubernetes and GitHub Actions, shortening release cycles and hardening rollbacks.
  • Rolled out distributed tracing with OpenTelemetry and Grafana Tempo, reducing time to diagnosis during peak traffic.
  • Hardened REST and LLM inference endpoints through PyTest suites, profiling and code review, improving code quality.
FastAPIAsyncIOgRPCRedisPostgreSQLGKEOpenTelemetry
Oracle Software Engineer India

Modernized enterprise Java and Spring Boot services out of a legacy monolith into distributed, event-driven components — secure REST APIs processing high-volume daily transactions with faster response times.

  • Wired scikit-learn fraud-detection models into Kafka-driven Python workflows, using feature engineering to reduce false positives.
  • Tuned Redis caching alongside Oracle Database indexing and query optimization for high-traffic transaction endpoints, lowering latency and raising peak throughput.
  • Automated OKE environments with Docker, Terraform and Jenkins pipelines, improving infrastructure utilization and release preparation.
  • Centralized security logging and audit trails in ELK and Splunk, flagging anomalous access and shortening investigations.
  • Raised API security standards with Spring Security and OAuth while practicing TDD with JUnit and Maven, improving productivity.
Spring BootSpring CloudKafkaOracle DBTerraformOAuthELK

Technical stack

What I reach for

Languages

Python · Java · SQL · Scala

Backend & APIs

FastAPI · Spring Boot · Spring Cloud · Hibernate · AsyncIO · gRPC · REST · Microservices · API Gateway

Distributed & messaging

Apache Kafka · event-driven architecture · load balancing · rate limiting

AI / ML

LLM integration · generative AI · scikit-learn · feature engineering · model inference

Data & caching

PostgreSQL · Oracle Database · Redis · query optimization & tuning

Cloud

GCP (GKE, Cloud Run, Cloud Storage) · Oracle Cloud Infrastructure (OKE)

DevOps & CI/CD

Docker · Kubernetes · Terraform · GitHub Actions · Jenkins · Git · Maven

Observability

OpenTelemetry · Grafana & Tempo · Prometheus · ELK · Splunk · distributed tracing

Security

Spring Security · OAuth2 · JWT · API security

Testing & quality

PyTest · JUnit · TDD · performance profiling · code review

About

Backend engineering, end to end

I like the unglamorous parts of software: the queue that never drops a message, the cache that absorbs a traffic spike, the trace that tells you exactly which hop went slow. Most of my work sits between an API contract and a cluster — designing services, tuning the data path, and making deployments boring.

Lately that means putting ML and LLM inference behind clean, observable endpoints so product teams can ship AI features without inheriting the operational risk.

Education

M.S. Management Information Systems
Lamar University, Beaumont, TX

Contact

Let's talk systems.

Open to backend and platform engineering conversations — roles, contract work, or a second opinion on an architecture you're stuck on. I reply within a day.

Sent straight to my inbox. I reply within a day — usually sooner.