Senior full-stack developer,
strongest on the backend
Writing production code since 2016 — I started with hand-coded markup, moved into PHP
and Laravel, and grew into architecture and tech lead work. Today I design systems,
own the hard parts of the backend, and cover the frontend when a project needs it.
Mostly service and outsourcing teams, which means a lot of different domains,
codebases and stacks. That variety is the point — it is what makes onboarding
into an unfamiliar project routine instead of risky.
Ten years of mostly non-product companies taught me one skill above the rest: reading
someone else's system quickly, understanding why it is the way it is, and making changes
that do not break it.
Backend architecture
Where I am strongest. Data models that survive the next feature, APIs that are boring to
consume, queues and caching where they belong. No N+1 queries, no per-row loops — bulk
and set-based by default.
Full-stack delivery
A feature is not done at the API boundary. I take it through to the interface — Vue,
TypeScript, accessible markup — so nothing is left waiting on someone else's sprint.
Fast onboarding
New domain, undocumented legacy, a stack I have not touched in a year — I map it, ask
the questions that matter, and open a useful pull request in the first week.
03 — AI-augmented engineering
I use AI every day — as an amplifier, not an autopilot
Modern delivery speed is not optional any more. I run Claude and Copilot inside my daily
loop, and I keep the same review bar I always had. The model drafts; I decide what ships.
Faster exploration. Mapping an unfamiliar codebase, tracing a call
path or summarising a legacy module takes hours instead of days.
Boilerplate and migrations. Scaffolding, repetitive refactors and
mechanical rewrites get delegated, so my attention goes to design decisions.
Tests and review. A second pass over every diff — edge cases, error
paths and the questions a tired reviewer would miss.
AI features in products. LLM integrations, prompt design and the
plumbing around them — retries, cost control, guardrails, evaluation.
04 — Stack
Tools I reach for
Technologies I have worked with across a decade of production projects.
Backend
PHP 5–8
Laravel 5–12
Symfony
REST APIs
Queues & workers
Third-party integrations
Data
PostgreSQL
MySQL
Redis
Query optimisation
Schema design
Frontend
Vue 2–3
Pinia / Vuex
TypeScript
Vuetify
Semantic HTML & CSS
jQuery (legacy rescue)
Infrastructure
Docker
CI/CD pipelines
Nginx
Linux
Cloudflare
Monitoring & error tracking
AI & process
Claude Code
GitHub Copilot
LLM API integration
Git
Jira / Trello / Notion
Code review
05 — Journey
From markup to architecture
Ten years in one direction. No career pivots — every layer I learned made the layer
above it cheaper to build, which is why I can now hold a whole system in my head
instead of just my slice of it.
01
Foundation — the browser
I started in 2016 turning designs into markup. Nobody calls that architecture, but it
is where I learned that structure is a decision: semantics, document order, how a
layout behaves when the content is twice as long as the mockup promised. It is still
the reason the interfaces I ship are accessible and fast, not merely finished.
02
Depth — PHP and Laravel
Then the centre of gravity moved server-side and stayed there. Data models, business
rules, third-party integrations, migrations you cannot roll back once they have run.
This is the work I am best at, and it taught me the two lessons I still lead with:
most bugs are data-shape problems, most slowness is query-shape problems, and both
are decided long before anyone writes a controller.
03
Range — full-stack and infrastructure
Vue on the front, Docker and CI/CD underneath — not to collect logos, but to delete
handoffs. A feature I can follow from the migration through the API to the component
and into a deployment never sits in a queue waiting on someone else's sprint. On a
small team that single difference is most of the timeline.
04
Ownership — architecture and technical leadership
Today the work is mostly decisions: what the system needs to look like in a year,
which shortcuts are worth taking, which ones get paid back with interest. I make the
architectural calls, build the parts that are hardest to get right, and review the
rest. AI tooling runs inside that loop — it raised my baseline speed without touching
the bar for what actually ships.
06 — Contact
Let's talk about your project
Tell me what you are building and where it hurts. If I am not the right fit, I will say
so quickly.
