Senior engineering, hired by the outcome

Your project, shipped end-to-end

I'm a director of engineering who still builds. I take on a small number of engagements each year — product builds, integration work, and short technical-strategy projects where deep ownership matters more than bench depth.

Start a conversation → See engagement types →

14+ years shipping production systems Fixed price or hourly San Francisco · remote worldwide

Ways to hire me

Three engagement shapes

4–12 weeks

Fixed-scope build

A working product, internal tool, CMS site, or service shipped end-to-end — design through deploy — with a defined launch target and a fixed price. Sano, below, is a good example.

1–4 weeks

Integration slice

A focused API, webhook, data pipeline, auth flow, or workflow automation that needs senior ownership, priced fixed or hourly by shape.

1–2 weeks

Advisory sprint

Architecture review, AI-delivery workflow setup, technical due diligence, or roadmap shaping — hourly, with a written handoff you keep.

Selected engagements

Recent work

Sano

2025

Custom jewelry artisan · E-commerce / Brand

A CMS-driven marketing and inquiry-cart site for an independent jewelry maker, built end-to-end from design through deploy.

React
TypeScript
Vite
Sanity CMS
TailwindCSS
shadcn/ui
TanStack Query
Vercel
Resend
Airtable

Sano is a brand site for a custom jewelry artisan. The client needed a presentable, low-maintenance storefront that they could update without engineering involvement — but with enough polish to compete with established e-commerce brands. The result is a single-page React app whose content (hero, story, collection, portfolio, team, testimonials, blog) is entirely managed through a Sanity Studio instance, with updates publishing instantly via the Sanity CDN.

The frontend is React 18 + TypeScript bundled by Vite, with a custom Tailwind theme defining jewelry-specific design tokens (jewelry-gold, jewelry-silver, jewelry-ivory). UI primitives come from shadcn/ui on top of Radix UI, with TanStack Query handling data fetching against the Sanity API via GROQ queries. Typed content hooks in src/hooks/useSanityContent.ts provide a single point of access for each content type.

Commerce is intentionally inquiry-based rather than transactional: a cart drawer lets visitors collect pieces they’re interested in and submit a purchase inquiry. The submission flows through Vercel serverless functions, lands in an Airtable base for the client’s pipeline, and triggers an email notification via Resend. A Shopify integration was scoped and removed in favor of this lighter model — better fit for one-of-a-kind work where each sale is a conversation, not a checkout.

Deployment is Vercel-managed on push to main, with the Sanity Studio deployed separately on Sanity’s own hosting. Coverage includes Vitest unit tests and Playwright end-to-end tests.

Capabilities

What I work on

Backend & platform

API design and full-stack product builds
Database modeling, ORM strategy, query performance
Microservices and event-driven architecture

Integrations & data

Third-party API and webhook integrations
ETL/ELT pipelines and analytics infrastructure
CMS-driven sites with custom content models

AI-native delivery

SDLC automation and tool-agnostic AI workflows
Agentic skills and orchestration patterns
Productivity measurement and quality gates

Technical strategy

Technical due diligence and architecture review
Engineering team and process consulting
Roadmap shaping and tech-debt strategy

Fit

Good fits & not-so-good fits

A good fit

Founder, operator, or small team that needs a senior engineer to own a project end-to-end
An existing system needs an integration, a CMS-driven site, or a focused backend service built
An engineering team needs an outside perspective on architecture, AI workflows, or delivery practice

Not a good fit

Anything that needs full-time, daytime availability (I'm employed and work side engagements off-hours)
Body-shop staffing or open-ended “extra hands” work without a clear outcome
Pre-product-market-fit pivots where the scope changes every week

Common questions

FAQ

Are you available right now?

I run a small queue. Reach out with what you’re working on and a rough timeline. I’ll tell you honestly whether I can take it on, when, and whether someone else would serve you better.

How do you price?

Depends on shape. Fixed-scope projects get a fixed price after a short scoping conversation. Hourly work is straight time-and-materials — best when the shape of the work is still being figured out. I’ll share specifics once I understand what you need.

Do you work nights and weekends?

Yes, that’s the constraint I’m honest about. I’m employed full-time, so client work happens off-hours. For most fixed-scope builds this is fine. For engagements that need daytime availability or real-time customer support, it isn’t.

What about ongoing support after launch?

Every fixed-scope project ships with a short warranty period for fixes. Beyond that, I’ll either hand off cleanly or stay on hourly for ongoing changes, whichever fits.

Have a project in mind?

Send the outcome you want, what exists today, your rough deadline, and any constraints I should know up front. I read every message.

Start a conversation →