Open to new opportunities
Engineering systems.Building what scales.
Senior PHP & Laravel engineer with 8+ years of experience in backend architecture, scalable applications and complex software systems.
The engineer behind the systems.
I design and build the backend systems that business-critical products depend on — the APIs, data models, queues and integrations that have to keep working long after launch day.
For more than eight years I have worked primarily in PHP and Laravel, moving from feature development to owning architecture: shaping modular codebases, modelling complex domains, and making the trade-offs that keep systems fast, secure and maintainable as teams and traffic grow.
I work closely with frontend engineers — often in Vue.js — and with product teams, translating ambiguous requirements into clear boundaries and predictable software. Increasingly, I use AI-assisted workflows to move faster without lowering the bar on review, testing and design.
I also have good experience in developing Realtime services with GO lang.
8+
Years of professional programming
00
Projects in this portfolio
00
Product domains represented
Fig. 01 — A typical system I design
Engineering philosophy
- 01
Boundaries before features
Clear module boundaries and explicit contracts make a system easier to change than any clever abstraction.
- 02
Boring where it matters
Proven tools for the critical path; experimentation where the cost of being wrong is small.
- 03
Readable at 3 a.m.
Code, logs and data models should explain themselves to whoever is on call — including future me.
Key strengths
Where I add the most value to a team and a codebase.
- PHP & Laravel
- Backend architecture
- API design
- Database modelling & optimisation
- Modular application architecture
- Scalable business systems
- Authentication & authorisation
- Application security
- Third-party integrations
- Performance optimisation
- Technical leadership
- Vue.js & frontend collaboration
- AI-assisted development
Selected work, built to carry weight.
Three products from the archive — platforms with real users, real data and real constraints. The full index holds the rest.
Select a project to expand it
00 of 00 projectsFull index with filters
Explore all projectsTechnical range.
The tools and practices I reach for, grouped by the problems they solve.
- 03.01Primary craft
Backend Engineering
- PHP 8.x
- Laravel
- Eloquent ORM
- Queues & Horizon
- Events & listeners
- Laravel Octane
- Testing with Pest & PHPUnit
- 03.02Systems that grow
Architecture & Scalability
- Modular monoliths
- Domain-driven design
- Service boundaries
- Caching strategies
- Async processing
- Multi-tenancy
- 03.03Data that holds up
Databases & Infrastructure
- MySQL
- PostgreSQL
- Redis
- Query & index optimisation
- Docker
- Linux & Nginx
- CI/CD pipelines
- 03.04Contracts & connectors
API Development & Integrations
- RESTful API design
- Webhooks
- OAuth 2.0
- Payment providers
- Third-party SDKs
- API versioning
- 03.05Across the stack
Frontend Collaboration
- Vue.js
- Inertia.js
- TypeScript
- Tailwind CSS
- API-first workflows
- 03.06How the work is done
Security & Engineering Practice
- Authentication & authorisation
- OWASP practices
- Code review
- Technical leadership
- AI-assisted development
- Documentation
A career of compounding depth.
From shipping features to owning architecture — each role added scope, responsibility and a longer view of what makes software last.
Open to new opportunities
Have a system that needs to scale?
I'm interested in senior and lead backend roles, architecture work and ambitious products that need a dependable engineering partner. Tell me what you're building.
Direct channels
How we'd start
- 01
Share the context
A few lines about the product, the team and where the system is today.
- 02
A focused call
We talk through goals, constraints and where I can add the most value.
- 03
A clear next step
You get a concrete proposal: scope, approach and how we'd work together.