02About

Engineer by trade, builder by habit.

I started with WordPress in 2017, as an intern at Designs Valley, and spent the first years learning the craft on real client work: custom themes, plugins, WooCommerce stores, migrations and launches.

That work kept pulling me deeper into the backend. Custom checkout logic became fulfilment integrations; integrations became Laravel applications; applications became full SaaS products with billing, queues and dashboards. Somewhere along the way the job stopped being "build the site" and became "own the system".

Today I work across the stack, mostly in Laravel and React, on products where the interesting problems are in the data, the background processing and the edges where systems meet. I also spend a growing share of my time on AI engineering: retrieval, agents and tool use, and how to put a language model inside an application without giving up control over what it can see and do.

AExperience

Where I’ve worked.

Agencies, product teams and international clients: nine years of shipping work that other people depend on.

  1. 2026 — Now
    Cart CompoundFreelance

    WordPress, WooCommerce & Laravel Engineer

    Jun 2026 — Now
  2. 2022 — Now
    Titan Dev AgencyContract

    Full-Stack PHP Developer

    Jul 2024 — Now

    Laravel, FilamentPHP, automation platforms, APIs, background jobs and production system improvements.

    Full-Stack WordPress Developer

    Mar 2022 — Jul 2024

    Custom themes and plugins, WooCommerce workflows, Gutenberg blocks and ACF systems.

  3. 2019 — Now
    IndependentInternational clients via Upwork & Fiverr

    WordPress & WooCommerce Developer

    Apr 2019 — Now

    Custom builds, commerce, performance work and long-running site improvements for clients abroad.

  4. 2017 — 2021
    Designs ValleyFull-time

    WordPress Developer

    Jul 2017 — Dec 2021

    Started as an intern and grew into a full development role: themes, plugins, WooCommerce, migrations, launches, and supporting junior developers.

BStack

The tools, by depth.

Ordered by how much of my work happens in them, not by how impressive they sound.

FoundationWhere most of my work lives
  • Laravel1
  • PHP1,2
  • MySQL1
  • JavaScript
  • React3
  • WordPress & WooCommerce2,4
ToolkitWhat I reach for regularly
  • FilamentPHP
  • Livewire
  • TypeScript
  • Tailwind CSS
  • REST APIs & webhooks
  • Stripe & Cashier
  • Queues & scheduled jobs
  • PostgreSQL
  • Linux, Nginx & systemd
  • GitHub Actions
  • AWS
  • Google APIs & BigQuery
FrontierWhat I'm exploring now
  • Python3,5
  • LLM integrations1
  • RAG3
  • AI agents & tool use3
  • Local models (Ollama)3
  • Workflow automation

Seen in — 1 OutreachFlow 2 UnderFit 3 RAG Support Agent 4 B2B Mint 5 Email Verifier

CCurrently curious about

AI, the engineering way.

Agents that stay inside the lines

Letting a model choose which tool to call is useful. Letting it choose whose data it reads is not. I like designs where scoping, permissions and read-only access are enforced by the system rather than requested in the prompt.

Local-first AI

Running the LLM and embeddings on your own machine with Ollama removes API keys and per-request cost, and changes which experiments are worth trying.

Products, not demos

The model is the easy part. Billing, retries, rate limits, background work and honest failure states are what turn an AI feature into something people rely on.

DPrinciples

How I like to build.

  1. Plan the structure in writing

    Before the code multiplies, I write down the architecture, the conventions and the edge cases. It feels slow on day one and pays for itself every week after.

  2. Conventions are architecture

    Thin jobs, focused services, enums that own their labels, one class that owns every rate. Small rules applied consistently are what keep a codebase workable for one person or for ten.

  3. Boring infrastructure, deliberate seams

    A database queue and a modest server can launch a product. What matters is that nothing in the design blocks the move to Redis or bigger hardware when usage asks for it.

  4. Fix the cause, not the symptom

    Problems get investigated rather than hidden behind patches. A production incident should leave behind a rule that prevents the next one.

  5. Be honest about the edges

    Known gaps get documented, not buried. A system you can reason about includes the parts that don't work yet.

→Get in touch

Let’s talk
engineering.

hi@ahmadthedev.com