Data model and API
PostgreSQL, SQL Server, MySQL or MongoDB schemas designed around the domain, exposed through Nest.js, Express or Laravel with a typed contract the frontend can rely on.
Most projects do not need a frontend contractor and a backend contractor negotiating across a ticket board. They need one engineer who can model the data, build the API, ship the interface and put the whole thing into production. That is the work I do: end-to-end product engineering across React and Next.js frontends and Nest.js or Express APIs, from schema to deployed feature.
PostgreSQL, SQL Server, MySQL or MongoDB schemas designed around the domain, exposed through Nest.js, Express or Laravel with a typed contract the frontend can rely on.
React and Next.js interfaces built on the same TypeScript types as the API, so contract changes fail at compile time instead of in front of users.
Approval chains, role and permission models and audit trails — the parts of enterprise software that are hard to retrofit and easy to get subtly wrong.
Docker, Nginx and CI/CD onto AWS or Vercel, so shipping is a routine operation rather than an event.
Projects where I have already done this, written up as case studies.
Permission-driven ERP covering HR, finance, procurement, approvals, payroll and audit.
Read case study: FHRADC Enterprise Management SystemHigh-scale event ticketing platform stress-tested to 100,000 concurrent users.
Read case study: The Ticket CentralAI-powered customer engagement platform automating conversations, leads and marketing workflows.
Read case study: VoxBox MarketingUS real-estate platform — cross-account AWS migration, HLS live streaming, first Play Store release.
Read case study: PropQwizReal-time soccer player-performance analytics behind a secure Node.js OAuth proxy.
Read case study: Insider Analytics IntegrationEnterprise support and project management portal used across Irish medical departments.
Read case study: OCM SupportLab management system running in Irish government hospitals, plus a legacy VB6 migration.
Read case study: OCM — Medical Lab Management SystemResponsive marketing site for a construction materials supplier, with multi-language navigation.
Read case study: Golden M InternationalOn my projects: the database schema, the API, the frontend that consumes it, and the deployment pipeline that puts it in production. On the FHRADC Enterprise Management System that means the complete Finance domain — budgeting, financial workflows, approvals and accounting operations — rather than a slice of the frontend handed off to someone else.
Both. A large share of my work has been joining live systems — stabilising the HLS streaming module in PropQwiz, migrating the Histology application off a legacy VB6 codebase onto Laravel, and adding modules to platforms already in production.
Nest.js when the project is TypeScript end to end and will grow past a handful of modules, because the structure pays for itself. Express when the surface is small and the overhead is not worth it. Laravel when the team or the existing system is PHP. I have shipped production systems on all three.
Both, and for agency subcontracting. I currently work as a Full Stack Engineer at Tech Direct Support and take on contract and freelance engagements alongside it.
If full stack development is what you need, tell me about the system, the constraints and the timeline.