Product builder · Full-stack developer · Portland, OR
I build products people actually use.
Or at least, products I really, really want them to use.
I find the place where work gets stuck, sit with the people living it, and build the tool that fixes it. I build with Claude every day, I check everything it gives me against the real data, and I keep improving what I ship from what people tell me.
- Right now The only developer at OMIC USA, a 60-person testing lab in Portland
- Every day Building and testing ideas with Claude
- Looking for Product, product operations or full-stack roles
Day job
At OMIC USA, I'm the only developer.
I own the software a 60-person testing lab runs on, from the system that prices every test and turns it into a lab work order, to the help desk that routes work between departments. I also run IT and the building. Requests come straight to me from chemists, lab managers, customer service and the company president, and I take them from the first conversation to production and keep supporting them after.
Lab Support
In useA help desk for a 60-person lab, from the pitch to the launch.
QUOLims and the 2026 price update
Price update liveThe lab's quoting system, rebuilt, and a price change across three production databases.
Read the story →
IT & Facility Workspace
In useMy own system for running IT and the building, with more than a decade of facility history I can ask questions of.
Read the story →Outside work
I keep building.
Almost every one of these started with something frustrating, slow or getting lost. The label on each one says honestly how far it got. Click any of them for the full story.
The Post
Used for realA back office for a local fence and deck contractor.
Chess Coach
WorkingA chess coach that trains you on your own mistakes.
Read the story →
Deal Bench
WorkingA real estate deal tool that looks at every listing photo.
Read the story →
Oregon Collective
Pre-launchA marketing co-op for small fence and deck companies.
Read the story →
MyLifeLang
Working prototypeLearn Spanish and Japanese from the sentences you actually say.
TalkWebsite
TestedFree sample websites to win roofing companies as customers.
Read the story →
Northwest Resale
WorkingIs this liquidation pallet worth buying?
Read the story →
JobSentry
PrototypeReviews in reverse: contractors rate their customers.
Read the story →
How AI Works
BuiltAn interactive explainer of AI for normal people.
Read the story →
PodThink
PrototypeA long podcast, turned into a study guide.
Read the story →
Kart School
BuiltA beginner's guide to go-karting.
Read the story →Also built: a staged product-research pipeline for dropshipping with a live dashboard, a Google Maps lead finder that found over 4,500 Oregon roofing companies, a bilingual church website, a detailed spec for an AI debate-practice app, and in college a Tableau sales dashboard and a full-stack web app on MongoDB, Express, React and Node.
How I work
People first. Then the plan. Then the build.
- 01
Sit with the people who have the problem
I run the workflow myself and watch how it actually works, which is rarely how it's written down.
- 02
Write it down before any code
A short spec, the edge cases and a test script. Most of the expensive mistakes get caught here.
- 03
Build with Claude, check everything
Claude writes a lot of my code. I decide what it should do, and I check every claim against the real data, because looking right isn't the same as being right.
- 04
Ship small, listen, improve
Every piece of feedback goes in a backlog in the person's own words, and the next update comes from there.
Skills
What I bring.
Product and operations
Talking to users and finding the real problem, mapping workflows and edge cases, writing specs and test scripts, soft launches, feedback backlogs, manuals and walkthrough videos, rolling changes out so people actually adopt them.
Building with AI
Claude Code as my daily build partner, spec-first plans, prototyping and testing ideas fast, the Claude API with structured outputs and fallbacks, designing AI features with a human in the loop.
Engineering
- C#
- .NET
- Blazor
- ASP.NET Core
- EF Core
- TypeScript
- JavaScript
- React
- Next.js
- Node.js
- Express
- Python
- FastAPI
- Playwright
- Git
- IIS
- Netlify
Data
- SQL Server
- T-SQL
- PostgreSQL
- MongoDB
- SQLite
- Prisma
- Excel
- Data reconciliation
- Power BI
- Tableau
About
Hi, I'm Thomas.
I like building the whole thing. Not just the code, but figuring out what people actually need, how the work really flows, where it breaks, and what a better system looks like. Then I build it, ship it, and keep tuning it from what people tell me.
AI is how I work. I use Claude every day to prototype ideas in an afternoon, test them against real data, and turn the ones that hold up into tools people rely on. It lets one person cover what used to take a small team, and I've used it to pick up new stacks fast: C# and Blazor at work, Next.js, Python and Node on my own projects.
I'm flexible by habit. On a given week I might be designing a workflow with a lab manager, cleaning up messy pricing data in SQL, building a dashboard, and fixing whatever broke in the building. I almost studied psychology, and that side still shows: I care most about how people actually behave and what makes a tool something they want to use.
Right now I'm the only developer, and the main IT and facility person, at OMIC USA in Portland. Before that I worked in the Intel and TikTok data centers while finishing a Business Information Systems degree with a Computer Science minor at Oregon State. I'm looking for a product, product operations or full-stack role, remote or in Portland, where I can own real products end to end.
Contact
Let's talk.
Open to conversations about product, operations and full-stack roles. The fastest way to reach me is email.