Andrew White Jr.
Self-taught · production-scarred · 79 services deep

What I've built (solo, in production, last 18 months)

Scars I earned (in chronological order)

• 555 MB / 189K-row SQLite indexer: recovered from "database is locked" production failure by tuning busy_timeout + switching to WAL mode. I have real scars around concurrent writers.
• Timing-safe HMAC bearer auth: the kind of detail you only bake in after a timing-attack bite. All internal service calls use it.
• Hand-rolled HMAC-SHA256 JWT for Ghost CMS Admin API: I read the RFC and implemented primitives instead of pulling a library. Kept the dependency footprint clean and now I actually understand JWT.
• Zero-downtime schema migrations on a Stripe-billing Flask app: add column → backfill → flip → drop old. The same playbook ports to Postgres with bigger-team tooling.
• PHI-safe LLM routing: health-domain prompts force to local Ollama instead of cloud APIs, regardless of which provider is faster. Policy-as-code primitive that matters in regulated domains.

Resume variants (pick the one that matches the role)

Quick links

How I'd spend my first two weeks on your team

Read the code, shadow oncall, learn the deploy path end-to-end, and find one real bug to fix before anyone assigns me one. I want the feel of "shipped here" before I try to decide what to build next. After that, ask me what's obviously broken and I'll tell you.

What I won't pretend

• No CS degree. Self-taught. If that's a dealbreaker, we've both saved time.
• TypeScript/React is read-and-ship competent, not day-one expert. I'd need a month to get to senior-frontend fluency. Python/FastAPI/backend is where I'm strong from day one.
• Kubernetes I've used at workstation scale (k3d). Production k8s I'd learn on the job — fast — because the underlying systems instincts are right.
• My GitHub looks quiet because most of my last 18 months lives in a private monorepo. Happy to walk through screenshots and architecture on a call.