I build backend systems that don't fall over — REST APIs, real-time features, and the CRUD nobody wants to write twice. Currently extending into full-stack work with Next.js.
I started out writing PHP because it was the fastest way to ship something real, and stuck with Laravel because it rewards doing things properly — clean migrations, real relationships between models, jobs that don't silently fail. Most of what I build lives behind the scenes: the API that a frontend team trusts to just work.
Replace this paragraph with your own story: what pulled you into backend work, the kind of problems you actually enjoy solving (auth systems? real-time features? messy data cleanup?), and what you're building toward now.
Currently extending into full-stack work with Next.js and Node — this site is part of that.
A Laravel + Next.js CRM covering task management, meetings, attendance, finance dashboards, and a payment gateway module.
Problem solved: Built real-time push notifications with Ably (JWT-scoped token requests) so task and meeting updates land instantly on the Next.js frontend, instead of relying on polling.
A full-featured Laravel REST API covering catalog, cart, orders, promotions, and loyalty — 36 migrations, cleanly normalized.
Problem solved: Designed a database schema that handles promotions and loyalty points without locking the catalog into rigid assumptions, then scaffolded Eloquent models and relationships to match.
An AI API integration added to an existing Laravel project — replace this with what you build (smart search, auto-summaries, etc).
Problem solved: Describe the real problem this solved once you've built it — what was manual before, and what the AI call automated.
Open to full-stack and backend roles, freelance work, or just talking shop about Laravel and API design.
built with Next.js · deployed on Vercel