03 Experience

Full-stack projects, AI implementations, and systems architecture

A record of technical execution: AI agent pipelines, full-stack web applications, e-commerce platforms, high-traffic CMS rebuilds, and API automation.

01 Selected work

Problems solved, outcomes measured

Engineering case studies across AI agent integration, full-stack applications, and high-scale platforms.

  • AI Integration u0026 Customer Support Agent

    Integrated multi-turn RAG search, OpenAI embeddings, and Pinecone vector search into an enterprise support platform.

    65% reduction in support response times with 98% accuracy on technical documentation queries

    • Next.js
    • OpenAI API
    • Pinecone
    • LangChain
    • RAG
  • Full-Stack Web Platform · Next.js u0026 Microservices

    Architecting a Multi-Tenant SaaS Portal with Real-Time Analytics

    Designed a scalable Next.js application with modular dashboard widgets, real-time webhooks, and automated subscription billing.

    Sub-second dashboard loading speed for over 50,000 active monthly users

    • React
    • Next.js
    • Node.js
    • PostgreSQL
    • Tailwind
  • High-Traffic Commerce u0026 Data Integration

    Scaling High-Volume E-Commerce u0026 n8n Automated Webhook Pipeline

    Built high-throughput n8n webhook automation and catalogue synchronization handling enterprise checkout volume with zero payload loss.

    100% reliable webhook delivery with zero lost transaction records during peak sales events

    • WooCommerce
    • Shopify
    • n8n
    • Redis
    • REST API
See all case studies →
02 Track record

Roles and responsibilities

The professional timeline behind the case studies.

  1. Present

    Senior Engineer – Enterprise WordPress & Web Platforms

    Enterprise platform engineering · WordPress, React, integrations

    Engineering and maintaining large WordPress platforms and the applications around them, where uptime, editorial velocity, and code quality carry equal weight.

    • Design plugin and block architecture around clear boundaries, so features ship independently of the theme layer.
    • Own performance work end to end: query profiling, object and page cache strategy, Core Web Vitals, and asset delivery budgets.
    • Gate quality with PHPCS, PHPStan, and GitHub Actions pipelines instead of relying on review discipline alone.
    • Build REST, GraphQL, and third-party integrations with defensive error handling, retries, and observable failure modes.
    • Mentor developers through review, pairing, and written documentation of recurring engineering patterns.
    • WordPress VIP
    • PHP
    • Gutenberg
    • React
    • GraphQL
    • GitHub Actions
    • PHPStan

  2. Earlier

    Full-Stack Engineer – Commerce & SaaS

    WooCommerce, Shopify, and custom application work

    Led commerce and product engineering across WooCommerce and Shopify storefronts alongside custom SaaS and application builds.

    • Extended checkout and product workflows without forking core behaviour, keeping upgrade paths intact.
    • Built custom Shopify themes and app functionality, including accessibility and ADA compliance work.
    • Delivered API-driven React and Next.js front ends against WordPress and bespoke backends.
    • Cut page weight and server response times through caching layers, database indexing, and query reduction.
    • WooCommerce
    • Shopify
    • React
    • Next.js
    • MySQL
    • Nginx
    • Cloudflare

  3. Foundations

    Web Developer – Themes, Plugins & Integrations

    Custom development, CMS platforms, and automation

    Built the fundamentals: theme and plugin development, the WordPress data model, CMS integrations, and the discipline of reading core before extending it.

    • Developed custom themes and plugins across a wide range of content models and integrations.
    • Connected CMS and marketing platforms – Contentstack, HubSpot, Wix – into shared content pipelines.
    • Automated repetitive business processes with Make.com, n8n, and GoHighLevel workflows.
    • Learned to debug at the query, hook, and HTTP layers instead of guessing at symptoms.
    • PHP
    • JavaScript
    • MySQL
    • Contentstack
    • HubSpot
    • n8n
    • Git

Questions about engagements and process

How does an engagement usually start?
With the problem and the constraint, not the solution. What is failing, what the platform has to keep doing while it is fixed, what cannot be changed, and what the deadline actually is. Most projects that go badly do so because a solution was chosen before the constraint was written down.
What does an architecture or performance audit produce?
A prioritised set of findings with evidence attached – query profiles, cache hit rates, rendering waterfalls and the specific code paths responsible – ranked by impact against effort. The deliverable is something an existing team can act on themselves, not a proposal for more work.
Can you work alongside an in-house engineering team?
That is the usual arrangement. The work goes through the same pull requests, review and CI as the rest of the team, and the patterns get documented as they are introduced. An engagement that leaves a team unable to maintain what was built has failed regardless of what shipped.
How is progress measured on this kind of work?
Against numbers agreed before the work starts. On performance that means Core Web Vitals targets, server response budgets and query counts per template. On architecture it is deployment frequency and how much of the codebase a given change has to touch. Vague success criteria produce vague outcomes.
Which parts of the stack do you own end to end?
Front end through infrastructure: React and Next.js interfaces, PHP and Node.js application layers, MySQL and PostgreSQL data models, Redis and Memcached caching, CI pipelines with PHPCS and PHPStan gates, and the deployment path onto WordPress VIP or cloud hosting.