My route into product was not a perfectly mapped career plan. It was Operations, then Merchandising, then Product — each move giving me a better view of how the business actually worked and where it kept getting stuck.
The path here
Not exactly a straight line
I spent roughly a decade at Overstock/Beyond. In Operations, I lived close to workflows, escalations, partners, fulfillment, and the consequences when systems failed.
Merchandising brought me closer to suppliers, assortment, and commercial decisions. By the time I moved into Product, many of the people using the tools were people whose work I already understood.
That history still shapes the problems I gravitate toward: unclear ownership, disconnected systems, manual processes, integrations, and business pain that has not yet been translated into a product problem.
Learned the workflows, escalations, partner realities, and downstream cost of systems that do not work.
Got closer to suppliers, assortment, commercial decisions, and the business behind the catalog.
Turned firsthand operational context into clearer tools, integrations, and customer experiences.
Uses new tools to make ideas tangible sooner, so teams can react to something real.
How I work
In practice
I like getting far enough into the work to understand what should actually change — and what should not.
A feature request is usually the beginning of the conversation. I want to see the actual workflow, the handoffs, and where people have learned to work around the system.
The person doing the job usually knows where the process bends or breaks. I would rather understand that reality than design from a tidy diagram alone.
I am comfortable moving between business, UX, operations, and engineering conversations — and translating enough context that each group can make a better decision.
The Extend test and Angi scheduling work both required changing direction when the data challenged an assumption. Defending the original idea is not the job.
Prototypes give people something specific to critique. They expose fuzzy requirements, missing journeys, and false confidence faster than another meeting usually will.
Good product judgment includes what not to build, what not to claim, and when the available data does not support a precise answer.
I am not a traditional software engineer, and I do not pretend to be an expert Python developer. My strength is understanding the user, the system, and the outcome well enough to work effectively with technical teams — and increasingly, to build a useful first version myself.
I have leaned into APIs, Figma, AI-assisted prototyping and development, Python and Tkinter for Compliance Navigator, basic SQL, Supabase, and hands-on systems work.
This portfolio is part of that practice. I used Lovable and AI-assisted development to shorten the distance between an idea, a prototype, and something another person can actually react to.
When Jira isn’t open
Curiosity, off the clock
Curiosity does not really clock out when I do. I tend to pick something up, learn enough to make it interesting, and then wonder what else I can do with it. Small projects rarely stay small for long.
I build content-creation and streaming studios, tinker with computers and systems, and like making tangible things. Camping, off-roading, and modifying trucks scratch the same itch: understand how it works, then see what it could become.
I love drawing. I play guitar, plus a little drums, trumpet, and ukulele — enough range to stay curious, not enough to start giving masterclasses.
Karaoke is approached with substantially more confidence than my dancing. The dance moves are terrible. Enthusiasm is not the problem.
I like being outside, competing a little, and regularly receiving reminders that one good golf shot does not guarantee the next one.
I own an absurd amount of body-recovery gear. If it hurts, there is a strong chance I own a device for it.
Also ordained in Utah. Long story. Legally useful under surprisingly specific circumstances.
George, VP of Barketing. Frequent coworker. His review process remains mostly snack-based.
For all the projects and hobbies, the people I love come first. I am especially close with my sisters, and family is a huge part of who I am.
Known weakness: Good people, good dogs, golf, questionable decisions involving cruises, and an alarming inability to play it cool.
I’m looking for product work where I can get close to the people and systems involved, collaborate deeply across functions, own a complicated problem space, and keep becoming more technically capable along the way.