Production ownership
Architecture, deployment, and operations
Comfortable taking responsibility for the real delivery surface, not just the prototype layer.
Why Work With Me
This page is here to answer the practical buyer questions: have you done real work, can you handle the delivery, and what kind of person will I be working with?
I work best when the real problem is not just “build this feature,” but “make this part of the business run better.” That usually means cleaning up handoffs, reducing manual work, and building something that still works after launch.
My background includes enterprise software, security, infrastructure, automation, and hands-on delivery for a live production platform. That mix matters because the work usually crosses more than one layer of the system.
I also serve as Treasurer for the VIFG nonprofit, contributing to quarterly financial review, stewardship planning, and oversight alongside the technical delivery work. That role reinforces the same expectation I bring to client work: responsible operations, clear accountability, and follow-through after launch.
My faith shapes how I work: honest communication, clear commitments, stewardship, and respect for the people who have to live with the system after launch.
Production ownership
Comfortable taking responsibility for the real delivery surface, not just the prototype layer.
Automation impact
Past automation work includes recurring processing and workflow improvements that cut manual team effort.
Enterprise credibility
Background includes frontend, APIs, security hardening, infrastructure automation, and production support.
Ongoing technical growth
Graduate study in AI supports the consulting work, but it is not the reason to trust the delivery.
Open the roles you care about and skim the rest.
June 2020 to Present · Sole engineer responsible for the full delivery lifecycle of accessible web systems for nonprofit organizations: architecture, frontend, infrastructure, deployment, and ongoing operational support.
Current role · Contribute to quarterly financial review, stewardship planning, and nonprofit oversight, helping support responsible operations and organizational accountability.
November 2024 to February 2025 · Short-term contract focused on enterprise API integration support: testing, validation, troubleshooting, and cross-team coordination for internal system workflows.
November 2022 to March 2024 · Owned infrastructure automation and cloud application delivery across AWS environments: provisioning, configuration management, microservice development, and operational tooling.
October 2021 to October 2022 · Owned application-level security hardening across internal web applications: vulnerability remediation, secure API design, and authentication enforcement.
June 2019 to June 2020 · Built and maintained frontend and service-layer software for internal retail systems at enterprise scale: cross-repo modernization, microservice development, and cross-team delivery.
System-level thinking
I do not stop at the interface. I plan the handoffs, rules, and failure points that make the system usable in real work.
Enterprise discipline
Large-company experience shows up in clearer delivery, better documentation, and fewer sloppy surprises.
Hands-on delivery
I can scope the work, build it, ship it, and support it instead of handing off a slide deck.
Values that travel into the work
My Christian faith shapes how I communicate and handle trust, while the work itself is for anyone who is a good fit.
University of St. Thomas
September 2024 to December 2026
Additional credential: Big Data certificate.
Augsburg University
2016 to May 2020
Pearson VUE · March 2024
The full PDF is still available if you want the complete timeline and traditional resume format. It stays secondary to the on-page summary.