Product engineer for hire
I take a goal and build it. The right way, from the start.
I work with founders who need someone to own the technical direction completely — one person, moving fast, with no team to manage and no architectural shortcuts.
If you’re building something that needs a serious technical foundation, I’m the person who builds it.
How I think about systems
Before building anything, pressure-test the idea.
Every system has complexity that isn’t obvious until someone asks the right questions. This is a simplified version of how I scope serious technical work before a line of code gets written.
Describe what you’re considering — the analysis surfaces where the complexity lives, what an MVP actually requires, and where systems like this typically fail in production.
Try it with something you’re building — or just read how it works.
Describe the system
Sometimes this will suggest narrowing scope — and occasionally it will suggest not building something yet. That's part of the point.
Sometimes this will suggest narrowing scope — and occasionally it will suggest not building something yet. That’s part of the point.
What I build
Full systems. Not features.
I don’t implement tickets or hand off components. I design and build the entire system — data model, API layer, infrastructure, real-time interfaces, AI integrations, billing, admin tooling — and I own every decision along the way.
Marketplace platforms
End-to-end marketplace infrastructure — listings, transactions, vendor management, review systems, and the operational tooling that keeps it running. Built to handle real usage from the start, not retrofitted for it.
AI workflow systems
Production-grade AI systems designed as stateful execution graphs, not prompt chains. Human-in-the-loop where decisions matter. Auditable, resumable, and designed to fail loudly rather than silently.
Revenue and billing infrastructure
Deterministic billing systems that guarantee correctness under real-world failure conditions. Append-only ledgers, idempotent settlement, resilient webhook handling. Systems that converge to correctness rather than approximate it.
Internal tools and operational systems
The systems that make a business run — intake workflows, document processing, admin dashboards, communication infrastructure, reporting pipelines. Built for operators who need reliability, not just functionality.
How I work
I own the technical direction. You own the vision.
I take a goal, ask the right questions, and build the system. I don’t need a technical spec, a project manager, or a team of engineers to get started.
I make the architectural decisions, own the infrastructure, and ship working software in iterations. I work best with founders who have strong domain knowledge and a clear sense of the problem they’re solving — and who want a technical partner who can translate that into a real system without hand-holding.
I use AI deliberately to move faster than a traditional engineering team. Not to replace architectural thinking — to execute it faster.
I work as a founding engineer or technical co-founder, not a vendor or an agency. The relationship is direct and the ownership is real.
I build things designed to outlast the initial engagement — clean architecture, documented decisions, systems your next engineer can understand and build on.
I’m most useful at the beginning — when the architectural decisions are still open and the system can be built correctly rather than fixed later.
How I build
Built for systems that have to survive production.
Every system I build follows the same architectural principles regardless of domain or stack.
- Serverless AWS architecture
- Event-driven workflows
- Infrastructure as code
- Observability from day one
- Security boundaries and least-privilege access
Proof of work
See what I actually build.
The Matter & Gas platform is a live production system built end-to-end — structured intake, real-time AI analysis, authenticated project workspaces, scheduling, real-time messaging, and a full administrative system running on AWS serverless infrastructure.
The engineering case study documents every architectural decision and the reasoning behind it — not a portfolio of screenshots, but a system you can read and evaluate.
Who I work with
The right fit.
- Seed stage founders who need a technical partner, not a vendor
- Non-technical founders who want someone to own the architecture completely and make it work
- Venture studios spinning up new products that need to be built fast and correctly from the start
- Operators with a specific system to build and no internal engineering capability to build it
Not a fit.
- Companies that need a team managed or a process followed
- Projects that require a fixed-price quote before the problem is understood
- Founders who need to approve every technical decision before work moves forward
- Anyone who needs it built in two weeks
Currently available.
If you’re building something that needs a serious technical foundation and you want one person to own it completely — I’m worth talking to.