work_with_me
Ways we can work together
From a focused review to building and running the whole thing: front-end, backend, cloud, and the AI on top. Pick the shape that fits where you are. If it's a software, cloud, or IT problem, it's worth a conversation.
Product Build
I build it with you, across front-end, backend, and cloud, shipped to a bar you can defend in production.
- Architecture, implementation, and delivery across the whole stack
- Production cloud on GCP (or your platform): CI/CD, observability, cost guardrails
- AI / LLM features wired in where they earn their place, in production rather than as demos
- A handover your team can own: docs, tests, and a clear runbook
best for: Founders who need a real product shipped, not a prototype.
Architecture & Cloud Review
A senior review of your stack (performance, scale, reliability, cloud cost, and AI readiness), with a roadmap you can act on.
- Architecture, performance, and reliability audit
- Cloud cost and scaling review: where the money and the risk are
- AI / production-readiness assessment
- A prioritized, written roadmap you can run with or without me
best for: Teams who want senior eyes on the system before they scale or raise.
Fractional Senior Engineer
An extra senior engineer and advisor on tap for your team and your roadmap, without a full-time hire.
- Hands-on delivery on your hardest features
- Architecture and cloud decisions, reviewed and de-risked
- Mentoring and code review that levels up the team
- A steady senior presence, dialled up or down as you need
best for: Teams that need senior depth without the full-time headcount.
also_on_the_table
And the wider engineering & IT work
The tiers above are the common shapes, but the range is broader. If it's a software, cloud, or IT problem, it's probably in scope. A few of the things I take on:
Build & ship
- Full-stack web apps: React / Next.js / Node / Python
- APIs & backend services
- Rescue & finish stalled or inherited projects
- Performance, refactoring & technical-debt work
Cloud & DevOps
- GCP / AWS architecture & migration
- Kubernetes, Docker, Terraform
- CI/CD pipelines & release automation
- Reliability, scaling & cloud-cost hardening
AI & data
- LLM & agentic features in real products
- Prompt, guardrail & evaluation design
- RAG & data pipelines
- Vertex AI / model integration
Advisory & IT
- Technical advisory & architecture consulting
- Code & security review
- Team mentoring & hiring support
- General IT & systems consulting
how_it_works
How an engagement starts
A 20-minute call
You tell me the problem and where you're stuck. I give you a straight read on how I'd approach it, and whether I'm the right fit.
A scoped proposal
A short written plan: scope, timeline, and a fixed or scoped price. No surprises, no lock-in.
We build, review, or ship
I work in the open: visible progress and tight feedback loops, held to a quality bar you can defend in production.
“His commitment to growth (his own and the team's) made for a genuinely motivating place to work. Collaborative, technically strong, and a natural leader.”
faq
Questions, answered
How do engagements usually start?
With a free 20-minute call. If it's a fit, I send a scoped proposal; if it isn't, I'll point you toward a better option.
Do you work fixed-price or hourly?
Reviews are fixed-scope, fixed-price. Builds are scoped per project. Fractional is a monthly retainer. Whatever's clearest for the work.
Can you work with my existing team and stack?
Yes. Most of my work is alongside an in-house team, in their codebase and on their cloud. I adapt to your stack, not the other way around.
Do you sign NDAs?
Happily. Most of my client work is under NDA; the case studies on this site are anonymized with permission.
Where are you based, and which timezones do you cover?
I work with teams worldwide, async-first, with calls scheduled to overlap your hours.
Have something to build, scale, or fix?
A 20-minute call. Tell me the problem; I'll tell you how I'd approach it, end to end.