ENGINEERING EVIDENCE

Difficult problems. Documented decisions.

What was broken, how I investigated it, what changed, and what the evidence supports.

DATA & PERFORMANCE

PostgreSQL Dashboard Optimization: 15s → 2s

Moving repeated reporting work out of the request path with materialized views, pre-aggregation and revised queries.

Node.js · PostgreSQL · PrismaRead case study

REPORTING ARCHITECTURE

MongoDB Reporting Across 26.6M Records

Replacing full-data downloads and application-side chart calculations with pre-aggregated collections and chart-specific queries.

MongoDB · Time-series aggregation · $mergeRead case study

NODE.JS & AWS

Node.js Processing Performance: 5 Minutes → 15 Seconds

Removing unnecessary browser overhead and sequential execution from a scheduled ticket scraper.

Node.js · AWS Lambda · AxiosRead case study

PRODUCTION DEBUGGING

When AI Was Confidently Wrong: Debugging an Apple Pay Production Failure

An Apple Pay failure showed why a plausible AI answer must still survive contact with observed browser behavior.

Stripe · Apple Pay · Browser user activationRead case study

APPLIED AI & INTEGRATIONS

AI Lead Qualification Connected to Real Operations

Connecting OpenAI, Grok and LangChain to qualification, HubSpot updates, calendar routing and payment-recovery operations.

Node.js · OpenAI · GrokRead case study

LET’S SOLVE IT

Have a difficult engineering problem?

If you’re dealing with a backend bottleneck, production issue, unreliable integration or an AI prototype that needs production engineering, let’s discuss it.

Discuss the problem