Product Engineer · Tennessee

I turn ambiguous problems into working systems.

The useful middle

I work best while the wind is still shifting.

Across interface, service, data, and infrastructure, I find the shape of the problem and carry the system through production.

  1. 01

    ProductFrame the useful problem

  2. 02

    EngineeringBuild the whole path

  3. 03

    SystemsLeave clean seams behind

02 / Operating range

Clarity while the wind is still shifting.

I'm a full-stack product builder for work that does not fit neatly into a ticket yet. I can find the shape of the problem, make the interface legible, and carry the system through production.

My background spans regulated fintech, reusable product platforms, operational software, and AI-assisted engineering. I care about the seams: the places where product intent, technical constraints, and human behavior meet.

03 / Selected products

Software for the work between people.

A small selection of products. Each turns a messy, social workflow into a clear next action.

01

Orchestral operations

Web / Native mobile

Chairs

Booking an orchestra is a chain of people, dates, offers, and answers. Chairs gives personnel managers one calm place to move that chain forward.

Managers create gigs, add dates, build rosters, send booking requests, and track responses. Musicians can accept or decline from a direct link, without creating an account first.

Manager
Create → roster → send → track
Musician
Open → review → answer
Built end-to-end
Product strategy, UX, full-stack engineering, and deployment
Visit Chairs
Chairs musician dashboard showing booking requests and confirmed work
Musician dashboard / mobileBookings + confirmed work
Lutheran.app home screen showing serving assignments, volunteer needs, and upcoming church events
Member home / mobileWeekly + occasional use
02

Church operations

Web / Native mobile

Lutheran.app

Church work is personal, local, and often spread across paper, inboxes, and memory. Lutheran.app makes the week legible without turning community into administration.

One shared system for ministries, calendars, service assignments, directories, reminders, and paper-to-app sign-ups—designed around what needs attention and what comes next.

Built end-to-end
Product strategy, UX, full-stack engineering, and deployment
Visit Lutheran.app
03

Live music trivia

Web / Native mobile

Wild Guess

Hosts run events, rounds, reveals, and scoring from a dedicated console. Teams join on their phones, choose a decade, claim a magic number, and follow the live leaderboard.

Built end-to-end
Product design and engineering across the host console, mobile app, shared backend, and deployment
Get Wild Guess
Wild Guess decade and magic number selection screen
Player app / live round setup

04 / Selected outcomes

Built where product detail has consequences.

  1. 01

    Marketplace

    Investor products with consequential details.

    Designed and delivered alternative-investment marketplace workflows, including compliance and KYC systems where clear state, traceability, and trust are part of the product.

  2. 02

    $65M

    Product engineering through a defining transaction.

    Contributed product engineering to an investment product through a $65M acquisition, connecting investor-facing experiences to the regulated systems underneath.

  3. 03

    AI

    Better tools, better daily work.

    Helped turn AI-assisted development from isolated experimentation into shared patterns, working examples, and practical team habits.

  4. 04

    Platform

    Shared foundations, not repeated decisions.

    Built reusable frontend infrastructure and design-system patterns so product teams could share interaction, accessibility, and implementation decisions.

05 / Working method

Find the seam. Build through it.

  1. 01

    Name the real constraint.

    Start with the person, the decision, and the thing that can go wrong—not the requested artifact.

  2. 02

    Make the path tangible.

    Prototype enough of the full system to learn where the product and technical assumptions break.

  3. 03

    Leave it easier to change.

    Extract the repeated decisions, keep ownership clear, and make the next version less expensive than the first.