Product Engineering
Spec-Driven Delivery: The Missing Layer in Agile Teams
Why agile breaks under ambiguity, how lightweight specs prevent rework, and why AI-assisted engineering makes acceptance criteria non-negotiable.
Read article →How I lead
VP–Engineering
Fit architecture to the stage
Stack, sequencing, and what can wait — built for where the company is, with a path to where it is going.
Make ownership real
Named owners, a delivery rhythm you can inspect, and a clear line between speed and quality.
Hold the hard calls
Scope, debt, stack, and when to say no. Someone has to own the tradeoff.
Stay after launch
First users, first real load, first messy growth. That is still the job.
VP–Engineering · 10+ years in product engineering
I work with founders and business leaders to shape technology decisions, guide engineering teams, and take products from idea to scale.
Experience
10+
Years in engineering
15+
Products & platforms
1
Startup founded
20
Engineers led
Startup founder background
Node.js · PostgreSQL · AWS
Fintech & payments
Enterprise-scale delivery
Team leadership
AI-assisted engineering
Judgment
Clarity before the build. Architecture that matches the stage. Delivery that is visible and owned. AI only where it creates value someone can defend.
Thinking
Notes from the work — how products get built, how teams deliver, and where AI is actually useful.
Product Engineering
Why agile breaks under ambiguity, how lightweight specs prevent rework, and why AI-assisted engineering makes acceptance criteria non-negotiable.
Read article →AI & Automation
Why this hybrid role is emerging, what it owns end-to-end, and how teams can ship reliable AI features with evaluation and governance.
Read article →Product Engineering
What FDEs do, how they differ from Solutions Engineering, and how founders can avoid turning customer delivery into a services trap.
Read article →Connect
I read and reply there.