Services
What you get, how it is shaped, and who writes the code.
Four areas of work, three shapes of engagement. All of it delivered by one senior engineer — the same one you speak to on the first call.
Disciplines
What each area actually covers.
Most engagements combine two of these. The mix is set during scoping, not sold as a package.
Product engineering
Ship the roadmap, not the backlog
Embedded in your team as a senior fullstack engineer, turning specs and Figma files into features your users actually get. Discovery, implementation, review, release.
- React, Next.js, React Native and TypeScript, end to end
- Design-faithful interfaces, down to the empty states
- Weekly releases behind feature flags
Code quality & DX
Make the fast path the safe path
A codebase that is still pleasant at month twenty-four. Typed boundaries, tests that catch real regressions, CI that answers in minutes, and review standards the whole team can hold.
- Typed contracts between client and API
- Test suites that pay for their runtime
- CI, linting and release automation
Architecture & scale
Built for the traffic you are about to get
Systems that hold under load and stay cheap to run. Caching, server and edge rendering, data-access patterns, and the unglamorous instrumentation that tells you what broke before your users do.
- Server and edge rendering, caching strategy
- Query and data-access performance work
- Observability, alerting and incident follow-up
AI product engineering
AI features that earn their place
LLM features built like the rest of the product: evaluated, cost-aware, and useful without a demo script. Streaming interfaces, tool calling, retrieval, and guardrails that survive real input.
- Streaming interfaces and tool-calling agents
- Retrieval and context pipelines
- Evaluation, cost and latency budgets
Engagements
Three ways to work together.
Same engineer, different shapes of commitment. Rates are shared on the first call — there is no discovery invoice to find them out.
Build sprint
2–6 weeks
A defined outcome shipped end to end: a new surface, a migration, a release that has been stuck in the backlog.
Includes
- Fixed scope agreed up front
- Weekly demo and written update
- Handover document at the end
- Most common
Embedded engineer
3–6+ months
Part of your team, in your rituals and your repo. The default for teams with more roadmap than engineers.
Includes
- Daily standups and code review
- Full ownership of a product area
- Mentoring and standards along the way
Codebase audit
1 week
A written read on architecture, performance, tests and delivery speed — with the fixes ranked by what they buy you.
Includes
- Architecture and dependency review
- Performance and cost findings
- Prioritised remediation plan
How it works
From first email to first release.
No discovery phase that bills for six weeks before anything runs. Four steps, and working software in the first one.
- 01
Scoping call
Thirty minutes on what you are building, what is in the way, and whether I am the right person for it. No deck.
- 02
Written proposal
Scope, milestones, rate and start date on a single page. You know exactly what you are buying before anything is signed.
- 03
Ship in week one
The first pull request lands in the first week. Small, reviewable changes from the start — no three-week silence.
- 04
Hand back stronger
Documentation, tests and a team that can keep going without me. The goal is to become unnecessary.
Toolkit
The stack behind the work.
Chosen because they hold up, not because they trended. If your team is already productive in something else, that matters more than my preferences.
- Frontend
- ReactNext.jsTypeScriptAstroTanStackTailwind CSSVue.js
- Mobile
- React NativeExpoiOSApple WatchAndroid
- Backend
- Node.jsNestJSHonoGraphQLtRPCPostgreSQLREST
- Platform
- CloudflareAWSGoogle CloudDockerGitHub ActionsNx
- Testing
- PlaywrightCypressJestReact Testing LibraryTDD
- AI
- LLM APIsRAGTool callingStreaming UIsEvaluation
Next step
Tell me what you are building.
Your product, your timeline, and the part that is currently in the way. That is enough for a useful first reply — and you will get a straight answer, including when someone else is the better fit.