Own the whole problem
I work across requirements, architecture, implementation, deployment, and long-term support rather than stopping at code delivery.
I build and modernize software for organizations that depend on existing systems, messy integrations, and durable operational behavior. Most of my work has lived where software supports real process, real users, and real consequences.
I work across requirements, architecture, implementation, deployment, and long-term support rather than stopping at code delivery.
I improve legacy systems in place when that is the responsible choice, respecting the business processes and operational constraints around them.
My background spans applications, databases, APIs, ETL, SCADA, metering, GIS, and internal platforms that were never designed to work together.
The software has to work for dispatchers, field crews, analysts, business users, and support staff, not just for the development team.
I choose tools and designs that serve reliability, maintainability, security, and operational needs instead of chasing fashion.
My professional background centers on utility and financial systems where continuity, auditability, and operational correctness are part of the job.
Sho-Me Power Electric Cooperative
Build internal operational software for a high-voltage electric cooperative where software reliability directly affects worker safety and day-to-day field coordination. Own requirements, architecture, implementation, deployment, and long-term support in a small team working across engineering, IT, and field operations.
Jack Henry & Associates
Owned delivery and technical direction for customer-specific enhancements across a heavily customized core banking platform used by hundreds of financial institutions. Worked in a high-audit regulatory environment where business continuity and correctness mattered more than novelty.
Top Shelf Systems
Supported development and maintenance of retail point-of-sale software for hardware and lumber supply clients, including data conversion, onboarding, and internal support utilities.
Redoubt Systems is independent engineering work outside my employment. It reflects how I approach architecture, automation, security, and operational ownership when building a system from the ground up.
Redoubt Systems
Designed and built a multi-tenant SaaS platform end-to-end, including control-plane software, infrastructure automation, server provisioning, tenant lifecycle management, and security hardening.
Selected examples of the kind of systems ownership and modernization work I enjoy most.
Case Study 1
Replaced a paper-based clearance workflow for bulk electric system operations with an auditable .NET application built around real dispatcher and field crew needs.
High-voltage work coordination depended on paper processes that made status, history, and oversight harder to manage.
Model the operational workflow directly and modernize the process without forcing operators to work around the software.
Database-backed .NET workflow with auditable state, role-aware interactions, and reporting support.
Worked closely with dispatch and field operations to shape the application around real clearance practices and constraints.
A live system used by 8 dispatchers and 17 field crews that improved visibility, consistency, and auditability.
Case Study 2
Connected SCADA, metering, weather, GIS, and internal business systems so operations staff could work with more complete and timely information.
Operational data lived in disconnected systems with different interfaces, update cycles, and ownership boundaries.
Build targeted synchronization, ETL, and dashboarding instead of forcing a disruptive platform rewrite.
Internal integrations spanning SCADA telemetry, metering, lightning and weather feeds, GIS, Solomon, and EHS platforms.
Delivered real-time dashboards, synchronization tooling, and mapping support for field operations and incident response.
Reduced manual data entry and versioning errors while improving situational awareness for outages and daily operations.
Case Study 3
Delivered long-term technical ownership inside a regulated core banking environment where every change had downstream compliance and upgrade implications.
Financial institutions needed client-specific enhancements without destabilizing a mature platform used at significant scale.
Pair delivery ownership with maintainable change management, release discipline, and internal tooling that reduced support risk.
Customized enterprise software with institution-specific logic, internal tracking tools, and data structures shaped by regulatory requirements.
Led a team of four across development, QA, and business analysis while managing ongoing customizations and upgrades.
Supported hundreds of financial institutions while improving supportability and preserving business continuity through change.
Case Study 4
Independent engineering project demonstrating multi-tenant architecture, infrastructure automation, security hardening, and end-to-end operational ownership.
Build a privacy-oriented communications platform without relying on manual provisioning or loosely isolated tenants.
Design the platform around repeatable automation, tenant isolation, and lifecycle control from the start.
Python and Flask control plane, Docker-isolated services, PostgreSQL, Nginx, Ansible automation, and privacy-oriented networking options.
Automated provisioning from billing event through server configuration, deployment, hardening, and tenant activation.
An early-access platform with live tenants that demonstrates architectural range beyond line-of-business applications.
I’m interested in staff-level and senior engineering roles where I can own complex systems, modernize existing platforms, and work across application, data, and infrastructure boundaries. I do my best work in environments where reliability, auditability, and operational correctness matter more than chasing the newest technology.