whoami

Taibouni Abdel Hafid

Senior Full-Stack Engineer · Laravel & PHP · Vue · Databases · DevOps

I rescue slow legacy PHP, rebuild it in Laravel, and own everything around it: the Vue and Svelte front ends, the databases, and the servers they run on.

  • Available now
  • 15+ years in production
  • Remote from Algeria · UTC+1, CET-aligned
  • Top Rated on Upwork · 34 jobs · $50K+
Book a 30-min callEmail me

stats --production

Results from real systems

~70%

faster legacy survey engine

35s → 11s at Group Caliber

130 → 32

database queries per request

grouped lookups, upserts, caching

100%

uptime on ZimouExpress

1,000+ parcels a day across Algeria

100K

storefront requests a day

at near-zero hosting cost

6–10

developers led as CTO

daily PR reviews across 2–3 repos

15+

years in production

PHP since 2012, security since 2011

skills --all

What I work with

Backend

PHP 8 and Laravel since 2012. I modernize legacy PHP without stopping the business.

  • Laravel
  • PHP 8
  • Filament
  • Livewire
  • REST APIs
  • OAuth
  • Queues
  • Reverb

Frontend

Vue 3 is my current focus, next to Svelte (Caliber v2, this site) and React/Next.js (storefronts).

  • Vue 3
  • Svelte 5
  • React / Next.js
  • Alpine.js
  • Tailwind
  • Drag & drop UIs

Data & performance

From query plans and indexes to choosing the right engine for analytics.

  • MySQL
  • SingleStore
  • PostgreSQL
  • TimescaleDB
  • Redis
  • Indexing
  • Caching
  • Imports

Infrastructure & DevOps

I set up the servers, the deploys and the monitoring, and I get paged when they break.

  • Docker
  • Compose
  • Laravel Forge
  • Cloudflare
  • Nginx
  • Linux
  • CI/CD
  • AWS
  • Vercel

Leadership

Former CTO of 6–10 developers. I split big problems so people can build in parallel, and still write the hard code.

  • Code review
  • Architecture
  • Hiring
  • Mentoring
  • Remote / async

Security

CTF player and Root-Me challenge author. I review every PR the way an attacker would read it.

  • Secure code review
  • OWASP
  • Turnstile / anti-bot
  • Hardening
  • Pentesting

projects

Case studies

01

Rescuing a legacy SaaS, then rebuilding it as v2

Group Caliber ApS · Danish brand & reputation tracking SaaS · Oct 2021 – Oct 2026

  • Survey engine ~70% faster (35s → 11s, 15s → 4.5s)
  • DB queries cut up to 75% (130 → 32)
  • Non-developers now manage the calculation rules
  • 5 years inside a Denmark-based team on CET hours
Problem and what I did

Problem. A native-PHP backend had become too slow to use. At its core sat a 10,000-line, 22-parameter function that only its original author could change.

What I did. Turned the legacy backend into a working product, then rebuilt it as v2 in Laravel and Svelte, database migration included. Replaced the giant function with a clean class structure and moved its calculation rules into an admin dashboard. Optimized upserts, grouped lookups and added runtime caching in the survey engine.

  • Laravel
  • Svelte
  • MySQL
  • Caching
  • Refactoring

02

Analytics at scale: SingleStore, PostgreSQL and TimescaleDB

Group Caliber ApS · brand & reputation tracking SaaS

  • Heavy aggregations moved off the transactional database
  • Large imports from stores and spreadsheets into analytics tables
  • Data-driven choice between SingleStore and Postgres + TimescaleDB
Problem and what I did

Problem. Reporting meant large aggregations over millions of rows, and a classic MySQL setup was the wrong tool for that kind of load.

What I did. Ran analytics workloads on SingleStore in production, tuned the heavy aggregation queries and the import paths that feed them, and ran a PostgreSQL + TimescaleDB proof of concept for the time-series side (hypertables and pre-computed aggregates).

  • SingleStore
  • PostgreSQL
  • TimescaleDB
  • MySQL
  • Laravel

03

The cockpit: one click, one new ERP client

ZimouGroup · CTO & shareholder · Sep 2023 – Jul 2026

  • Manual server setup replaced by automated onboarding
  • One OAuth hub for every instance
  • Product later became Yalidine's Aventy
Problem and what I did

Problem. Every client of the MyEcom ERP needed a dedicated instance, and setting each one up by hand was slow and error-prone.

What I did. Built a Filament control panel that provisions and deploys a dedicated Laravel ERP per client, orchestrating servers, sites, DNS and frontends through the Laravel Forge, Cloudflare and Vercel APIs, with provisioning running through Laravel queues. Added a central OAuth service that manages Google and other third-party connections, token refresh included, for every instance.

  • Laravel
  • Filament
  • Queues
  • Forge API
  • Cloudflare API
  • Vercel API
  • OAuth

04

Production infrastructure, owned end to end

ZimouGroup · Orestor · Group Caliber

  • 100% uptime on ZimouExpress at 1,000+ parcels a day
  • Dedicated database server with a replica
  • Zero-touch deploys on any infrastructure
Problem and what I did

Problem. Small teams running real traffic, with nobody whose full-time job was the servers.

