Founding engineer turned technical lead — and I run three of my own products. So the advice you get is from someone who still has to live with the decisions, not someone who moved on to slides.
You bring a codebase or a design you are unsure about. I go through it and tell you what will break, what to cut, and what to build next — in writing, so your team can act on it.
Ongoing sounding board for founders and small teams. Scoping an MVP, choosing a stack, deciding what is worth building — the calls you want to have before committing three months to something.
For engineers deciding what to do next. Levelling up, moving into lead roles, interview prep, or working out whether to go build your own thing. I have done all three.
Not case studies from a deck — live software with real users, where I own every decision.
Founding Engineer → Technical Lead
Shipped the production MVP in 2 months, then grew into leading a team of five. Cut load times 40% and deployment time 80%.
Frontend Developer
Publisher analytics dashboards. Lifted Lighthouse scores from 60 to 90+ and cut build times 70% by moving Webpack to esbuild.
Full Stack Developer
Built and launched a buyer-facing e-commerce platform from scratch. Checkout and UX work drove 3x revenue growth.
