Operational design · Payments · Systems
I’m a builder by nature: I like knowing how things work, and making them work. Over 15+ years I’ve operated at virtually every level across enterprise IT, healthcare, and fintech, as the end user, the engineer, the builder, and the executive. What I care about is how a company works on the inside, and what that means once its customers are involved.
Hiring? Here’s my experience and what I’m looking for.
Spokane Valley, WA · Remote friendly
Rare combination: I’ve been every person in the room — user, builder, engineer, executive — across multiple industries, and recognize the systemic patterns that stay invisible when you stay in one lane.
View résuméOrganizations, like products, must be intentionally designed. Read the stack top-down the way your customers experience it — then fix it bottom-up.
What customers experience, report, and reflect back.
These are symptoms — not root causes.
What gets built, shipped, and supported.
Quality here is a direct output of the three layers beneath it.
Information flow, decision-making, and cross-team alignment.
Misalignment here creates compounding friction at every layer above.
Systems, tools, documentation, and internal knowledge structures.
When broken, teams work around it — creating invisible operational debt.
Roles, responsibilities, handoffs, and day-to-day workflows.
When poorly defined, every layer above inherits the confusion.
Most problems surface at L5. Most fixes start at L1.
The situation, the foundation-level change, and what it produced.
An API-integration and onboarding workbench for payment-provider UAT — spec ingestion, live sandbox execution, flow testing, and a governed AI layer.
Metrics verified · 28 Sep 2026. Counted from the live database and test suite, current sandboxes only.
Most people come to me seeing a specific problem, but not the full picture around it. Others have grown faster than their processes and need help realigning and planning what comes next.
When things aren’t working and it’s hard to see why, or when you know where you’re going but not where to start.
I find where the friction is actually coming from, and help you fix it in the right order.
How it worksWhen you’re choosing a gateway, wiring one into a platform, or getting a customer live on a payments API.
Gateway selection, integration architecture review, and outsourced UAT through go-live, from someone who has run the UAT himself.
How it worksI started on a helpdesk, and I’ve since worked at nearly every level above it: systems engineering, account management, project delivery, a startup I co-founded, and director-level solutions work in payments. The thing I’m best at hasn’t changed: getting to the root cause quickly, whether the problem is a system or a room full of frustrated people.
The longer versionI’m taking on consulting engagements now, project-based or retainer, across fintech, SaaS, and beyond — the problems I solve aren’t industry-specific.
I’m open to the right role too: hands-on, somewhere I can shape how the company works internally and see what that means for its customers.