What I did. Containerized dev and production stacks with Docker and Compose. Set up zero-downtime deploys through Forge and CI, Cloudflare in front of everything, and monitoring with Bugsnag and Nightwatch. After the ZimouExpress incident, moved the database to its own server with a read/write replica. At Orestor, ran load-balanced Linux servers across physical machines, VPS and cloud.

  • Docker
  • Compose
  • Laravel Forge
  • Cloudflare
  • Nginx
  • Linux
  • CI/CD
  • Bugsnag
  • Nightwatch

05

Making order dispatch reliable

MyEcom ERP, later Yalidine's Aventy · ZimouGroup

  • Reliable dispatch to third-party couriers
  • Real-time order notifications
Problem and what I did

Problem. The team had struggled to get the ERP's queue system working, and orders to delivery companies were unreliable.

What I did. Rebuilt the Laravel queue system and added real-time order notifications with Laravel Reverb and WebSockets.

  • Laravel
  • Queues
  • Reverb
  • WebSockets
  • Redis

06

ZimouExpress, a delivery hub for Algeria

ZimouGroup

  • 1,000+ parcels a day
  • All wilayas covered
  • 100% uptime
Problem and what I did

Problem. Sellers had to juggle several courier companies, each with its own system.

What I did. Kept the Laravel hub that connects Algeria's courier companies running and growing.

  • Laravel
  • Courier APIs
  • Linux
  • Cloudflare

07

Storefront platform at near-zero cost

ZimouGroup · ERP ecosystem

  • 100K requests a day
  • Near-zero hosting cost
  • ERP origin never exposed
Problem and what I did

Problem. Each ERP client needed a public storefront without ever exposing the ERP's own address.

What I did. Built a platform on Next.js and Turso that gives every client its own storefront and proxies orders into their ERP.

  • Next.js
  • Turso
  • Vercel
  • Proxying

08

Orestor, a Shopify-like store generator

Co-founder, head developer & sysadmin · Feb 2018 – Aug 2021

  • Automated full-site generation
  • Zero-touch deploys on any infrastructure
  • Owned production end to end
Problem and what I did

Problem. Merchants needed complete, hosted online stores generated automatically.

What I did. Primary backend engineer. Built a custom lightweight MVC framework for full-site generation and a zero-touch deployment pipeline with auto-configuration across physical servers, VPS and cloud. Ran production: load balancing, Linux, Cloudflare, monitoring and client onboarding.

  • PHP
  • Custom MVC
  • Linux
  • Load balancing
  • Cloudflare

cat incident.log

The day the database died

Mid-afternoon on a busy day at ZimouExpress, thousands of parcels were being created, and the server went dark: the hosting bill had gone unpaid and the provider cut it off.

When it came back, MySQL would not stay up. The InnoDB files were corrupted, and a forced-recovery restart failed.

I moved the damaged production files aside, started MySQL on an empty database with the same name and structure, ran the repair, and swapped the original files back in at the right moment. The data came back.

resolved: Afterwards the database got its own server with a read/write replica, and monitoring through Forge, Bugsnag and Nightwatch. That night is why ZimouGroup hired me.

reviews

What clients say

Hafid is very skilled in PHP, backend development and Laravel. He tackles tasks with a great attitude and mind set. He helped us refactor and optimize on an existing PHP backend, and not only did he do the tasks appointed, he also identified other areas to improve on both security, performance and maintainability.
Henrik B., client · Upwork
Taibouni was enormously helpful to us in uncovering issues in our setup and code and assisted us onto the right path to resolution. He was professional and courteous at all times and his experience was evident in the final work!
Client · Upwork

Top Rated · 34 jobs · 25 reviews · $50K+ earned · Upwork profile

experience

Experience

  1. Oct 2021 – Oct 2026

    Senior Full-Stack Developer (Laravel & Svelte)

    Group Caliber ApS · remote, Denmark

    Legacy rescue, v2 rebuild, ~70% faster survey engine

  2. Sep 2023 – Jul 2026

    Chief Technology Officer & Shareholder

    ZimouGroup · remote

    Hands-on Laravel lead: cockpit, queues, ZimouExpress, storefronts, hiring and mentoring. Occasional consultant since.

  3. Feb 2018 – Aug 2021

    Co-Founder, Head Developer & SysAdmin

    Orestor · Algeria

    Shopify-like platform, custom MVC framework, zero-touch deployment

  4. Feb 2012 – Aug 2018

    Freelance Full-Stack Developer

    Clients incl. Katy Computer Specialists

    PHP apps, databases for high-traffic lead-gen platforms, hardening and tuning

  5. 2011 – 2012

    CTF player & challenge author

    Root-Me · Blindp0wn3rs

    Authored 3 realist challenges, published CTF write-ups

man hafid

Questions people ask

Where are you based, and what hours do you work?

Algeria, UTC+1, aligned with CET. I spent five years inside a Denmark-based team on CET hours, fully remote.

Full-time or contract?

Both. I'm open to full-time remote roles and to contract work, from a short audit to owning a product's backend.

How do you take over a codebase you didn't write?

Read it the way an attacker would: config, secrets, auth, queries, uploads, servers. Then fix what's dangerous first and refactor in small steps that ship, so the business never stops. Type audit in the terminal for my checklist.

How do you use AI in your work?

I use Claude Code every day. Everything it writes gets reviewed and tested by me before it ships.

Why is there a terminal?

I started in security and CTFs in 2011, and old habits stay. There's also a hidden flag in there for the curious.

sudo hire-me

Have a codebase that's fighting you?

Architecture, code, data, servers and security, owned by one person. A 30-minute call is enough to tell whether I can help.