About
Hello, I’m
There’s always a better way, and I enjoy trying to find it.
Full-stack, with design as the specialty — I’ll write the schema and then spend just as long getting the screen right. Some of it is my job: benefits portals, an accessibility platform. The rest is games, art, and apps for my kids.
The work itself is on the portfolio page, and the personal side is in the library. This is the background behind both.
How I ended up here
I did not set out to be an engineer. I started in benefits administration, got annoyed at how much of the job was copying things between systems, and taught myself enough to stop doing that by hand. The automation made my own role redundant, which turned out to be the best thing that could have happened.
Mar 2015
Benefits specialist
Started administering benefits for employer clients.
May 2016
Assistant account manager
Taught myself VB, JavaScript and REST APIs and automated the manual parts of the job without being asked to. The automation made the role redundant.
Jul 2017
Information systems analyst
Moved into IS and earned a project lead role within a year, owning the full lifecycle on C# MVC applications.
Nov 2019
Information systems analyst lead
Led a team of analysts and built the documentation and governance frameworks the department buildout was based on.
Nov 2022
Director of Technology Operations
Leading a twenty-person department, remote from Saratoga Springs, UT.
EducationM.S. Technology Management · B.S. Marketing Management
The day job
Most of what I do now is clear the way for twenty other people.
My team delivers about five times what it used to, and there are fewer of us every year. Help desk volume is the lowest we have on record and satisfaction is the highest. Those numbers are the team’s — what I changed is how the work moves through us.
Projects my team delivered per year, after I rebuilt how we work
Same team, then a smaller one. Enterprise delivery followed the same curve, from 1 completed project to 14 — 6 in production, 4 releasing, 4 in development. I changed the systems; they did the work.
Still building
I never stopped building the things I ask other people to build.
Six of these run AI in production, and every one of them has to survive an audit. Documents go in as native PDF and image blocks and come back through forced tool-use against a JSON schema, so what I get is structured data rather than prose I have to pick apart. Every extraction carries a confidence score, and the score decides whether the work posts, waits for a person, or gets thrown out. I like that part — the whole trick is deciding what the machine is allowed to be sure about.