I have 10+ years building and modernizing enterprise systems in C#/.NET, TypeScript and Python on Azure and AWS. I built automation behind 13,500 mortgage transactions a day and put ML into production workflows. I bring a former team leader's habits: clear communication, production judgment and a bias for simple solutions.
Escrow Audit Automation: an orchestrator I co-designed with our architect and senior engineer. It moved mortgage packages of 40–300+ pages through scanning, ML and data extraction, then back into a legacy core system.
We pulled audit out of the monolith into new microservices that still had to talk to the legacy .NET core, without breaking a business running at record volume. The orchestrator coordinated each stage, updated workflow statuses, and wrote extracted data back to the core database. Every hop was monitored so operations leaders could see what was happening as it happened.
I split the build into components owned by six teams so the work ran in parallel instead of in sequence. That cut the delivery estimate in half.
I helped decompose the document and post-close services from the core monolith, moved core systems from on-prem to Azure, then from Azure to AWS. I also helped replace off-hours-only releases with CI/CD pipelines.
I helped move a document-database data layer to relational SQL: 2M+ rows migrated with the business running, for faster queries and real reporting.
I built rules-driven automation for Final Policy and Recording send-out, plus round-robin order assignment and a real-time package tracker, inside a .NET/WPF core platform.
I scraped 100K+ free-text county rejection letters and partnered with Data Science on LightGBM and TensorFlow models. I also shipped Rejection Reason capture in the core app to feed downstream automation.
I built Splunk dashboards and alerts across the core services so the team found problems before users did, and on-call stopped meaning guesswork.
My current builds include a Next.js component generator driven by LLMs and MCP, an AI agent that turns natural-language questions into market-data API calls, and this site.
Simple problems get simple fixes. I reach for complexity only when the problem demands it, and I can explain why.
I started as a QE, so I think in test pyramids and try to break my own code before anyone else does.
I've run incident calls from day one: find out what's impacted, protect the business, then fix the root cause.
Years of teaching mean I can walk a principal engineer or a VP of Operations through a design and leave both better informed.
I've led teams, so I know what senior engineers do beyond code: unblock people, mentor, document and own the outcome.
I deliver web apps, API integrations and workflow automation from discovery to launch, and advise client leadership on technology strategy. Clients include First Independence Bank, where I'm leading the website redesign.
I designed enterprise engineering programs in cloud, AI, security and full-stack development with Azure, M365 and GitHub leaders. I ran classrooms as agile product teams, and mentored and placed 100+ new hires.
I led up to two teams and nine cross-functional reports across escrow, audit, documents, payments, closings and accounting. Over that time the platforms scaled from ~3,500 to ~13,500 transactions a day.
I built 600+ automated UI and integration tests for a .NET/WPF core platform, introduced integration testing to the Title channel, and mentored new QEs.
I built the systems behind a turnaround school's culture. The school's state ranking rose 16 points in three years, and that's where I learned to lead a room.
If your team needs an engineer who ships, communicates and steadies the room when production gets loud, let's talk this week.
Hiring a manager instead? See the engineering manager profile →