Recover direction
Diagnose why a product or delivery effort has stalled, then rebuild a path the team can trust and execute.
Work
Each case study focuses on the parts that matter in a hiring conversation: what I inherited, what I personally owned, the tradeoffs I made, how I worked with the team, and what changed.
Diagnose why a product or delivery effort has stalled, then rebuild a path the team can trust and execute.
Change live products and platforms without treating users, reliability, or operational continuity as acceptable collateral damage.
Create clearer ownership, stronger technical judgment, and teams that can sustain the work without depending on heroics.
Explore the evidence
Showing 12 experiences
I designed and built a Node.js controller that translated a binary serial protocol into safe, stateful bill acceptance and dispensing operations for Bitcoin ATMs.
2020 · Production release
As Frontend Team Lead with engineering-manager responsibilities, I rebuilt team capacity, strengthened accessibility and quality, and helped steward a live veterans memorial platform—work later recognized in a ceremony by the VLM VA Director.
< 2 months · Administrative platform delivery
At Onaroll, I mapped an unfamiliar production system, learned a new deployment platform, and implemented most of a live Create React App and Heroku migration to Next.js and Vercel without downtime or known production defects.
0 · Known launch defects
I designed and built a standalone Node.js ingestion service that collected daily files from secure SFTP sources, translated incompatible schemas into the platform’s internal model, and eliminated manual conversion for the supported dispute-data pipelines.
Daily · Reliable automated ingestion
I turned a loosely defined, one-week client commitment into a stable standalone React and Node.js application that connected a nonstandard data workflow to the company’s primary dispute-management platform.
1 week · Production delivery window
I turned a spreadsheet-based workflow for legacy clients into a focused internal operations platform that imported existing data, launched in roughly 2–3 weeks, and saved Operations approximately 295 hours of manual entry every month.
295 hours/month · Manual entry eliminated
At Midigator, I helped rescue DisputeFlow 2, stabilized its architecture and delivery practices, evolved it into the more extensible DisputeFlow 2.1 platform, and coached a disconnected engineering group into a confident team that grew into larger responsibilities.
2 → 2.1 · From rescue to extensible platform
I independently recreated ten legacy C++ slot titles as playable desktop-browser proofs of concept, building a reusable HTML5/CreateJS engine that made nine titles repeatable and a tenth deeply customizable.
10 · Playable browser proofs of concept
I transformed an aspiring founder’s early-stage concept into a client-accepted, full-stack analytics MVP by defining the product, designing the architecture, and building the data pipeline, calculation engine, interface, tests, and documented handoff from the ground up.
Accepted · Client-reviewed MVP
At NexGaming, I took a custom casino operations platform from paper sketches and evolving stakeholder conversations through architecture, full-stack development, third-party integration, testing, deployment, training, production support, and handoff.
9 months · Concept to production
I redesigned a fragmented Farm Credit website-delivery process into a parallel, reusable system that cut the full discovery-to-launch lifecycle from roughly 22 months to 2–3 months on the first site, expanded team capacity, and supported at least eight distinct association launches.
22 months → 2–3 months · Full discovery-to-launch lifecycle
In 2011–2012, I independently built a WordPress and PHP platform that automated daily courthouse-data ingestion and grew into a connected internal system for staff-reviewed outreach, follow-up, administration, and real-time courtroom support.
Daily · Automated courthouse-data pipeline