I design backend systems that pay people, move freight, and stay up. Currently leading delivery for Big4 engagements at SyanSoft Technologies — Java, Spring Boot, microservices, and the operational discipline to keep them all running.
Architected the payments platform for a US-based consumer lender. Designed the ledger, idempotency keys, ACH/Plaid/Stripe rails, and the reconciliation pipeline. Led a team of 6 backend engineers from kickoff to production.
Real-time tracking and automated invoicing for a regional freight carrier. Decomposed a four-year-old monolith into 14 services around shipments, billing, and notifications. 1M+ events/day across the bus.
Analytics surface that turns raw event streams into plain-English summaries and anomaly alerts. Built the prompt-cache layer, the cost governor, and the JSON-mode validator. Cut model spend 40% in the first quarter.
Bespoke gateway in front of 22 backend services. Token-bucket rate limiting, circuit breakers, OpenTelemetry across the board. Handled 1M+ requests/day at single-digit ms p99 overhead.
Led the breakup of a Django monolith into Spring services on AWS. Strangler-fig pattern across 9 months. Zero downtime cutover, regression-test suite green throughout, no rollbacks.
Architecture ownership for Big4-aligned engagements. I lead cross-functional delivery teams, define engineering standards, and drive the AI-integration roadmap across the org. Hands-on with the systems I design — code, reviews, and on-call rotations.
Led the engineering team. Designed microservices handling millions of requests per day. Established CI/CD, observability, and code-review practices that survived my tenure.
Built backend services and APIs serving thousands of daily users. Spring Boot, PostgreSQL, REST. Where I learned that a clean migration history is worth more than any clever framework.
A written audit of your current system: bottlenecks, failure modes, and the changes that buy you the most runway. For teams who suspect their architecture is the thing slowing them down.
A production-grade payments core — ledger, idempotency, ACH/Stripe/Plaid rails, reconciliation. For founders and CTOs who can't afford a single double-charge.
Strangler-fig plan and execution. I run the cutover playbook I've used to break apart four monoliths without a rollback. Best when your release cadence has stalled.
A prompt-cache, budget guard, and JSON-mode validator dropped in front of your LLM calls. For teams whose OpenAI bill is growing faster than their revenue.
If you're building something that needs to stay up — payments, logistics, AI on top of real data, or an architecture that's stopped scaling — I'd like to hear about it.